Re: [idn] Fw: Results of BALLOT on Five Canonical Mapping Errors

["Mark Davis" <mark.davis@jtcsv.com>]

One should not read too much into this decision. The Unicode stability
policies only permit extremely constrained changes; see:

http://www.unicode.org/standard/stability_policy.html#Normalization

Jamo mappings would not fall under those criteria.

However, Kent Karlsson has been working on additional mappings and
information for aiding in the processing of Hangul/Jamo characters. Such
mappings the UTC is open to considering, and you might contact him to find
out the status of that effort.

Mark
__________________________________
http://www.macchiato.com
►  “Eppur si muove” ◄

----- Original Message -----
From: "Soobok Lee" <lsb@postel.co.kr>
To: "James Seng" <jseng@pobox.org.sg>
Cc: "IETF/IDN WG" <idn@ops.ietf.org>
Sent: Saturday, December 07, 2002 05:17
Subject: Re: [idn] Fw: Results of BALLOT on Five Canonical Mapping Errors


>
> Thanks. I welcome Option A. This is the right decision!
>
> I hope to see Unicode 4.0 NFC also has
>  corrected version of hangul jamo processing. My concern was
>  that such false mappings become too heavily deployed and established
>  to be corrected sometime later, due to critical use in IDN identifiers.
>  But, Today, UTC decision opened the  right way for correction.
>  I fullheartedly appreciate for their honest efforts around this.
>
> Then, what would be done on Stringprep ? Will it follow
> future Unicode 4.0 ? Of course, it will take some time for authors
> to give the answer. So, I won't prompt them today... :-)
>
> Soobok Lee
>
>
> On Sat, Dec 07, 2002 at 04:54:17PM +0800, James Seng wrote:
> > fyi
> >
> > ----- Original Message -----
> > From: "Lisa Moore" <lisam@us.ibm.com>
> > To: "unicore" <unicore@unicode.org>
> > Sent: Saturday, December 07, 2002 6:09 AM
> > Subject: Results of BALLOT on Five Canonical Mapping Errors
> >
> >
> > > Folks,
> > >
> > > We are closing the ballot - 14 out of 18 members have voted, a
majority of
> > > full members voted for Option A:
> > >
> > > A) Fix the canonical mappings and issue another normalization
corrigendum
> > > with corrected mappings in the Unicode 4.0 time frame, as follows:
> > >
> > >    Make the following corrections in UnicodeData.txt for 4.0:
> > >    Correct canonical mapping for 2F868 from 2136A to 36FC.
> > >    Correct canonical mapping for 2F874 from 5F33 to 5F53.
> > >    Correct canonical mapping for 2F91F from 43AB to 243AB.
> > >    Correct canonical mapping for 2F95F from 7AAE to 7AEE.
> > >    Correct canonical mapping for 2F9BF from 4D57 to 45D7.
> > >    Add the following entries to NormalizationCorrections.txt:
> > >    2F868;2136A;36FC;4.0.0 # Corrigendum 4
> > >    2F874;5F33;5F53;4.0.0 # Corrigendum 4
> > >    2F91F;43AB;243AB;4.0.0 # Corrigendum 4
> > >    2F95F;7AAE;7AEE;4.0.0 # Corrigendum 4
> > >    2F9BF;4D57;45D7;4.0.0 # Corrigendum 4
> > >
> > > The vote was:
> > >
> > >       13 for A (Adobe, Apple, Basis, HP, Justsystem, Microsoft,
Oracle,
> > > Peoplesoft, RLG, SAP, Sun, Sybase, Unisys)
> > >       1 for B (IBM)
> > >
> > > Thank you to all for voting so promptly.  The UTC will now support
> > > correcting the five above mappings at next week's WG2 meeting.
> > >
> > > Lisa
> > >
> > >
> > >
> > >
> >
>
>