From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: [patch] Support CUSTOM_ID property in latex export
Date: Sun, 16 Feb 2014 10:10:12 +0100 [thread overview]
Message-ID: <87iosfs9sb.fsf@gmail.com> (raw)
In-Reply-To: <87vbwggcwb.fsf@berkeley.edu> (Richard Lawrence's message of "Sat, 15 Feb 2014 15:43:48 -0800")
Hello,
Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> 1) Sometimes I need to refer to a section from within an embedded LaTeX
> block. In that case, I need to know the appropriate label to use at the
> LaTeX level, not just in Org. For example:
>
> * A headline
> :PROPERTIES:
> :CUSTOM_ID: sec:a-headline
> :END:
>
> # ... stuff ...
>
> #+BEGIN_LATEX
> % ... more stuff ...
> (see section~\ref{sec:a-headline})
> #+END_LATEX
I don't think this is a good idea, as the character set allowed in
\label{...} macros is only a subset of the character set allowed in
custom id value. Hence the `org-export-solidify-link-text' function.
If you are cautious, this will not be a problem, but it could bite users
with little LaTeX knowledge.
> This is not possible with the present section labeling in LaTeX export,
> because I have no way of forcing Org to use a particular label for a
> section.
* A headline
#+latex: \label{my-section}
#+BEGIN_LATEX
% ... more stuff ...
(see section~\ref{my-section})
#+END_LATEX
It also seems more consistent to me: since you want to explicitly write
the \ref{...}, you are also expected to explicitly write the \label{...}
part.
> 2) I hope this doesn't happen, but there may come a time when I need to
> move away from Org and just use straight LaTeX. Having control over the
> labeling will make this transition much easier, because it means I won't
> have to worry about manually changing the labels in a long document from
> Org's default "sec-..." numbering to my own semantic labels.
See above. You can even automate that with a hook (i.e., get the custom
id value and add a corresponding label at the beginning of the
headline).
> 3) This will make the LaTeX exporter's behavior more consistent with the
> HTML exporter's behavior. The HTML exporter will use CUSTOM_ID if it is
> supplied to construct the id attributes of headlines and divs. If
> someone is relying on this behavior of the HTML exporter, they might be
> unpleasantly surprised by the LaTeX exporter's behavior.
One relying on an implementation detail instead of the actual
specifications has to be prepared for surprises.
What do you think?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-02-16 9:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 20:19 [patch] Support CUSTOM_ID property in latex export Richard Lawrence
2014-02-15 22:44 ` Nicolas Goaziou
2014-02-15 23:43 ` Richard Lawrence
2014-02-16 9:10 ` Nicolas Goaziou [this message]
2014-02-16 20:10 ` Richard Lawrence
2014-02-18 21:56 ` Nicolas Goaziou
2014-02-18 22:35 ` Richard Lawrence
2014-02-19 12:43 ` Nicolas Goaziou
2014-02-20 5:04 ` Richard Lawrence
2014-02-21 19:35 ` Richard Lawrence
2014-02-22 9:24 ` Nicolas Goaziou
2014-02-22 20:35 ` Richard Lawrence
2014-02-22 22:31 ` Nicolas Goaziou
2014-02-23 0:37 ` Richard Lawrence
2014-02-23 8:37 ` Nicolas Goaziou
2014-02-23 8:53 ` Achim Gratz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iosfs9sb.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.