From: Rasmus <rasmus@gmx.us>
To: bzg@gnu.org
Cc: emacs-orgmode@gnu.org
Subject: Re: LaTeX special characters 8.3.1
Date: Sun, 16 Aug 2015 16:00:02 +0200 [thread overview]
Message-ID: <87fv3jnxjx.fsf@gmx.us> (raw)
In-Reply-To: <874mjzqtbi.fsf@gnu.org> (Bastien Guerry's message of "Sun, 16 Aug 2015 15:03:13 +0200")
Bastien Guerry <bzg@gnu.org> writes:
> Hi Rasmus,
>
> Rasmus <rasmus@gmx.us> writes:
>
>> Scott Randby <srandby@gmail.com> writes:
>>
>>> Until 8.3.1, I needed to use \% in an org document in order to get the
>>> % symbol displayed when exporting to LaTeX. I just discovered that \%
>>> messes up the exported document, and that using % only works. I've
>>> also experimented with \$ and $ and found the same behavior.
>>>
>>> I've looked through the 8.3.1 changes document, but I can't find
>>> reference to this change. Since I use special characters frequently, I
>>> need more information about this change. Where can I find it?
>>
>> % Is exported as "\%" in latex.
>>
>> $ is a mess. It's uses some heuristic to determine if it's a math snippet
>> or a currency symbol.
>>
>> You can always use a snippet, @@latex:%@@ which is exported literally in
>> the backend before the colon.
>
> Did you find the change we could document in ORG-NEWS?
AFAIK there's no change in 8.3. If you export a document consisting of
"$ %" with ox-latex with 8.2.10 you also get "\$ \%".
Rasmus
--
Lasciate ogni speranza o voi che entrate: siete nella mani di'machellaio
next prev parent reply other threads:[~2015-08-16 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 18:19 LaTeX special characters 8.3.1 Scott Randby
2015-08-08 18:24 ` Ken Mankoff
2015-08-08 18:52 ` Rasmus
2015-08-08 19:00 ` Scott Randby
2015-08-16 13:03 ` Bastien Guerry
2015-08-16 14:00 ` Rasmus [this message]
2015-08-16 14:15 ` Bastien Guerry
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=87fv3jnxjx.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=bzg@gnu.org \
--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).