[I18n]UTF-8 XLC_LOCALE for CJK
Hi all, I saw ko_KR.UTF-8 and ja_JP.UTF-8 XLC_LOCALE files has accepted into CVS (#5421, Jungshik Shin). Is it sane to add zh_TW.UTF-8 and zh_CN.UTF-8 XLC_LOCALE also? Also putting BIG5-0 for legacy support in UTF-8 is a right thing to do? Regards, Leon -- Leon Ho, Red Hat Inc., Asia-Pacific Operations <[EMAIL PROTECTED]> Files:http://people.redhat.com/llch Legal:http://apac.redhat.com/disclaimer ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]Unicode coverage for languages
On Sun, 7 Jul 2002, Keith Packard wrote: > > http://www.info.gov.hk/digital21/eng/hkscs/download.html > > Thanks. I notice that the newest part of this table references quite a > few symbols beyond the BMP; would you suggest that I use the older > entries? Or should I use the non-BMP entries and let people only use > fonts with support for those glyphs? I think the idea is to stick to its ISO10646-1:2000 codepoints as most HKSCS fonts I have seen are only reference to these codepoints (which within BMP). Leon -- Leon Ho, Red Hat Inc., Asia-Pacific Operations <[EMAIL PROTECTED]> Files:http://people.redhat.com/llch Legal:http://apac.redhat.com/disclaimer ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]Unicode coverage for languages
On Sun, 7 Jul 2002, Keith Packard wrote: > > The question is whether we should mark certified GB18030 fonts as suitable > for zh-TW as well as zh-CN. I have the GB18030 varient of SimSun here in > TrueType and it does not have the traditional Chinese codePageRange bit > set, but does cover the codepoints found in Big5. > > If that's just varience in typographic style, we should make sure it > doesn't influence language support. Should a reader in zh-CN locale > use a Sung typeface for traditional Chinese? Or should we direct them to > a Ming typeface instead? It would be a good idea to let user to determine (or overwrite the default) on what font they want to use for each language (ie. in fonts.conf). > > Would it be appropriate to mark a GB18030 font as supporting 'zh' then? > Right now, I'm using: I think the ideal way is to add certified GB18030 for zh, but with lower priority. But of course users may encounter the mixed glyphs from different character if they have a incomplete Big5 or HKSCS font. ie. Higher its priority if it have correct codePageRange bit, include the font and lower its priority if it covers the codepoints but does not not match that codePageRange bit. > > gb2312 -> zh-cn > Big5-> zh-tw > JIS X 0208 -> ja > KSC 5601-> ko > > I could easily add: > > GB18030 -> zh > > As per your earlier suggestion, I will add: > > gb2312 -> zh-sg > Big5-> zh-mo > > I don't have a complete codepoint set for HKSCS; can someone point me at > one? http://www.info.gov.hk/digital21/eng/hkscs/download.html Other useful documents: http://www.info.gov.hk/digital21/eng/hkscs/document.html > > With these additions, a GB18030 font would advertise support for: > > zh, zh-cn, zh-tw, zh-sg, zh-mo > > while older GB2312 fonts would be limited to > > zh-cn, zh-sg > > Keith PackardXFree86 Core TeamHP Cambridge Research Lab -- Leon Ho, Red Hat Inc., Asia-Pacific Operations <[EMAIL PROTECTED]> Files:http://people.redhat.com/llch Legal:http://apac.redhat.com/disclaimer ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]xterm to invoke luit
> > Does luit support the encodings that do not compatible with iso-2022? > > For example GB18030? > > It supports a few non-ISO-2022-compliant encodings such as Big5. > It doesn't support GB18030 so far, though Juliusz is willing to > support it. See his message at If I do # LANG=zh_TW.Big5 xterm -u8 -e luit Warning: couldn't find charset data for locale zh_TW.Big5; using ISO 8859-1. # xterm -u8 -e luit -g2 'Big 5' # LANG=zh_TW.Big5 It still cannot display any big5 encoded char. Anything I did wrong? Leon > > http://mail.nl.linux.org/linux-utf8/2001-11/msg00093.html > > for detail. -- Leon Ho, Red Hat Inc., Asia-Pacific Operations <[EMAIL PROTECTED]> Files:http://people.redhat.com/llch Legal:http://apac.redhat.com/disclaimer ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [I18n]Re: [Xpert]4.2 is not compatiable with 4.1 ?
On Mon, 28 Jan 2002, Owen Taylor wrote: > I believe the cause and effect was: > > - xcin didn't work > - This cause untested code to be run which crashed. > > So, the crash was a side effect of xcin not working; I looked > at it a bit and it didn't work with: > > XMODIFIERS=@im=xcin By default if you have LANG=zh_TW.Big5, then "xcin" is the default IM server name. If LANG=zh_CN.GB2312, then the server name should be "xcin-zh_CN.GB2312" > But it worked fine with: > > XMODIFIERS=@im=xcin-zh_TW > > (At least, I got a status window to pop up.) > > If the previous used to work, it probably was because Xlib used to be > less strict about checking the IM server name; xcin doesn't seem to > support 'xcin' as a servername, just xcin-zh_TW and xcin-zh_CN. -- Leon Ho, Red Hat Inc., Asia-Pacific Operations <[EMAIL PROTECTED]> Files:http://people.redhat.com/llch Legal:http://apac.redhat.com/disclaimer ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
