Bug 129468

Summary:	XIM preedit broken in kbabel with recent qt
Product:	[Unmaintained] kbabel	Reporter:	Jens Petersen <petersen>
Component:	general	Assignee:	Stanislav Visnovsky <visnovsky>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	cfeck, mueller, samjnaa
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	qt-x11-free-3.3.6-qt-x11-immodule-unified-qt3.3.5-20060318-resetinputcontext.patch

Description Jens Petersen 2006-06-20 08:56:06 UTC

Version:            (using KDE KDE 3.5.3)
Installed from:    Fedora RPMs
OS:                Linux

It is not possible to input Japanese and other Asian languages that
use XIM preedit with recent qt (>=3.3.5).  Preedit input cannot be
made or committed to kbabel widgets.

This is reproducible on Fedora Core 5 (kde-3.5.1 and qt-3.3.5) and later.
Fedora Core 4 (kde-3.4.0,qt-3.3.4) is ok.

[Note Fedora Core has a patch on qt to enable immodules, but I tested both
qt-3.3.5 and qt-3.3.6 without the immodule patches on
FC5 and still kbabel preedit does not work, so it seems indeed this
is problem is related qt itself.  I also tested qt-3.3.4 without immodule
on FC4 and kbabel preedit still works ok.
Not using on-spot-input seems to be the only workaround for newer qt.]

Comment 1 Nicolas Goutte 2006-06-24 13:30:03 UTC

See also bug #123225

Comment 2 Jens Petersen 2006-06-30 11:14:34 UTC

Than Ngo found that this is caused by all the resetInputContext()'s
in src/widgets/qtextedit.cpp.

Comment 3 Mike FABIAN 2007-01-03 15:31:28 UTC

This problem can be reproduced on openSUSE 10.2 with qt3-3.3.7 as well.

Comment 4 Jens Petersen 2007-01-04 00:24:00 UTC

Created attachment 19096 [details]
qt-x11-free-3.3.6-qt-x11-immodule-unified-qt3.3.5-20060318-resetinputcontext.patch

Here is actual patch.

Comment 5 Shriramana Sharma 2007-01-15 15:24:04 UTC

@Jens: Fedora Core 6 has fixed this bug. You may want to try that.

Comment 6 Christoph Feck 2011-06-26 14:03:52 UTC

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.