emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Christian Moe <mail@christianmoe.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org, Piter_ <x.piter@gmail.com>
Subject: Re: plus in superscript.
Date: Thu, 15 Sep 2011 09:43:57 +0200	[thread overview]
Message-ID: <4E71ACBD.9030102@christianmoe.com> (raw)
In-Reply-To: <424.1316071148@alphaville.dokosmarshall.org>

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

Yours,

Christian

On 9/15/11 9:19 AM, Nick Dokos wrote:
> suvayu ali<fatkasuvayu+linux@gmail.com>  wrote:
>
>> Hi Nick,
>>
>> On Wed, Sep 14, 2011 at 6:55 PM, Nick Dokos<nicholas.dokos@hp.com>  wrote:
>>> * This is a test: \(T^{+}\)
>>
>> Apart from what Christian said, do you have any comments about $..$
>> and \(..\) ? I hear conflicting arguments about which is preferred
>> (e.g. $..$ is a TeX construct where as \(..\) is a LaTeX macro arguing
>> in favour of $..$). Specially an opinion in the context of org ->
>> latex export would be interesting to hear.
>>
>
> As far as LaTeX is concerned, I believe that $...$ and \(...\) are
> entirely equivalent (but you have to use \[...\], and not $$...$$ for
> displayed material). That's from reading Lamport's book: sec 3.3 and
> Appendix E (the "Miscellaneous" section); I have not checked the code.
>
> I prefer \(...\) and (iirc) sometimes that has worked when $...$ has
> not, but I don't remember the context; afaik those (rare) situations
> were deemed to be bugs in the exporter and have all been fixed.
>
> Nick
>
>
>

next prev parent reply	other threads:[~2011-09-15  7:42 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 [this message]
2011-09-15  7:44         ` Carsten Dominik
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=4E71ACBD.9030102@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --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

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).