emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: old to new converter transition
Date: Fri, 08 Feb 2013 13:07:28 +0100	[thread overview]
Message-ID: <87ip63nh4v.fsf@gmail.com> (raw)
In-Reply-To: 5114AF3E.9000106@gmail.com

[-- Attachment #1: Type: text/plain, Size: 259 bytes --]

Rainer M Krug <r.m.krug@gmail.com> writes:

> Would it be possible to collect this info on a "quick and dirty" worg page? At the moment, the
> info is in several different threads?

here is at least a nicely formatted version of this info I made for
myself:


[-- Attachment #2: Org-mode transition old-to-new-exporter --]
[-- Type: text/plain, Size: 1654 bytes --]

               _________________________________________

                ORGMODE: OLD TO NEW EXPORTER TRANSITION

                            Thorsten Jolitz
               _________________________________________


                             2013-02-08 Fr


Table of Contents
_________________

1 Org-mode transition from old to new exporter
.. 1.1 Export engine renamed:
.. 1.2 Backend requires renamed:
.. 1.3 All backend specific variables and functions renamed:
.. 1.4 Generic export variables retain the name org-export-*
.. 1.5 org-latex-to-pdf-process has been renamed
.. 1.6 Guess, export snippets and backend symbols renamed:


/unofficial summary of changes/


1 Org-mode transition from old to new exporter
==============================================

1.1 Export engine renamed:
~~~~~~~~~~~~~~~~~~~~~~~~~~

  org-export → ox


1.2 Backend requires renamed:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  org-e-* → ox-*


1.3 All backend specific variables and functions renamed:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  - org-export-* → org-* (e.g. org-html-xml-declaration, ..)
  - org-e-* → org-* (e.g. org-latex-classes, org-ascii-bullets, ..)


1.4 Generic export variables retain the name org-export-*
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  (e.g. org-export-dispatch-use-expert-ui,
   org-export-filter-headline-functions, ..)


1.5 org-latex-to-pdf-process has been renamed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  to org-latex-pdf-process


1.6 Guess, export snippets and backend symbols renamed:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  - e-<backend> → <backend>

[-- Attachment #3: Type: text/plain, Size: 22 bytes --]


-- 
cheers,
Thorsten

  reply	other threads:[~2013-02-08 12:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-07 14:26 old to new converter transition Rainer M Krug
2013-02-07 14:29 ` Nicolas Goaziou
2013-02-07 14:31   ` Rainer M Krug
2013-02-07 15:04 ` Suvayu Ali
2013-02-08  7:54   ` Rainer M Krug
2013-02-08 12:07     ` Thorsten Jolitz [this message]
2013-02-08 16:25     ` Bastien
2013-02-08 16:51       ` Suvayu Ali
2013-02-08 18:33         ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ip63nh4v.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).