Bug 103544

Summary: Korean input is wrong.
Product: Red Hat Enterprise Linux 3 Reporter: David Joo <djoo>
Component: gtkhtml3Assignee: Jeremy Katz <katzj>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: eng-i18n-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:58:23 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:

Description David Joo 2003-09-02 03:03:21 UTC
Description of problem: When Korean is being input, it doesn't show what is
being typed. Also, when it's all typed, the order of characters are different
Also the position of cursor is worng

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


How reproducible:
Every time

Steps to Reproduce:
1. Start Evolution
2. Try to write a new email with Korean
3. 
    
Actual results:
When you type "rkskekfk" you won't be able to see the result of "rk" until you
have "sk" being entered. Also after you enter "rkskekfk", (in UTF-8, it will
look something like "ëë¼ë¤ê°". Also the position of cursor is in the middle
instead of end of the last character.

Expected results:
The above input should look something like "ê°ëë¤ë¼"

(You should be able to see these Korean output if you have the browser to have
UTF-8)

Additional info:
To test this better way, please set the /etc/sysconfig/i18n to have following entry.
LANG=ko_KR.eucKR
LC_MESSAGES="en_US.UTF-8"

Then ami's menu will be in English.

To show this bug, you need to set ami in specific way.
KBD Type is : 2bul
INPUT OPTION is : Committed by characters

then save it. but do not close it
if you close it, you won't be able to use ami

To toggle between Korean and English, use, shift+space key

Comment 1 Jeremy Katz 2003-09-02 19:19:07 UTC

*** This bug has been marked as a duplicate of 91481 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:58:23 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.