Re: Re: [m17n] No compose characters possible with asian language setting
Lars Dɪᴇᴄᴋᴏᴡ <[email protected]>
| Newsgroups | gmane.linux.suse.m17n |
|---|---|
| Message-ID | <[email protected]> |
Mike FABIAN ✍: > Compose *does* work with scim for quite a while now. I certainly don't see it; the intertubes have complaints from other users to back up my position. I am very interested in why it works for you. $ rpm -qa|ack 's[ck]im'|sort scim-1.4.7-181.1.x86_64 scim-anthy-1.2.7-6.1.x86_64 scim-pinyin-0.5.91.20060705-273.2.x86_64 scim-pinyin-skim-0.5.91.20060705-273.2.x86_64 scim-qtimm-0.9.4-278.2.x86_64 scim-tomoe-0.6.0-4.1.x86_64 skim-1.4.5-269.2.x86_64 $ env|sort|ack IM GTK_IM_MODULE=scim QT_IM_MODULE=scim QT_IM_SWITCHER=imsw-multi XMODIFIERS=@im=SCIM The Compose key does not work in any application unless I unset those variables first. Then, of course, scim does not work. But I want to be able to use both in the same application; uim allows for this. > One could also ready the compose table at runtime, but that would > cost a little bit of performance. That's definitely the way to go. The original Compose feature reads the customisations in my ~/.XCompose file, and so should any emulation thereof.
signature.asc
(application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEABECAAYFAksBuOAACgkQFtlTdOX00Hr1RQCeJjIIGJ8mPaU3Pd9cvL7thaBE +ecAn0ZA2FaLbZ0akMQNi4n4FPkzm3g7 =tsvX -----END PGP SIGNATURE-----