emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: LaTeX math mode and export
Date: Sat, 12 Oct 2013 12:56:28 +0200	[thread overview]
Message-ID: <20131012105628.GA31274@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <874n8m9azg.fsf@gmail.com>

On Sat, Oct 12, 2013 at 09:58:27AM +0200, Nicolas Goaziou wrote:
> Fabrice Popineau <fabrice.popineau@supelec.fr> writes:
> 
> > The problem as I feel it is that \[ \] works sometimes, but not as
> > often as with LaTeX, which is disconcerting.
> 
> \[...\] is more limited in Org than in LaTeX, indeed.
> 
> > I know that theparagraph entity in Org mode is different than what it is is
> > in LaTeX, but still.
> >
> > Why \[ ... \] couldn't be handled as if it where \begin{equation} ...
> > \end{equation} ?
> > Is there any other use of \[ that would prevent its detection ?
> 
> There are two types of structures in Org syntax: inline (i.e. contained
> in a paragraph) and not inline. inlined structures always belong to
> a non-inlined one. Therefore, the parser always gives precedence to
> non-inlined syntax over inlined one.
> 
> Thus, the following example will be a single paragraph with some maths
> inside:
> 
>   A paragraph with \[1+1=2\] maths.
> 
> But the following one:
> 
>   A paragraph
>   \[1
>     + 1
>     = 2
>   \]
>   with maths.
> 
> will be a paragraph, a list and another paragraph: "A paragraph\n\[1",
> " + 1" and " = 2\n\]\nwith maths."
> 
> If \[...\] constructs were to be changed into non-inlined, the maths
> snippet in the first example would not be recognized.
> 
> It is theoretically possible to make "\[...\]" both inline and
> non-inline. Though, I have the feeling that it would come with its own
> set of problems.

A very nice explanation.  Thank you.

> > Sorry to be such an hassle, but that would help to smooth the conversion of
> > previous LaTeX files/users
> > to Org.
> 
> I think that a major pitfall for these users is to think that you can
> wrap LaTeX syntax in Org structures. Actually, Org only supports
> a limited set of LaTeX syntax.

If I may, I think these users are better off using some of the Org
outside Org libraries.

  <http://orgmode.org/worg/org-tutorials/org-outside-org.html>

One of Org's goals, with regards to exporters, is to be uniform across
all backends so that one can export the same document using multiple
backends without major changes.  Including more and more LaTeX source
deviates from that goal.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

      parent reply	other threads:[~2013-10-12 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11  9:13 LaTeX math mode and export Fabrice Popineau
2013-10-11 15:43 ` Nicolas Goaziou
2013-10-11 22:03   ` Fabrice Popineau
2013-10-12  7:58     ` Nicolas Goaziou
2013-10-12  8:31       ` Nicolas Goaziou
2013-10-12 10:56       ` Suvayu Ali [this message]

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=20131012105628.GA31274@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --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).