https://bugzilla.novell.com/show_bug.cgi?id=230217
Summary: kbabel does not allow skim to input Chinese chars Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: gubotruth@gmail.com QAContact: qa@suse.de CC: zsu@novell.com
openSUSE 10.2 x86_64, KDE environment, all packages from the DVD.
With scim/skim ok in all other K apps, Kbabel does not allow skim to input Chinese chars in its msgstr field. With Eng keyboard on, everything's good.
However, with a Chinese IM on, it seems that every time I press a key, an IMEnd signal is sent. For instance, with pinyin on, I press "wo" in order to form a char query, it strangely runs into this way(from shell):
sending IMStart with 0 chars to 0x9fdce0 sending IMCompose to 0x9fdce0 with 1 chars, cpos=0, sellen=1, text=我 sending IMCompose to 0x9fdce0 with 1 chars, cpos=1, sellen=0, text=我 sending IMEnd with 0 chars to 0x9fdce0, text= sending IMStart with 0 chars to 0x9fdce0 sending IMCompose to 0x9fdce0 with 1 chars, cpos=0, sellen=1, text=哦 sending IMCompose to 0x9fdce0 with 1 chars, cpos=1, sellen=0, text=哦 sending IMEnd with 0 chars to 0x9fdce0, text=
And there will be no char to be display in Kbabel.
This bug has been there since SUSE 10.1, also existing in SLE 10 series.
https://bugzilla.novell.com/show_bug.cgi?id=230217
stbinner@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |mfabian@novell.com
------- Comment #1 from stbinner@novell.com 2006-12-26 05:44 MST ------- Mike, can you help? :-)
https://bugzilla.novell.com/show_bug.cgi?id=230217
mfabian@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #2 from mfabian@novell.com 2007-01-02 11:44 MST ------- I can reproduce that on openSUSE 10.2.
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #3 from mfabian@novell.com 2007-01-02 12:24 MST ------- The Compose support built into SCIM still works.
I thought this bug might be related to bug #59633 but as Compose still works this might be an unrelated problem.
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #4 from mfabian@novell.com 2007-01-02 12:37 MST ------- It doesn't work with QT_IM_MODULE=xim either, no matter whether SCIM or some other XIM server like kinput2 is used. I.e.
XMODIFIERS="@im=kinput2" QT_IM_MODULE=xim kbabel ja.po
doesn't work either.
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #5 from mfabian@novell.com 2007-01-02 12:58 MST ------- A workaround is described in
http://lists.sourceforge.jp/mailman/archives/scim-imengine-dev/2006-April/00...
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #6 from mfabian@novell.com 2007-01-02 13:00 MST ------- The workaround is:
Start /usr/lib/qt3/bin/qtconfig and select "OverTheSpot" and then use XIM:
QT_IM_MODULE=xim kbabel ja.po
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #7 from mfabian@novell.com 2007-01-03 07:11 MST ------- Of course the workaround mentioned in comment #6 makes the input more inconvenient in many other KDE/Qt applications because all Qt applications use "OverTheSpot" by default if this is set in qtconfig. And for applictions where it works, "OnTheSpot" is much more convenient.
Therefore it is better to use this workaround only for Kbabel, which can be achieved by setting the inputstyle not in qtconfig but with a command line option for Kbabel instead. Like this:
QT_IM_MODULE=xim XMODIFIERS=@im=SCIM kbabel --inputstyle overthespot ja.po
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #8 from mfabian@novell.com 2007-01-03 07:24 MST ------- Here is the upstream bug report:
http://bugs.kde.org/show_bug.cgi?id=129468
https://bugzilla.novell.com/show_bug.cgi?id=230217
samjnaa@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |samjnaa@gmail.com
------- Comment #9 from samjnaa@gmail.com 2007-01-15 07:20 MST ------- http://bugs.kde.org/attachment.cgi?id=19096&action=view gives the patch. Please can we have updated packages of qt (I presume it's really a qt bug and not a kbabel bug)? This is seriously preventing usage of KBabel on openSUSE 10.2 for translation work to Asian languages. Fedora Core 6 has fixed this bug, and I don't see any reason a fixed package for openSUSE 10.2 cannot be released.
Thanks in advance.
https://bugzilla.novell.com/show_bug.cgi?id=230217
------- Comment #10 from mfabian@novell.com 2007-01-16 12:19 MST ------- It's not clear whether it is really a qt bug. As it works fine, it could be a bug in Kbabel. Maybe the patch for Qt is just a workaround.
https://bugzilla.novell.com/show_bug.cgi?id=230217
Mike Fabian mfabian@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mfabian@novell.com |hvogel@novell.com
https://bugzilla.novell.com/show_bug.cgi?id=230217
User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=230217#c11
Andreas Jaeger aj@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX
--- Comment #11 from Andreas Jaeger aj@novell.com 2009-02-25 06:52:56 MST --- Why was this bug never followed up?
I'm closing this as WONTFIX for 10.2. If the bug still exists in 11.1, please reopen.