Hi, At Thu, 2 May 2002 02:14:29 -0400 (EDT), Jungshik Shin wrote:
> You mean IIIMF, didn't you? If there's any actual implementation, > I'd love to try it out. We need to have Windows 2k/XP or MacOS 9/X > style keyboard/IM switching mechanism/UI so that keyboard/IM modules > targeted at/customized for each language can coexist and be brought up as > necessary. It appears that IIIMF seems to be the only way unless somebody > writes a gigantic one-fits-all XIM server for UTF-8 locale(s). I heard that IIIMF has some security problems from Project HEKE people http://www.kmc.gr.jp/proj/heke/ . I don't know whether it is true or not, nor the problem (if any) is solved or not. There _is_ already an implementation of IIIMF. You can download it from Li18nux site. However, I could not succeeded to try it. Since I have heard several reports of IIIMF users, it is simply my fault. There seems to be some XIM-based implementations which can input multiple complex languages. One is "ximswitch" software in Kondara Linux distribution. http://www.kondara.org . I downloaded it but I didn't test it yet. Another is mlterm http://mlterm.sourceforge.net/ which is entirely client-side solution to switch multiple XIM servers. Though I don't think it is a good idea to require clients to have such mechanisms, it is the only practical way so far to realize multiple language input. > How about just running your favorite XIM under ja_JP.EUC-JP while > all other applications are launched under ja_JP.UTF-8? As you know well, > it just works fine although the character repertoire you can enter > is limited to that of EUC-JP. Of course, this is not full-blown UTF-8 > support, but at least it should give you the same degree of Japanese > input support under ja_JP.UTF-8 as under ja_JP.EUC-JP. Well, then > you would say what the point of moving to UTF-8 is. You can at least > display more characters under UTF-8 than under EUC-JP, can't you? :-) There are, so far, no conversion engine which requires over-EUC-JP character set. Thus, EUC-JP is enough now. If someone wants to develop an input engine which supports more characters, he/she will want to use UTF-8. However, I think nobody feels strong necessity of it in Japan, besides pure technical interests for Unicode itself. > BTW, Xkb may work for Korean Hangul, too and we don't need > XIM if we use 'three-set keyboard' instead of 'two-set keyboard' and can > live without Hanjas. I have to know more about Xkb to be certain, though. I see. This is not true for Japanese. Japanese people do need grammar and context analysis software to get Kanji text. How about Chinese? --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ "Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/ -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
