>Let's assume you use kinput2 for example.
>It should work if you use
> export XMODIFIERS="@im=kinput2"
> LANG=ja_JP LC_ALL=ja_JP kinput2 -xim -kinput -canna &
> LANG=en_US.UTF-8 LC_CTYPE=ja_JP.UTF-8
program-where-you-want-to-input Japanese
thanks for the tips, but what I really wanted was use japanese/other
languages
input methods, but not be in a ja_JP locale. (just the default local
en_US.UTF-8)
(Also I was hoping it could be done in an application that was already
running,
for example I would start off in VIQR, then maybe do some korean input,
then
switch to XIM/kinput2/canna, all in the original gedit window...)
im curious why I would set the LC_CYPTE to ja_JP.UTF-8,
why would that be any different than en_US.UTF-8 when the
LANG is en_US.UTF-8. I'm not worried about japanese collation
i'd prefer to use a default "unicode collation".
>And you should probably better start the kinput2 server itself in
>ja_JP.eucJP locale. But that doesn't mean that the client program
>where you want to input Japanese also has to run in ja_JP.eucJP, you
>can just as well run the client with LC_CTYPE=ja_JP.UTF-8.
Im curious, why do you suggest that kinput2 should be run with
eucJP as its startup encoding? Does it have bugs if that is not the
case?
Anyway, I was mostly hoping for an automated way of getting into
and out of japanese input mode using the right-click context menu...
��TL_"���|���'jYez���
܆+ކ�i����Y�)�Ɗ��X����
