Georg Baum wrote:
No. What is exported currently to LaTeX is a mixture of utf8 (e.g.
InsetCommandParams) and ucs4 code points as numbers. It would be pretty
easy to always do utf8 export, but this does not make sense IMO before it
is clear how LaTeX export to other encodings than utf8 should look like.
I think the first question to answer is: Do we need to handle different
encodings in insets, or are we going to export to utf8 and converting if
necessary? The latter would be more simple, but it might not be flexible
enough.
LaTeX can do UTF8, it seems.
http://mail.nl.linux.org/linux-utf8/2004-04/msg00000.html
Just use "\usepackage[utf8]{inputenc}".
Let's do UTF-8 all over the place as the first step.
I can't believe nobody did this so far!
Georg, you can do that in a hour, can't you?
LyX 1.5 would instantly become useful again, and thus there is a chance
we would have testers!
After that, we can consider to support the encodings LyX-1.4 can use, to
the same level as LyX-1.4, but I would say that this is a second
priority: UTF-8 is superior in almost any way.
After that, we can see if more should be done, but I have not heard many
requests for strange encodings, so why bother at all?
Regards,
Asger
