[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

Re: [I18n]Unicode coverage for languages

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 Operati

Re: [I18n]Unicode coverage for languages

o.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 wou

Re: [I18n]xterm to invoke luit

inux.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 ?

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 Ha