Yasushi SHOJI <ya...@atmark-techno.com> writes:

> That means that whenever your-choice-of-coding-system can handle the
> "characters" for the translation string, meaning that the coding
> system has code points for all of the characters of the translation
> string and Emacs can convert between them, it is free to use any
> character for the output, right?
> If one wants to use French, she sets the current buffer coding system
> to any coding system which can handle French and set the language
> option as "fr".  In that case, her/his org buffer should already have
> French characters in it, there is no need for translation string to be
> strictly ASCII only when you export with plain / ascii, no?

There's a limitation: if you use Latin1 characters (e.g. when you write
in French), you cannot export to text/ascii anymore.

So, if, for some reason, you really need to export to ascii only, but
still need to write in french, you have to be careful not to use any of
these Latin1 characters, in particular in translated strings. Similarly,
Japanese :ascii entries could be written using romanji.

I don't know to what extent it is useful, though.

> I'm checking exporters I use, including plain text and html, but it
> doesn't seems to go wrong. But I really needs some help for other
> back-ends. I'll post a patch for testing if anyone's interested in.

Good idea.

You can also set entries to :default and provide a different :latex
value, if required.


Nicolas Goaziou

Reply via email to