Version: (using KDE KDE 3.5.1) Installed from: Gentoo Packages Compiler: g++ 3.4.5 OS: Linux Can't write CJK characters with SCIM. Tested with scim-anthy, scim-hangul. but nothing works :(
Can you enter CJK characters in non-KDE apps?
Yes. can enter CJK characters in every apps that supports XIM (except kbabel)
Have you removed the default binding for Ctrl+space key shortcut or is it a different problem?
I think it's a different problem. I can write CJK texts. but, they disappear immediately after I type them.
See also bug #129468
What is your version of qt?
I also cannot use UIM to enter Japanese and Chinese text on KBabel, while I can on other KDE and Qt applications, and GTK and X applications. The same symptom as Park J. K. describes, what I type with the input method immediately disappears. I had this problem in KDE 3.5.0 to 3.5.3 (all KDE versions I've used), using Slackware 10.1-10.2. I had a similar problem with the application KVirc <http://www.kvirc.net>, because the custom text widget it implemented did not handle the im{Start, Compose, End}Event correctly. I read that KBabel may also implement its own text widget. If the cause of this problem is similar, the patches on http://bugtrack.kvirc.omnikron.net/view.php?id=287 may be helpful for fixing it.
A workaround for this is to use OverTheSpot Xinput style. You can make kbabel automatically run with this by editing its KMenu entry command to: kbabel %i %m --inputstyle overthespot -caption "%c" %U
This problem can be reproduced on openSUSE 10.2 with qt3-3.3.7 as well.
I can reproduce this issue on Kubuntu 7.04 with KBabel 1.11.4 and KDE 3.5.6 The workaround above does not help on my system. I have disabled the conflict shortcut already. I found this issue only in KBabel. Other KDE apps accept Chinese input happily.
does KAider (http://techbase.kde.org/Projects/Summer_of_Code/2007/Projects/KAider) work for you?
KBabel is no longer maintained, please use the KDE 4 translator's tool called "Lokalize" instead. For more information, please visit http://userbase.kde.org/Lokalize If this is a bug which is also present in Lokalize, please add a comment so that I can reassign the bug the the Lokalize authors.