emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Thomas Holst <thomas.holst@de.bosch.com>
Cc: Orgmode <emacs-orgmode@gnu.org>
Subject: Re: [new exporter] problems exporting mathmode to LaTeX
Date: Wed, 18 Jul 2012 15:46:55 +0200	[thread overview]
Message-ID: <87txx52ncg.fsf@gmail.com> (raw)
In-Reply-To: <ywodwr21gywx@de.bosch.com> (Thomas Holst's message of "Wed, 18 Jul 2012 12:13:18 +0200")

Hello,

Thomas Holst <thomas.holst@de.bosch.com> writes:

> So here is the next one:
> #+BEGIN_SRC org
>   160\(^\circ\}\nbsp{}C
>   -11^{\circ}\nbsp{}C
> #+END_SRC
>
> With the old exporter this becomes:
> #+BEGIN_SRC latex
>   160\(^\circ\)~C
>   -11$^{\circ}$~C
> #+END_SRC
> in LaTeX. Which looks well in pdf.
>
> With the new exporter it becomes:
> #+BEGIN_SRC latex
>   160\(^\circ\)~C
>   -11$^{\mathrm{\^{}}}$~C
> #+END_SRC
> in LaTeX. Where the second construct obviously is not what is expected
> and looks totaly wrong in pdf.

I don't know how you obtain this result, you may have settings different
than mine.

Anyway, the new exporter doesn't change anything with regards to src
blocks. It basically runs `org-export-blocks-preprocess' in a temporary
clone of the buffer being exported and then parses the obtained
expansion.

If you want to have a glimpse at what is really parsed, you can evaluate
the following snippet in the buffer you want to export:

  (let ((org-current-export-file (current-buffer)))
    (org-export-blocks-preprocess))

It may help to understand what is going on.


Regards,

-- 
Nicolas Goaziou

  parent reply	other threads:[~2012-07-18 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-18 10:13 [new exporter] problems exporting mathmode to LaTeX Thomas Holst
2012-07-18 11:48 ` Giovanni Ridolfi
2012-07-18 13:46 ` Nicolas Goaziou [this message]
2012-07-18 14:18   ` Holst Thomas (DGS-EC/ESE4)
2012-07-18 14:48     ` Nicolas Goaziou
2012-07-19  6:48       ` Thomas Holst

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=87txx52ncg.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=thomas.holst@de.bosch.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).