From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Sebastien Vauban
<public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.org>
Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: [new exporter] latex: why does {{}} become \{\{\}\} ?
Date: Wed, 17 Oct 2012 14:03:57 +0200 [thread overview]
Message-ID: <87bog1nw42.fsf@gmail.com> (raw)
In-Reply-To: <80hapu85ib.fsf@somewhere.org> (Sebastien Vauban's message of "Tue, 16 Oct 2012 23:35:24 +0200")
Hello,
"Sebastien Vauban"
<wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
> Hello Nicolas,
>
> Nicolas Goaziou wrote:
>> "Myles English" <mylesenglish-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> Can anyone tell me please why (in the examples below) {} exports fine
>>> but {{}} exports as \{\{\}\} ? Am I meant to wrap these in
>>> #+begin_latex blocks?
>>
>> You're writing LaTeX code in an Org buffer. This is only possible to
>> a limited extent. In particular, these lines should indeed go within
>> a LaTeX block.
>
> Within a LaTeX block (#+begin_latex) or within a Babel block for LaTeX
> language (#+begin_src latex)? Do you make a difference?
There's a big difference.
#+begin_latex means "paste this code unmodified in the latex back-end,
and only in the latex back-end". Nothing is evaluated.
With a #+begin_src latex block, depending on :exports parameter, you can
produce something (in this case, probably an image file) and create
a link valid in any back-end, as long as it supports the file format.
Both are possible.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-10-17 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 15:29 [new exporter] latex: why does {{}} become \{\{\}\} ? Myles English
2012-10-16 19:21 ` Nicolas Goaziou
2012-10-16 21:26 ` Myles English
2012-10-16 21:35 ` Sebastien Vauban
2012-10-17 12:03 ` Nicolas Goaziou [this message]
2012-10-19 13:05 ` Sebastien Vauban
2012-10-21 18:47 ` Charles Berry
2012-10-21 19:14 ` cberry
2012-10-21 19:51 ` Myles English
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=87bog1nw42.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@plane.gmane.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).