Matthias Neubauer <neubauer(a)informatik.uni-freiburg.de> writes:
>>>> Given a working Mule (e.g. a Mule that can convert
between character
>>>> sets and UTF 8 correctly), adding Xft support to it should be a one
>>>> day project. We already have the supplementary patch from Yuri and
>>>> Alkesey.
>>>>
>>>> It would be really cool if some of you, the XEmacs/Mule guys, could
>>>> look at their Unicode conversion and tell us whether this is the right
>>>> thing to do to get such an Utf8 conversion. Or otherwise tell us how
>>>> to fix it. Given that, I am more than happy to integrate it in our
>>>> stuff to enable Mule support right away.
So all I'd like to know for now is, if it's generally possible to
convert text coded in one of the different character sets to Utf8
(and if so how)? It shouldn't be that hard to answer that question?
Or is it?
On the display level, you only have to deal with one character set,
the internal encoding used by Mule. That is a variable width encoding
that shares some properties with UTF-8, but is not based on Unicode.
It's possible to convert this internal encoding to UTF-8, but it
requires mapping tables from Mule characters to Unicode characters,
and those mapping tables are huge. Such tables might exist in 21.5,
but I'm not sure.