On Mon, Apr 09, 2007 at 04:32:47PM +0200, Toni Mueller wrote: > > Hi, > > On Thu, 29.03.2007 at 01:47:24 +0900, Osamu Aoki <[EMAIL PROTECTED]> wrote: > > Have you read README.Debian for SCIM and configured > > /SupportedUnicodeLocales value? > > after reading this, I configured > > /SupportedUnicodeLocales = > de_DE.utf8,en_US.UTF-8,en_GB.UTF_8,fr_FR.UTF-8,zh_CN.UTF-8 > > in the hope to solve the problem, but quite contrary to my expectation, > this effectively killed my ability to switch input methods. So, I > reverted the change and resorted to my wrapper script. Currently, I > start all applications that I want to use scim with using this script: > > ------ cut > #!/bin/sh > > unset LC_MESSAGES > unset LC_COLLATE > unset LC_CTYPE > unset LC_TIME > > exec $* > ------ cut
That is because you have non-compatible encoding for these values. | $ env|grep -E '(LANG|LC_)' | LANG=de_DE.utf8 | LC_MESSAGES=C | LC_COLLATE=C | LC_CTYPE=C | LC_TIME=C You have to run program in the compatible/consistent encoding under UTF-8. If you are trying to get C like environment, I suggest LANG=de_DE.utf8 LC_MESSAGES=en_US.utf8 LC_COLLATE=en_US.utf8 LC_CTYPE=en_US.utf8 LC_TIME=en_US.utf8 I guess ... I know ja_JP.eucJP works but as written in the README.Debian "The maintainer of scim package recommends using UTF-8 locale. :-)" C is non-UTF8 locale. > This script unsets the variables I had customized, and then starts the > application in question which then only has the customized LANG > variable to work with. Yes, but now you get German messages... Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
