SCIM and XIM - 2008-03-12 10:53:16 SCIM and XIMAfter a long time struggling with SCIM and XIM in Ubuntu and finally switching to UIM, I managed to solve my headache. It seems the reason some Americans were not suffering the same issues I had finally lead to a locale issue.en_US or en_GBSCIM will by default support en_US in Ubuntu, but for anyone outside of the US, we have to add manually this support by editing the ~/.scim/global file. This isn't a problem, but what gave me a one year headache was the way that SCIM interprets this file. Just adding your local is not necessarily enough.Beware the spaceYou see for whatever reason, I had: "/SupportedUnicodeLocales = en_US.UTF-8, en_GB.UTF-8"
And no luck. What I needed was:
"/SupportedUnicodeLocales = en_US.UTF-8,en_GB.UTF-8"
Note the lack of space after the first locale. Annoyingly, is SCIM finds a space here, it will them proceed to ignore everything else on the line. This is a shame as most other systems are more forgiving in their config file parsing and the space certainly make the file more readable.What should I add?If you're having the same problem, run the "locale" command at the terminal, find the line that starts with LANG=, in my case it's LANG=en_GB.UTF-8. Then add that locale into your global file (in homedir/.scim). Should sort the problem of SCIM not working in non GTK or QT apps. |
