[cw-discuss] How to use IME in MS Office 2003?

[Gernot Hassenpflug]

On Feb 18, 2008 10:34 PM, Aric Stewart <aric at codeweavers.com> wrote:
>
> Which XIM are you trying to use. for Japanese i would recommend kinput2.

Hello,
Thank you for confirming that I should be able to use a normal X input
method rather than the MS IME.
I usually use UIM and Anthy under GNOME, but according to your
recommendations as a test I set up kinput2 with canna. It works using
Shift-space to change to hiragana mode in the terminal. However, see
below.

> You have to make sure your locale is set to ja_JP.UTF-8  and you need to
> make sure that kinput2 is working properly. This will involve having
> kinput2 and cannaserver both running.

Unfortunately, I eventually discovered I had been bitten by the locale
bug. The name of the locale must be "ja_JP.utf8" :-( At least then it
is set correctly using LC_ALL and LANG.

> Here is more information:
> http://dspnet.fr/~lonewolf/LinuxJapan/Howto_English_Japanese.html
>
> Make sure that the XMODIFIERS environment variable is set such as this
> XMODIFIERS="@im=kinput2"

OK, done.

> Then you can test input first using notepad.  run ~/cxoffice/bin/wine
> notepad
> then try inputing Japanese into notepad.  Then it should also work in MS
> Office 2003.

Unfortunately shift-space does nothing in notepad, even though the
command "locale" in the terminal returns ja_JP.utf8, and XMODIFIERS is
exported. UIM/Canna works in kterm with shift-space still (i.e., GNOME
UIM is active).

I then solved the problem. running "kinput2-canna &" , then exporting
XMODIFIERS="@im=kinput2" and then opening "kterm &" where shift-space
now activated the familiar kiinput2 sub-window. Now when I ran notepad
from kterm I could input Japanese using kinput2. This is a bit like
stepping bacl 5 years in time to the Solaris systems I used to work
with at Kyoto University :-)

I suspect I might be able to continue using Anthy/UIM also, but I have
not yet worked out the magic incantations for that.

Many thanks for the tips, absolutely invaluable in helping me find a
route that works. Hopefully I've documented my steps enough to help
others too.

Best regards,
   Gernot Hassenpflug