[g11n-ko-discuss] [Fwd: Re: [i18n-discuss] Please review the onepager for "Korean Input Method Enhancement" project]

[Ienup Sung]

-------- Original Message --------
Subject: Re: [i18n-discuss] Please review the onepager for "Korean Input 
Method Enhancement" project
Date: Tue, 22 Jan 2008 12:18:13 -0800
From: Ienup Sung <Ienup.Sung at Sun.COM>
Reply-To: Ienup.Sung at Sun.COM
Organization: Sun Microsystems, Inc.
To: Aijin Kim <Aijin.Kim at Sun.COM>
CC: g11n-ko-discuss at sun.com, gto-ext at Sun.COM, Jeffrey Chen <Pu.Chen at Sun.COM>
References: <479405FC.2000402 at Sun.COM>

Hi Kim, Aijin-si,

Thanks first of all for doing this good project. I've also cc'd
g11n-ko-discuss mailing list at OpenSolaris.org.

I have a few questions to ask on the project:

It appears to me that this project will replace the existing so-called
KOLE with HangulLE at Nevada while supply both at S10UR, correct?

What are the compatibility issues in terms of user's usage perspecitive?
Are all existing input modes and key sequences and so on be the same and
supported with new HangulLE?

With HangulLE, would you or how do you support user-defined characters?

How the Hanja Tool and existing user Hangul-Hanja dictionary plays their
roles with new HangulLE?

In Korean EUC locale with KS C 5601-1987 fonts, as you know, there are five
characters that are not in the KS C 5601-1987 character set while in
the course of composition of Hangul syllables, do required to be
present/visible at preedit window as visual feedback. They are 뢔, 쌰, 쎼,
쓔, and 쬬 (in UTF-8) and in our Korean EUC fonts, the glyphs for them are
intentionally added at user-defined area between 0x497a and 0x497e so that
during preedit, those glyphs will be shown as user visual feedback.
Would such characters also be supported at the new HangulLE for
the Korean EUC locale?

In the section 4.1.4. (1), the one pager describes the auto composition when
vowel starts a syllable. Would such auto auto composition a feature that can
be turned on and off and if so what would be the switch? In the (2),
would step Hangul-to-Hanja conversion still be supported using Ctrl+N and P?

In the section 4.1.5, the aux window layout is shown as:

+-------------------------------------------------------------------+
| Mode Switch | Hanja | Full/Half  | Virtual Keyboard | Properties  |
+-------------------------------------------------------------------+

which appears reversed "Hanja" and "Full/Half" of the current aux window.
Is there any specific reason why that has to be that way possibly increasing
confusion among users? Also, would it be possible to change the "Hanja"
image at the aux window? (If necessary, I could supply a better image
too. Please let me know.)

Would you please specify OSR numbers for Sun internal reviewers?

It appears to me that this project will require an ARC approval as
a fast track mainly due to imported interface of libhangul. For that,
the section 4.5 would need a little bit of update also possibly based on
the answers to the questions above.

Ienup

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: korean_im_enhancement_onepager.txt
Url: http://mail.opensolaris.org/pipermail/g11n-ko-discuss/attachments/20080122/5c8888e0/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: file:///tmp/is/nsmail-2.asc
Url: http://mail.opensolaris.org/pipermail/g11n-ko-discuss/attachments/20080122/5c8888e0/attachment.ksh