Re: [ANN] ASCII back-end for new export engine

[Nicolas Goaziou <n.goaziou@gmail.com>]

tsd@tsdye.com (Thomas S. Dye) writes:

> The old exporter recognized LaTeX commands for accented characters.  So,
> \=o in the Org mode file would yield \={o} in the LaTeX file.  The new
> exporter gives $\backslash$=o for this construct.  

Indeed, the parser recognizes LaTeX commands and environments, but is
more strict with other LaTeXisms.

> How does the new
> LaTeX exporter recognize accented characters?

The Org way (portable across major back-ends) to handle this is to
define an new entity, and name it for example "omacr"[1]. You can
then access it with \omacr in your buffer.

Other (but inferior) solutions could be to define a macro:

                          #+macro: omacr \={o}

or use an export snippet:

                            @e-latex{\={o}}

> I can't find a way to get creator information into \hypersetup{} without
> also having it inserted as normal text at the end of the file.  Is this
> possible?

That's not possible at the moment.

There are three states for creator, on, off and comment, and two places
to insert the information (in hypersetup and at the end of the exported
data).

What would be a correct way to handle the different configurations here?


Regards,

[1] I'm a bit surprised that it doesn't exist in `org-entities', as
many national characters are already there.

-- 
Nicolas Goaziou