From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Scott Randby <srandby@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Multiple underscores crash org latex export; other exporters survive
Date: Wed, 07 Dec 2016 12:21:39 +0100 [thread overview]
Message-ID: <87fum0htmk.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <084a9c31-e7b1-72af-8d78-9655dc006d00@gmail.com> (Scott Randby's message of "Tue, 6 Dec 2016 21:06:47 -0500")
Hello,
Scott Randby <srandby@gmail.com> writes:
> On 12/06/2016 06:50 PM, Nicolas Goaziou wrote:
>> I fixed it in maint. Basically, a_b_c is translated as a\(_b\)\(_c\).
>
> With this solution, "a" will be exported as text while "b" and "c" will
> be exported as a single subsrcipt using the math font.
Not at all. I simplified the output for clarity but the real generated
code is
a\(_{\text{b}}\)\(_{\text{c}}\)
> I would prefer that a_b_c be translated as \(a_{b_{c}}\).
As you pointed out, the string is ambiguous anyway. The point of the fix
is to generate valid LaTeX code. You can obtain the above unambiguously
with
a_{b_c}
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-12-07 11:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 19:40 Multiple underscores crash org latex export; other exporters survive Scott Otterson
2016-12-03 21:24 ` Scott Randby
2016-12-03 22:31 ` Charles C. Berry
2016-12-04 4:53 ` Scott Randby
2016-12-04 10:13 ` Nicolas Goaziou
2016-12-04 16:03 ` Scott Randby
2016-12-05 8:36 ` Scott Otterson
2016-12-06 1:33 ` Scott Randby
[not found] ` <CAPY3P0QcpouDjmNpmaY6FzNSNjZyHAGufrbVtSuBzPxr6mUAzg@mail.gmail.com>
2016-12-06 18:18 ` Scott Randby
2016-12-06 23:50 ` Nicolas Goaziou
2016-12-07 2:06 ` Scott Randby
2016-12-07 11:21 ` Nicolas Goaziou [this message]
2016-12-10 23:24 ` Scott Randby
2016-12-11 0:05 ` Nicolas Goaziou
2016-12-12 3:37 ` Scott Randby
2016-12-12 7:46 ` Nicolas Goaziou
2016-12-12 15:18 ` Scott Otterson
2016-12-13 12:54 ` Nicolas Goaziou
2016-12-05 17:30 ` Charles C. Berry
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=87fum0htmk.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@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).