-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > However, this does not work for asian input methods. Especially the > > asian IMs are the ones which depend on the locale. They shouldn't > > do it. > > That's why I suggest my way. I have one UXTerm for English which to > not activate IM. I can have another UXTerm running on the same X > screen from my menu for Japanese which activate IM upon SHIFT-SPACE. > > Did you tried my way and talking? > > > http://qref.sourceforge.net/Debian/reference/ch-tune.en.html#s-x-cjk
I am still doing it and I'm not happy with it at all. If I have to input multiple languages in the same document / application - for example chinese, english, german -, i currently have to start it from a chinese terminal to get chinese input method, then save the document, close teh application, start the same application again from my normal english system, open the document again and type english (and if I change the keyboard settings on the fly - german). This is crazy. I want to change my input method between western / asian or even between asian on the fly without the need of starting multiple instances and reopening / closing the document all the time. It's even worse when I use ICQ to chat with my buddies. Some are chinese, some are german. If I want to input chinese, i cannot input german at the same time. very unconvenient if you are chatting with two budies at the same time and they use different languages. The only solution for this is: use unicode (utf-8) and have an IM which can switch between different languages but uses unicode in the background. SCIM does that but is still lacking canna support for japanese and a few useful input methods. > > > So, instead of trying to work around the problem by changing your > > individual system, we should convice the programmers of these > > applications in question, not to depend on the locale setting, but > > use a switch in the application configuration to choose the proper > > input method. > > Mlterm address this issue this way so does some other terminal > programs. I know. But I'm not only using terminal based apps, but merely graphical apps. > But that beat some good thing about locale. Menu actually fill in > gap. only if you need terminal based apps and only want to use one charset at the time. > > Unfortunately openoffice.org goes in the same wrong direction, by > > requiring the user to use a chinese locale setting to input > > chinese... that's nuts! Obviously the developers didn't think of > > people who have to deal with more than one language... :( > > So why not set 2 openoffice menu (i.e., invocation commands) for > Chinese and English. You can enen set up one system with basically > chinese environment but also specify English messages. Then program > will be IM aware but easy on English reader. that's what I'm currently doing. but as said, when I start oo.o in chinese mode, I can type english and chinese, yes. But I cannot change to other western languages on the fly because the IM program occupies my keyboard and overrides the x-keyboard or - in my case - KDE. (currently all IM programs I know are only usable with a native us-english keyboard layout - this is another thing to work on. The IM program should integrate with the xserver, so that you can use any keyboard layout as the base layout and switch to the IM when you need it.) > I think compose key sequences overrap with IM key sequences. in some apps yes. > > Arne GÃtje (éçè) <[EMAIL PROTECTED]> > > It looks like your name comes up OK in my ja_JP.eucJP locale :-) I'm using utf-8. if eucJP uses the same codepoints, there you go... ;) Cheers Arne - -- Arne GÃtje (éçè) <[EMAIL PROTECTED]> PGP/GnuPG key: 1024D/685D1E8C Fingerprint: 2056 F6B7 DEA8 B478 311F 1C34 6E9F D06E 685D 1E8C Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/3nyHbp/QbmhdHowRAqLtAJ0cuz2pnxg2v7q1kYougS1vvppKcwCfUhUU zCqVsOpp9wWTS7ykHNqM1xI= =eAs6 -----END PGP SIGNATURE-----