Scim doesn't work in xterm if you're using a locale that isn't listed in /etc/scim/global which currently lists only en_US.UTF-8. GTK apps don't seem to be affected from this problem which makes it so confusing, because you see that Scim is working fine everywhere, just not in xterm. I don't know the purpose of this configuration setting. Why would you want to restrict Scim to certain locales only? If I don't want to use Scim I don't launch it. If there's a setting that will allow all *.UTF-8 locales to be accepted, Gentoo should use that by default. Otherwise it may be possible to patch out the respective check. At the very least the ebuild should print an elog that informs the user that he'll have to add all of his required locales to /etc/scim/global if he wants Scim to work in xterm (and probably other plain X11 apps, too). Reproducible: Always Steps to Reproduce: 1. LC_ALL=de_DE.UTF-8 uxterm 2. Try to use Scim => doesn't work (assuming de_DE.UTF-8 is not listed in /etc/scim/global) 3. LC_ALL=en_US.UTF-8 uxterm 4. Scim works 5. Add de_DE.UTF-8 to /etc/scim/global 6. LC_ALL=de_DE.UTF-8 uxterm 7. Scim now works here, too.
"Scim works" in my case means "I can input Japanese using Scim-anthy"
I can confirm this issue. However with correct setting starting xterm takes a lot of time because it tries to list all fonts with exotic charsets via X11.
Patch #242 - 2009/2/15 * change default XIM font from "*" to "fixed" to improve startup time in zh_CN.UTF-8 locale (Mike Fabian, SuSE Bugzilla #464930).
Still valid with app-i18n/scim-1.4.9 ?
Yes, still the same problem in app-i18n/scim-1.4.9.
But it's per design, I mean, it's really an upstream problem, please read the following links: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404546 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478145 I have also checked other distributions packages (opensuse, fedora, debian, ubuntu and mandriva) and I haven't found any fix for it. I think that we could "fix" this simply adding an "elog" entry in ebuild for informing scim users about what to do and how to configure this Do you know about a better solution (or patch)? Thanks
elog message added.
