Around 15 o'clock on May 15, Juliusz Chroboczek wrote:
> XTerm will remain Unicode-only internally, if that's what you mean.
> The question is whether the ISO 2022 interpreter should be part of
> XTerm, or in a separate process.
Yes, that's what I meant. You frightened me a bit with visions of 2022
parsing in the middle of the existing VT100 emulator. Is it UTF-8 or some
UCS varient?
> Perhaps not on topic, but a side effect of this latest work is that
> fontenc has been adapted for use as a standalone library (nthe new
> version hasn't been submitted to XFree86 yet).
That's excellent. I can build a simple glue library between that and Xft
to provide legacy encoding transformations to a pure Unicode Xft library.
Now I just need to manage truetype fonts with broken (or non-existant)
Unicode tables. The existing Xft APIs will be officially specified as
Unicode only; the 'encoding' field in an Xft name will only specify the
desired subset of Unicode to match.
[EMAIL PROTECTED] XFree86 Core Team SuSE, Inc.
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
