[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: [I18n] Unicode support status

This is a forwarded message
From: Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>
To: i18n@XFree86.Org <i18n@XFree86.Org>
Date: Thursday, June 08, 2000, 6:19:16 PM
Subject: [I18n] Unicode support status

===8<==============Original message text===============
There seems to be an upcoming code freeze for the 4.0.1 release next
week, which might be a good point to review the state of UTF-8 support
and other issues.

One of the major UTF-8 problems with XFree86 4.0 is that the UTF-8
support for xterm is not compiled in by default, i.e. the UTF-8 mode of
xterm is not yet widely available to users. What is necessary to fix
this and can it be done before 4.0.1?

I got bombarded with requests to add more ISO 8859 variants of the fixed
fonts, most notably by folks from Baltic countries who urgently want to
have 8859-4 and 8859-13 fonts. Therefore, I was planning to add all 8859
variants of the 6x13 and 8x13 fonts (including bold and oblique) to the
next update, unless there has been some progress with the BDF recoding
engine. (Juliusz?)

I got a contribution of an 18x18ko Korean UCS font. This font duplicates
many of the 18x18ja characters. Should I add it as a separate font or
shall we do something with font sets such that we have a single 18x18
chinese main font, and 18x18ko and 18x18jp contain only glyphs in those
code ranges where there are language-dependent stylistic differences.
Would existing software have difficulty with handling such a splitup?

Any progresses on the Xlib UTF-8 locale front that can already be
utilized in xterm?

Any other things missing?


Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org,  WWW: <http://www.cl.cam.ac.uk/~mgk25/>

I18n mailing list

===8<===========End of original message text===========

Best regards,
 hashao                            mailto:hashao@telebot.com

| This message was re-posted from debian-chinese@lists.debian.org
| and converted from big5 to gb2312 by an automatic gateway.

Reply to: