[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mozilla-i18n
Subject:    Making iso10646-x fonts available for encoding other than UTF-8(was..Re: ... font for GB18030 encodi
From:       Jungshik Shin <jshin () pantheon ! yale ! edu>
Date:       2001-06-29 18:56:37
[Download RAW message or body]

In <3B3BDCE4.691E8C62@netscape.com>, Yung-Fong Tang wrote:

: Good point. I don't think we have UI for that.
: I think Sun plan to use different way to support GB18030 font. They will
: have a "gb18030.2000-1" font instead of useing ISO10646-1 font


: James Su wrote:

:> Because GB18030 is a 4 bytes encoding, and XFree86 only allow 2 bytes
:> font encoding. So we cannot use GB18030 as font encoding, we must use
:> iso10646-1 directly for GB18030.
:> I think it's a bug of mozilla. iso10646-1 fonts should be added into the
:> fonts list of "Simplified Chinese" or perhaps all of the language list.

  More or less I agree with you on this point. I've already raised
this point a couple of times before because Korean also needs this
feature. 


: I am not sure that is the right way to deal with this.

  It might not be the best, but it can be argued that it's better than
keep making tons of fonts with locale-specific encodings  (such as
gb18030.2000-1, ksc5601.1992-3, and so forth).

  One thing Mozilla can do
is make use of 'style' field of XLFD to differentiate iso10646-1 fonts.
XF86 4.x ships a few iso10646-x fonts with 'ko' and 'ja' in style
field.  For a given language group (say Japanese), Mozilla may just
list iso10646-1 fonts with style field 'ja' in addition to jis x 208,
212 and other fonts it would list.

   Jungshik Shin

[prev in list] [next in list] [prev in thread] [next in thread]