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

[tsd@tsdye.com (Thomas S. Dye)]

Hi Nicolas,

I couldn't make this work.

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> 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.

I defined a new entity in org-entities-user, but the new exporter
appears to ignore it.  Does it look at this variable, or just
org-entities?

I played around a bit with entities defined in org-entities, and these
do transcode properly.  How do I get one in the middle of a word?  If I
leave a space after the entity, the space ends up in the output.  If I
don't leave a space, the entity isn't recognized.  

All the best,
Tom

>
> 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.

-- 
Thomas S. Dye
http://www.tsdye.com