Bug 13879 (nidev) - When I type some letter with shift key in Byeoru engine, UIM shows english capital letter.
Summary: When I type some letter with shift key in Byeoru engine, UIM shows english ca...
Status: RESOLVED FIXED
Alias: nidev
Product: UIM
Classification: Unclassified
Component: generic Scheme codes (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: uim-bugs
QA Contact:
URL: http://nidev.org
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-31 21:26 UTC by ChangBeom Yoon
Modified: 2008-01-01 10:04 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
byeoru.scm patch (1.89 KB, patch)
2007-12-31 21:33 UTC, ChangBeom Yoon
Details | Splinter Review

Description ChangBeom Yoon 2007-12-31 21:26:40 UTC
I found a problem with UIM, especially with Byeoru engine.
I built UIM at  2008-01-01 14:10:40 (GMT+9).
When I Input korean letter 'ㅏㅐㅣㅗㅜ' with shift key pressed, UIM doesn't show 'ㅏㅐㅣㅗㅜ' but 'KOLDU'.
This is strange.
I found that byeoru.scm doesn't have definition for shifted keys.
I mean, byeoru.scm only contains "shifted key" definitions for 'Q(ㅃ), W(ㅉ), E(ㄸ), R(ㄲ), T(ㅆ), O(ㅒ), P(ㅖ)'.
I'll add my patch in this report.
Thank you.

ps. sorry for my poor english.
Comment 1 ChangBeom Yoon 2007-12-31 21:33:35 UTC
Created attachment 13439 [details] [review]
byeoru.scm patch
Comment 2 Jae-hyeon Park 2008-01-01 10:04:45 UTC
I did not realize that this could be a problem for two reasons.
First, hanterm works like the present 2-beol layout in byeoru, and I
mimicked hanterm.  Second, I don't use 2-beol layout.

Today, I found that MS-Windows IME maps <Shift>k to "ㅏ", and this
seems to be reasonable.  On the other hand, I am afraid that there are
users who are used to the hanterm-like behavior.  As a compromise, I
added another 2-beol layout in the style of Windows IME, and set it as
the default.  This should fix the problem.

Thank you very much for your report and patch.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.