Heads up! Some non-GTK, non-QT apps have a broken XIM implementation

[Arne Goetje]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

just to let you guys know that this issue exists:

it seems some applications have a broken XIM implementation, e.g.
fontforge. When "enable complex characters" is enabled in
language-selector, it will set XMODIFIERS="@im=SCIM" among other
environment variables. When this variable exists, in fontforge the
keyboard will block, regardless if scim has been activated with
CRTL+SPACE or not. Workaround: unset XMODIFIERS before calling
fontforge. This might also apply to other non-GTK and non-QT
applications. I don't think this is SCIM's fault, but a broken XIM
implementation in those applications. As this only affects some non-GTK
and non-QT apps it is independent from the actual input module being
used (scim, scim-immodule or scim-bridge).

How to test:

 * run System/Administration/Language Support
 * check the "enable complex character support" checkbox for your locale
 * relogin or reboot if relogin doesn't work
 * start any non-GTK and non-QT application
 * try to type something in that application. If the keyboard blocks,
the application is affected.
 * open a terminal window and call 'export' to check that XMODIFIERS
exists and has a value. The value should be "@im=SCIM".
 * 'unset XMODIFIERS'
 * run the application from this terminal and see if the typing now
works or not.

Workaround:

as CJK input won't work anyways for those applications, we can run the
'unset' command in a shell script prior to running the application.

Cheers
Arne
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIBbm2bp/QbmhdHowRAi+WAJ9PMyASBqQw6KGaE+DLVTnOhGAVEACggO6P
gZF6Av6bLzEuM1Zqp7kUOBg=
=vsGN
-----END PGP SIGNATURE-----