From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: "Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Fri, 19 Sep 2014 08:49:19 -0700 [thread overview]
Message-ID: <8738bn391c.fsf@berkeley.edu> (raw)
In-Reply-To: <CACsgZ=r1vzPQg1KB3N7j6Mn+nyu=PUrxJCeRr5ebqmpywsQ0bg@mail.gmail.com>
Hi Joseph,
"Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com> writes:
> Great thanks for your answering my two questions, especially sharing your
> experience for cross-referencing in LaTeX export.
>
> Though your suggestion for cross-referencing is an excellent workaround, I
> wonder whether there is any benefit using org-mode in writing papers in
> this case; for instance, manual setting of CUSTOM_ID would be a hassle,
> considering that it can be easily & automatically done in LaTeX with
> AUCTeX/RefTeX's label function.
Don't you need to make sure that your sections have a consistent label
in order to refer to them?
At any rate, one of the reasons I use this solution is that I want to be
able to easily use plain LaTeX at points where I discover that I can't
make Org do everything I want. One of the cases I was worried about,
for example, is having a section reference inside an embedded LaTeX
block. If you don't know the label ahead of time, you can't use a raw
\ref command inside #+BEGIN_LATEX...#+END_LATEX. So I like being able
to set the labels via CUSTOM_ID on an as-needed basis. (I don't do it
for every section.)
You might be able to get away with less; it looks to me like the
[[*Foo][Section Foo]] still produces a link to a headline in LaTeX
output. Does that not work for you?
> I still don't know why the new export engine has brought so many
> compatibility issues in its behavior. It seems that I'd better go
> back to the prior version (7.X) in order to focus on my research.
The new export engine was a complete re-write, and came with an attempt
to define and standardize Org syntax. Some of the incompatibilities are
due to that standardization: the old LaTeX and HTML exporters might
treat some text differently, for example, or not deal with some corner
case, so in writing a new export engine, it was necessary to define the
correct behavior. Other incompatibilities are just bugs that come with
any new piece of software; the exporter is under heavy development and
those are constantly getting fixed.
The new exporter really is a *lot* better, and in my experience it is
worth the effort to upgrade. I found myself bumping into the
limitations of the pre-8.0 exporter very frequently. If you don't, you
can wait, but I think you'll find the new exporter a lot easier to work
with and to get help with.
Best,
Richard
OpenPGP Key ID: CF6FA646
Fingerprint: 9969 43E1 CF6F A646
(See http://www.ocf.berkeley.edu/~rwl/encryption.html for more information.)
next prev parent reply other threads:[~2014-09-19 15:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 4:50 Changed behaviours of LaTeX exporter in version 8.0+ Kyeong Soo (Joseph) Kim
2014-09-18 7:07 ` Kyeong Soo (Joseph) Kim
2014-09-18 7:32 ` Kyeong Soo (Joseph) Kim
2014-09-18 16:10 ` Richard Lawrence
[not found] ` <CACsgZ=r1vzPQg1KB3N7j6Mn+nyu=PUrxJCeRr5ebqmpywsQ0bg@mail.gmail.com>
2014-09-19 15:49 ` Richard Lawrence [this message]
2014-09-20 15:32 ` Kyeong Soo (Joseph) Kim
2014-09-22 16:00 ` Nicolas Goaziou
2014-09-23 3:03 ` Kyeong Soo (Joseph) Kim
2014-09-27 22:01 ` Nicolas Goaziou
2014-09-29 4:51 ` Kyeong Soo (Joseph) Kim
2014-09-29 7:07 ` Nicolas Goaziou
2014-09-29 7:57 ` Kyeong Soo (Joseph) Kim
2014-09-29 8:53 ` Rasmus
2014-09-29 9:59 ` Kyeong Soo (Joseph) Kim
2014-09-29 10:09 ` Rasmus
2014-09-29 12:18 ` Kyeong Soo (Joseph) Kim
2014-09-29 14:18 ` Rasmus
2014-09-29 14:18 ` Rasmus
2014-10-01 9:39 ` Kyeong Soo (Joseph) Kim
2014-09-18 15:47 ` Richard Lawrence
-- strict thread matches above, loose matches on Subject: below --
2014-09-17 14:54 Kyeong Soo (Joseph) Kim
2014-09-17 19:01 ` Nicolas Goaziou
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=8738bn391c.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=kyeongsoo.kim@gmail.com \
/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).