Bug 137412

Summary:	[qt] cannot handle Key event and IM event together correctly
Product:	[Fedora] Fedora	Reporter:	Leon Ho <llch>
Component:	qt	Assignee:	Than Ngo <than>
Status:	CLOSED RAWHIDE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	eng-i18n-bugs
Target Milestone:	---	Keywords:	i18n
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-11-09 15:43:35 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	125997, 137149

Description Leon Ho 2004-10-28 11:27:22 UTC

Description of problem:
Qt cannot handle Key event and IM event together correctly. The order
will swap around when they posted together.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. login into KDE using ko_KR.UTF-8
2. kedit
3. shift-space
4. rkeksk<space>

  
Actual results:
output will be rkek<space>sk in hangul

Expected results:
output will be rkeksk<space> in hangul

Additional info:

Comment 1 Leon Ho 2004-11-01 11:40:22 UTC

Look like it is a problem on over-the-spot method in current im module. I am
contacting the developer now to try to get some fixes on qt immodule.

However we should move back to on-the-spot now as it has improved since we
visited a while ago. The method handles this situation correctly, plus
on-the-spot is using application to render the preedit area. I have tested with
input methods they are have better behavior.

Than, can we s/Over The Spot/On The Spot/ in /usr/lib/qt-3.3/etc/settings/qtrc
in redhat-artwork and qt package for RHEL4?

Thanks.

Comment 2 Than Ngo 2004-11-02 10:34:56 UTC

sure, i will do it in next rebuild. please let me know if the bug in
qt immodule is fixed. thanks

Comment 3 Than Ngo 2004-11-09 15:43:35 UTC

it's now fixed in redhat-artwork-0.119-1.1E.