Hi, thjis is continuation of http://bugs.debian.org/349397
Just for the record: >From UIM official web page http://uim.freedesktop.org/wiki/WhatsUIM | What applications can I use with uim? | | * All X applications. (You can use them with uim-xim.) | | * Gtk+ applications such as gedit. There are two way to use uim. Through | uim gtk-immodule directly, or through xim immodule. We recommend using | uim through gtk immodule directly. | | * All qt applications. There are two ways to use uim, through XIM or | qt-immodule. If you want to uim with qt-immodule, you will need [WWW]a | patch now. | | * All console applications. (You can use them with uim-fep.) | | * Emacs (You can use it with uim-el). So UIM, we should use gtk immodule directly :-) as we do now. >From SCIM official wiki page http://www.scim-im.org/wiki/documentation/installation_and_configuration/all/system_configuration | | export [EMAIL PROTECTED] #case matters for this variable! | export GTK_IM_MODULE=xim | export QT_IM_MODULE=xim | ... | Because the XIM protocol has a lot of limitations (for example, | it may freeze your entire X when something goes wrong with the input | method server), this combination of settings is generally not | recommended. | ... [then it goes...] | export [EMAIL PROTECTED] #case matters for this variable! | export GTK_IM_MODULE=scim | export QT_IM_MODULE=scim | | XMODIFIERS will be used in all X applications (via an older XIM | protocol), such as xpdf. It does not have other more advanced input | method abstract layers. | | Default input methods of GTK/Qt im-module are set by the last two lines. | Please set them as above. Even if the necessary support does not exist, | these two lines should have no side effects at all on your system. | | And there are 3 pages of how to disable them such as | [EMAIL PROTECTED] emacs | See page linked from: http://www.scim-im.org/wiki/faq/general/is_it_possible_to_prevent_ctrl_space_from_activating_scim_in_some_apps So it sounds like we should do what is best for SCIM is the same as UIM case, [EMAIL PROTECTED] GTK_IM_MODULE=scim But what is the problem: SCIM gtk IM Module and Firefox/Mozilla/Acrobat Reader 7 or any other Gtk+2 based C++ applications are binary incompatible with each other if they are not compiled with the same branches of gcc/glibc. This is the reason to use GTK_IM_MODULE=xim for some application. Since all free software on debian is compiled under the same same branches of gcc/glibc, above issue is non-issue. For proprietary software, GTK_IM_MODULE=xim ./firefox-installer type of starting will solve it. If Ming agrees or be quiet, I will switch default to GTK_IM_MODULE=scim. By the time of release C++ ABI change should be finished. ISince I do not want to flip-flop on this, I will keep this open to collect opinion. Regards, Osamu PS: I CCed all parties involved. Sorry if you get duplicates. I think Muto-san will get it anyway being im-switch maintainer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
