I am working my way true the "CJK Support in Suse Linux" Manual. I have installed the japanese fonts (checked by the 2.1.1 example). Now I started the section 3 Input. If I do the examples 3.1.3.1 and 3.1.3.1.1 (with gvim) it doesn't work as described: - Shift-Space don't work - I have japanese items but I cannot enter japanese text Are their more descriptions available how to set up the environment? Also if I start with the example 3.1.3.1. a strange message "warning yubin7 ... " pops up. ??? Thanks for any comment. -- --------------------------------------------------- Mit freundlichen Gruessen / Best regards Ulrich Groh ----------------------------------------------------
ugroh@t-online.de (Ulrich Groh) writes:
I am working my way true the "CJK Support in Suse Linux" Manual. I have installed the japanese fonts (checked by the 2.1.1 example). Now I started the section 3 Input.
If I do the examples 3.1.3.1 and 3.1.3.1.1 (with gvim)
I.e. you did start kinput2 like ~$ LANG=ja_JP kinput2 -xim -kinput -canna &
it doesn't work as described:
- Shift-Space don't work - I have japanese items but I cannot enter japanese text
To be able to do Japanese input, you need LC_CTYPE=ja_JP.eucJP (or the alias LC_CTYPE=ja_JP). But as you say you have Japanese menus, i.e. it looks like you did start gvim in a Japanese locale and you probably have this already. The command 'cannastat' should list kinput2 as a client, like this: mfabian@gregory:~$ cannastat Connected to unix Canna Server (Ver. 3.5) Total connecting clients 1 USER_NAME ID NO U_CX C_TIME U_TIME I_TIME HOST_NAME CLIENT mfabian 0 0 3 Fri 23 11:59am 1 15 localhost kinput2 mfabian@gregory:~$ I guess you forgot to set XMODIFIERS="@im=kinput2". It must be set in the environment of the application where you want to do Japanese input. ~$ XMODIFIERS=@im=kinput2 LC_ALL=ja_JP.eucJP gvim Also please try some other applications capable of Japanese input instead of gvim, for example rxvt, to find out whether you have a problem with Japanese input in general or especially with gvim.
Are their more descriptions available how to set up the environment? Also if I start with the example 3.1.3.1. a strange message "warning yubin7 ... " pops up.
This is a warning only and can be ignored. There is a supplementary dictionary for Canna which contains Japanese postal codes. If you want it you can get it here: ftp://ftp.suse.com/pub/suse/i386/7.3/suse/j2/canna-yubin.rpm The Canna package already contains the necessary entries to use this dictionary, therefore it will be automatically used if you install the package, but if you don't have it installed, there will be a warning that this dictionary cannot be found. This doesn't do any harm, it just means that you can't use this dictionary, everything else works normally. -- Mike Fabian <mfabian@suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。
On Wednesday 28 November 2001 23:30, Mike Fabian wrote:
~$ XMODIFIERS="@im=kinput2" LC_ALL=ja_JP.eucJP gvim
Also please try some other applications capable of Japanese input instead of gvim, for example rxvt, to find out whether you have a problem with Japanese input in general or especially with gvim.
With LC_ALL=jp_JP.eucJP everything is working now (gvim, emacs, ..). You should add this to your CJK manual. Thanks. Ulrich Groh
ugroh@t-online.de (Ulrich Groh) writes:
On Wednesday 28 November 2001 23:30, Mike Fabian wrote:
~$ XMODIFIERS="@im=kinput2" LC_ALL=ja_JP.eucJP gvim
Also please try some other applications capable of Japanese input instead of gvim, for example rxvt, to find out whether you have a problem with Japanese input in general or especially with gvim.
With LC_ALL=jp_JP.eucJP everything is working now (gvim, emacs, ..). You should add this to your CJK manual.
LC_ALL is more than necessary. Actually you need only LC_CTYPE and this is mentioned in my SuSE-CJK pages in the XIM section. The important variable for XIM is only LC_CTYPE, when setting only LC_CTYPE to Japanese should work as well. With ~$ LANG=de_DE LC_CTYPE=ja_JP gvim Japanese input in gvim works for me. You can see that in the environment of gvim started with the above commandline only LC_CTYPE was set to a Japanese locale by replacing 'gvim' with the 'locale' command: ~$ LANG=de_DE LC_CTYPE=ja_JP locale LANG=de_DE LC_CTYPE=ja_JP LC_NUMERIC="de_DE" LC_TIME="de_DE" LC_COLLATE=POSIX LC_MONETARY="de_DE" LC_MESSAGES="de_DE" LC_PAPER="de_DE" LC_NAME="de_DE" LC_ADDRESS="de_DE" LC_TELEPHONE="de_DE" LC_MEASUREMENT="de_DE" LC_IDENTIFICATION="de_DE" LC_ALL= ~$ Whether you use LC_CTYPE=ja_JP or LC_CTYPE=ja_JP.eucJP doesn't matter the former is just an alias for the latter. When you use LC_ALL, you force *all* LC_* variables to this value: mfabian@gregory:~$ LC_ALL=en_US LANG=de_DE LC_CTYPE=ja_JP locale LANG=de_DE LC_CTYPE="en_US" LC_NUMERIC="en_US" LC_TIME="en_US" LC_COLLATE="en_US" LC_MONETARY="en_US" LC_MESSAGES="en_US" LC_PAPER="en_US" LC_NAME="en_US" LC_ADDRESS="en_US" LC_TELEPHONE="en_US" LC_MEASUREMENT="en_US" LC_IDENTIFICATION="en_US" LC_ALL=en_US mfabian@gregory:~$ With this setting, Japanese input using XIM would not work, LC_ALL=en_US overrides LC_CTYPE=ja_JP here. These locale specific variables are already documented in the info pages of glibc, but maybe I should add some notes to my SuSE-CJK pages as well. -- Mike Fabian <mfabian@suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。
participants (2)
-
Mike Fabian -
ugroh＠t-online.de