Hi, Shin and Kent
hangul jamo sequences like LLV(choseong1+choseong2+jungseong) are already
normalized by NFC partial jamo combination into (L)(LV).
If we do not modify current version of NFC jamo handling behavior,
we should add some (L)(LV) <==> LLV equivalence for correct rendering
implementation.
Another partial jamo combination is also found in
NFC's handling of (choseong+jongseong+ ancient jongseong) sequence.
: LVFa ---> (LV)(Fa)
Martin Duerst had said the latter normaliation may not be a fault, but
(LV)(Fa) is just an intermediate form of hangul syllable.
(Martin, correct me if i am misrepresent you ).
Martin and Mark,would you comment on these partial jamo combination ?
Regards,
Soobok Lee
----- Original Message -----
From: "Jungshik Shin"
To: "Soobok Lee"
Cc: "Kent Karlsson" ;
Sent: Wednesday, November 14, 2001 2:08 PM
Subject: [idn] Re: new hangul nameprep issue
> On Wed, 14 Nov 2001, Soobok Lee wrote:
>
> Hi,
>
> > Thanks for your valuable contributions. I promise to investigate
> > it thoroughly.
>
> > First, please test the enclosed link in IE 5.0, 5.5, 6.0 in Win 2K
> > and Win XP.
>
> I'm sure MS IE 5.0/5.5 doesn't work. As I wrote earlier,
> even MS IE 6.0 under Korean MS Office XP wouldn't work for sample
> cases in your test page (MS hasn't yet added support of generic Hangul
> syllable formation stipulated in TUS 3.0 for modern Korean - which
> can be represented by precomposed Hangul syllables at U+AC00 block -
> although it supports that for Middle Korean.) However, two test cases
> in my test page at are likely to work
> in MS IE 6.0 + Korean MS Office XP/Korean MS Windows XP.
>
> > That contains some javascript codes to make on-the-fly html containing
> > the 3 sequences you give me.
> > In my win2k and IE 6.0 (english version) rendering,
> > syllable breaks are assumed in the choseong sequence.
> > I will test this link in other platforms.
>
> > http://164.124.123.207/etc/f8.html
>
> BTW, I'm afraid your javascript(ECMAscript) is not compliant to
> ECMA-262
> (ftp://ftp.ecma.ch/ecma-st/Ecma-262.pdf) and ISO/IEC 16262. unescape()
> is not a part of the standard (see section B.2 of ECMA-262) so that
> unescaping "%uhhhh" is not supported by Netscape although it's
> supported
> by MS IE. You can simply use "\uhhhh" to include Unicode characters in
> a string (see section 7.8.4 of ECMA-262)
>
> Regards,
>
> Jungshik Shin
>
>
>
>
![]()
![]()
![]()
![]()