On Fri, 6 Dec 2002, Jungshik Shin wrote: > On Fri, 6 Dec 2002, Maiorana, Jason wrote: > > im curious why I would set the LC_CYPTE to ja_JP.UTF-8, > > why would that be any different than en_US.UTF-8 when the > > LANG is en_US.UTF-8. I'm not worried about japanese collation
> Unfortunately, most XIM servers are written in such a way > that they can only be launched under a certain locale. However, BTW, I didn't mean that kinput2, Xcin and Ami cannot be modified to work under en_US.UTF-8 locale. They can, but their dependency on fontset make them work less optimal than under their 'native' locales. I guess we have to give up 'stretching' old XIM protocol and had better focus on a new IIIMF(Internet Intranet Input Method Framework: http://www.openi18n.org/subgroups/im/IIIMF. Li18Nux.org changed the name to become OpenI18N.org) or gtk2 input modules or similar mechanisms. MS Windows has something called TSF(Text Service Framework) which appears to be very flexible. IMHO, XIM is too old to be on par with likes of TSF. IIIMF is at a far better position for that than XIM. Jungshik -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
