On Thu, 17 Oct 2002, Tomohiro KUBOTA wrote: > > I also noticed that if XMODIFIERS="@im=kinput2", kinput2 still does not > > work if the application is not launched in a ja_JP.* locale (fr_FR.UTF-8 > > does not work). > Please try ja_JP.UTF-8 locale.
That's what I use. kword and the like are able to use kinput2 if they are launched in the ja_JP.UTF-8 locale but not in they are launched in fr_FR.UTF-8. > Please try mlterm. (http://mlterm.sourceforge.net/) It can use > multiple XIM servers by switching. It is not a good idea to use > multiple XIM servers *at the exactly same time*, because you will > need multiple key binds for invocation of each XIM server. Anyway, Sure. But you should be able to, say, type a text using Compose (Multi_key and dead keys) for, say, French, and invoke kinput2 by shift-space to type a Japanese name. Of course, while you are typing Japanese, Compose does not make sense; but the user should not have to go into a menu and switch stuff to be able to type a word of Japanese in the French text! > mlterm can input mixture of (for example) Japanese, Chinese, and I'll have a look at it. > > * The locale should bear no influence on whether an input method is used. > > I think this can be achieved in toolkit level, so that application > developers don't need to know about XIM. (Otherwise, because very > few developers know about XIM, very few application softwares will > support XIM.) At least Qt3 has good support for XIM, apparently. :-) But it still enforces those stupid restrictions. David Monniaux http://www.di.ens.fr/~monniaux Laboratoire d'informatique de l'�cole Normale Sup�rieure, Paris, France _______________________________________________ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
