Comment 7 for bug 107391

Ming Hua wrote:
> Hi David,
>
> I need a clarification about the situation -- does XIM mode work for
> you? To test, modify you .xsession (as you seem to be using .xsession)
> to add:
>
> XMODIFIERS="@im=SCIM"
> GTK_IM_MODULE="xim"
> export XMODIFIERS
> export GTK_IM_MODULE
> scim -d
>
> And then restart X. Now in GTK apps such as gedit, you should see "X
> Input Method" selected in the right-click menu. Now if scim still
> doesn't work, we can continue to investigate the socket issue.
I did that, except that I set the env variables in a terminal (I removed
my .xsession file first, of course), and it does what it is supposed to
do (that is if I choose the input system, xim is set as a default). Note
that I still somtimes problems with software (they launch but hang; it
hangs at a different system call, though, according to strace for the
launched application).

Anyway, when I want to use japanese input (anthy system), it still fails
when I try to convert the kana to kanji.

I have to confess though I am a bit confused: what does it mean to set
XMODIFIERS to SCIM, but GTK_IM_MODULE to xim ? What is the connection
between scim and xim ? (I thought scim was a "better" xim, eg they
provide the same functionality).
>
> As for the debug package, sorry scim still doesn't provide a debug
> symbol package yet. I'd like to give you a package to test with debug
> symbol included (maybe also a new upstream version), but let's clarify
> some things first.
I tried to install it by myself from sources, but there seems to be a
bug in they autoconf/automake scripts which prevents me from installing
it in my $HOME (I do not have root access to this machine).

David