Enable SCIM render deadkeys useless in KDE/Qt apps
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SCIM |
Unknown
|
Unknown
|
|||
kdebase (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
scim (Debian) |
Fix Released
|
Unknown
|
|||
scim (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
scim-bridge (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: scim
Background
=========
I saw similar bugs, they talk about problems in KDE session or in old versions of Ubuntu.
This one is about
- running KDE programs under Gnome session
- with SCIM enabled for complex character entry
- in non asian locale
- in the last Gutsy version
I was using Feisty and Feisty works well, but Gutsy not, this is a lot of backward steps.
The Problem
=========
The problem is:
I installed asian language support for Chinese and Japanese. Then marked the field "Enable support to enter complex characters".
Then restarted the machine and tried to write Chinese and Japanese. The first issues was we're unable to use SCIM, and unable to write accents, cause dead keys are broken. It means you press the accent key like ~ and then the vowel a expecting ã as a result but getting ~a instead. OK, I started to read about a solution and found we must change:
GTK_IM_MODULE=xim
QT_IM_MODULE=xim
for
GTK_IM_
QT_IM_MODULE=
Of course I installed scim-bridge-
But the solution just worked for Gnome applications. Now i can write chinese and accents in gnome apps like gedit. In KDE applications the problem persists, it does not recognize dead keys, and I can just write english and chinese, but not spanish or portuguese in KDE apps. That turn those applications useless for productive work.
Changed in scim: | |
status: | Unknown → Confirmed |
Changed in scim: | |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in scim (Debian): | |
status: | Confirmed → Fix Released |
The "deadkeys not working with SCIM" is a well-known bug, and have been somehow mitigated in gutsy by the change of /FrontEnd/ X11/Dynamic setting.
Your problem is the result of multiple bugs, including language-selector's configurations for input methods, scim's im-switch setting (I suspect that's the reason your system worked for feisty but not for gutsy, if you used your old $HOME from feisty), as well as scim and scim-bridge. To be honest, I don't think it's wise to associate this bug to multiple packages, but I'm not going to change that.