[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Thomas S. Dye
Subject: Re: [O] [ANN] ASCII back-end for new export engine
Date: Mon, 06 Feb 2012 08:46:05 -1000

Nicolas Goaziou <address@hidden> writes:

> address@hidden (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.

Yes, this seems like a good solution.  Thanks.
> 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?


  - off, no information is inserted
  - on, information is inserted in \hypersetup{} and as text at the end of the 
  - comment, information is inserted in \hypersetup and as a comment at the
end of the file.
All the best,

Thomas S. Dye

reply via email to

[Prev in Thread] Current Thread [Next in Thread]