[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [new exporter] latex: why does {{}} b ecome \{\{\}\} ?
From: |
Charles Berry |
Subject: |
Re: [O] [new exporter] latex: why does {{}} b ecome \{\{\}\} ? |
Date: |
Sun, 21 Oct 2012 18:47:04 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Sebastien Vauban <address@hidden> writes:
>
> Hi Nicolas,
>
> Nicolas Goaziou wrote:
> > "Sebastien Vauban"
> >> 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.
I guess I do not understand.
Using git pull today,
(org-export-to-buffer 'e-latex "scratch.tex") exports this
#+begin_latex
\begin{displaymath}
\mbox{a}=\frac{b}{1 + c}
\end{displaymath}
#+end_latex
as this
\begin{latex}
\begin{displaymath}
\mbox{a}=\frac{b}{1 + c}
\end{displaymath}
\end{latex}
So how do I get rid of the enclosing lines:
\begin{latex}
\end{latex}
??
Chuck
> >
> > 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.
>
> I realize having taken the bad habit of only using #+begin_src latex blocks
> even for code that only matters for the LaTeX back-end (such as TikZ
> decorations). By carefully using the Babel options, it comes down to the same
> effect/behavior, but, OK, that's NOT the Right Way To Do!
>
> Best regards,
> Seb
>