From: Carsten Dominik <carsten.dominik@gmail.com>
To: mail@christianmoe.com
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org, Piter_ <x.piter@gmail.com>
Subject: Re: plus in superscript.
Date: Thu, 15 Sep 2011 09:44:51 +0200 [thread overview]
Message-ID: <E21C2BF1-EF39-4DC8-8282-809EFDDA1B42@gmail.com> (raw)
In-Reply-To: <4E71ACBD.9030102@christianmoe.com>
On Sep 15, 2011, at 9:43 AM, Christian Moe wrote:
> Hi,
>
> $...$ may sometimes get confused with currency signs, variable names and whatnot.
>
> Org-mode is sophisticated about it as long as you follow a few safeguards -- from the Info section 11.7.3:
>
> To avoid conflicts
> with currency specifications, single `$' characters are only
> recognized as math delimiters if the enclosed text contains at
> most two line breaks, is directly attached to the `$' characters
> with no whitespace in between, and if the closing `$' is followed
> by whitespace, punctuation or a dash. For the other delimiters,
> there is no such restriction, so when in doubt, use `\(...\)' as
> inline math delimiters.
>
> But note that MathJax, the preferred backend for math in Org's HTML exports, does not support $...$ by default. To configure it, see:
>
> http://www.mathjax.org/docs/1.1/tex.html#tex-and-latex-math-delimiters
When Org exports to HTML for use with MathJax, it does convert $..$ to \(..\) to work around this.
Still, parsing $...$ is much harder than parsing \(..\), so most of the time, using \(//\) will give better and more stable results with Org-mode.
- Carsten
next prev parent reply other threads:[~2011-09-15 7:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 16:32 plus in superscript Piter_
2011-09-14 16:55 ` Nick Dokos
2011-09-14 17:21 ` Christian Moe
2011-09-14 17:28 ` Nick Dokos
2011-09-14 22:29 ` suvayu ali
2011-09-15 7:19 ` Nick Dokos
2011-09-15 7:43 ` Christian Moe
2011-09-15 7:44 ` Carsten Dominik [this message]
2011-09-15 8:23 ` Christian Moe
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=E21C2BF1-EF39-4DC8-8282-809EFDDA1B42@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--cc=nicholas.dokos@hp.com \
--cc=x.piter@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).