Pure X windows applications don't accept SCIM input

[Ryu Kent]

Binary package hint: scim

Ubuntu 7.04. Pure X windows applications (non GTK or QT) do not accept SCIM input of extended characters through XIM even when XMODIFIERS environment variable is set to "@im=SCIM". GTK and QT apps seem fine.

[Ming Hua (minghua)]

This seems quite strange. What locale are you using? And is this bug still reproducible in the final 7.04 release?

[Ryu Kent (ryukent)]

Thanks for the reply,

Yes this bug is very much live in the final 7.04. I've had to switch
to UIM as I'm doing Java development and SCIM is as good as useless
there.

Here's how to replicate:

Fresh install of Ubuntu 7.04. I'm using en_GB.UTF-8 locale and yes it
is registered in the global file. The problem does not seem to affect
other dists of linux.

Install SCIM and Japanese support as of:
https://help.ubuntu.com/community/Japanese_Input_and_Fonts_in_Ubuntu_7%2e04
(Which incidentally I wrote)

Now with applications such as netbeans, or anything else Java, or even
xterm, when SCIM-Anthy is selected as input method, it reverts back to
just accepting western characters. I think this is a problem with the
XIM interface connecting to SCIM. In QT apps, when SCIM is selected as
the input (right hand clicking on a lineinput box), no problems, but
when you select XIM as the input, even when SCIM is set up in XIM
mode, still nothing but direct style input.

Have tried many hours trying to fix, but no luck.

Cheers, Ryu

On 14/05/07, Ming Hua <email address hidden> wrote:
> This seems quite strange. What locale are you using? And is this bug
> still reproducible in the final 7.04 release?
>
> --
> Pure X windows applications don't accept SCIM input
> https://bugs.launchpad.net/bugs/100030
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Ming Hua (minghua)]

On Tue, May 15, 2007 at 02:42:12AM -0000, Ryu Kent wrote:
>
> Yes this bug is very much live in the final 7.04.

Thanks for the additional information, Ryu. Hope someone with more
knowledge can look at this and figure out what the problem is.

Meanwhile I'll see if I can reproduce it in Debian/Ubuntu when I have
time.

Ming
2007.05.15

[Ryu Kent (ryukent)]

RE: Bug 98890

This was the same issue but is solved in non en_US locales with the correct line in the global file. Note there must be no space after the comma when delimiting locales. en_US is not affected as it is added as default.

[Ming Hua (minghua)]

Since bug #98890 has been closed, and Ryu Kent acknowledged this is the same issue of incorrect configuration file, I'm closing this bug as well.