From: tsd@tsdye.com (Thomas S. Dye)
To: Gunnar Wolf <gwolf@gwolf.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] Guides on what incompatibilities to watch for?
Date: Tue, 19 Feb 2013 09:11:20 -1000 [thread overview]
Message-ID: <m1zjz0dspz.fsf@tsdye.com> (raw)
In-Reply-To: <20130219175703.GC130669@gwolf.org> (Gunnar Wolf's message of "Tue, 19 Feb 2013 11:57:03 -0600")
Gunnar Wolf <gwolf@gwolf.org> writes:
> Hi,
>
> I'm not very specific in this mail, but am wondering…
>
> I have some nontrivial documents written in Org-mode. My main use case
> for Org is mostly to author texts, rather than using its time-tracking
> features. I fear that with the new exporter, several of my documents'
> features will no longer work or -worse- be interpretted differently,
> having a negative impact in my output.
>
> Is there a guide on what items should I mostly watch for (or even
> better, what syntax changes should I make) to get my results as
> similar as possible to what I had beforehand?
>
> I am not yet running with the new release; as I follow the Debian
> packaging, I'll rather wait until it "lands" in my system. Still, I
> want to prepare and not let this get me off-guard!
>
Aloha Gunnar,
Please see http://orgmode.org/worg/org-faq.html#new-exporter-switch.
Old documents will typically require some changes to work with the new
exporter, but the changes are relatively few and that Nicolas has worked
hard to preserve backward compatibility where possible.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-02-19 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 17:57 [new exporter] Guides on what incompatibilities to watch for? Gunnar Wolf
2013-02-19 19:04 ` Suvayu Ali
2013-02-19 19:38 ` Bastien
2013-02-19 19:11 ` Thomas S. Dye [this message]
2013-02-20 8:21 ` Eric S Fraga
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=m1zjz0dspz.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=gwolf@gwolf.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).