Subject: Fwd: Unicode letter ballot

From: Patrik Fältström <[email-masked]>
Date: Sun, 24 Nov 2002 09:38:00 +0100

As liason with the Unicode Consortium, I report the following.

     Regards, Patrik

Begin forwarded message:

> From: Rick McGowan <[email-masked]>
> Date: lör nov 23, 2002  21:12:10 Europe/Stockholm
> To: [email-masked]
> Subject: Unicode letter ballot
>
> To members of liaisons organizations:
>
> Clerical errors were found in canonical mappings for 5 Han
> compatibility chars in plane 2... There is a letter ballot being 
> issued to
> Unicode members, attached below.
>
> For further information on possible actions resulting from this ballot,
> please see the following two pages:
> 	http://www.unicode.org/unicode/uni2errata/UnicodeErrata.html
> 	http://www.unicode.org/Public/UNIDATA/NormalizationCorrections.txt
>
> Regards,
> 	Rick McGowan
> 	Unicode, Inc.
>
> ---------------------------------------
>>
>> BALLOT to decide the correction for five canonical mapping errors in 
>> the
>> Unicode Character Database.
>>
>>  APPROVE Option A: __
>>
>> OR
>>
>>  APPROVE Option B: __
>>
>> ___________________________________________
>>
>> SUMMARY
>>
>> There are five clear errors have been discovered in the canonical 
>> mappings
>> for Plane 2 CJK compatibility characters, verified independently by
>> multiple experts. Those errors are for U+2F868, U+2F874, U+2F91F, 
>> U+2F95F,
>> and U+2F9BF.
>>
>> An additional five characters have been determined to have certain 
>> visual
>> or clerical errors, but these will be handled through annotations to 
>> the
>> names list.
>>
>> At UTC 93, the committee approved that a letter ballot be issued to 
>> choose
>> the appropriate corrective action, either Option A or Option B:
>>
>> 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
>>
>> B) Add five new characters with the correct canonical mappings and
>> deprecate the existing characters with the incorrect mappings, as 
>> follows:
>>
>>    Deprecate 2F868, 2F874, 2F91F, 2F95F, 2F9BF.
>>    Encode 5 new CJK compatibility characters as follows:
>>    2FA1E CJK COMPATIBILITY CHARACTER-2FA1E --> 36FC
>>    2FA1F CJK COMPATIBILITY CHARACTER-2FA1F --> 5F53
>>    2FA20 CJK COMPATIBILITY CHARACTER-2FA20 --> 243AB
>>    2FA21 CJK COMPATIBILITY CHARACTER-2FA21 --> 7AEE
>>    2FA22 CJK COMPATIBILITY CHARACTER-2FA22 --> 45D7
>> ___________________________________________
>>
>> IMPLICATIONS OF THE TWO OPTIONS:
>>
>> Implications of Option A.
>>    a. Can be accomplished in Unicode 4.0 timeframe.
>>    b. Requires issuing technical corrigendum 4 for
>>       Unicode and a technical corrigendum for 10646.
>>    c. Impacts normalization stability.
>>    d. Follows precedent of technical corrigendum 3.
>>
>> Implications of Option B.
>>    a. Deprecates 5 characters and creates 5 duplicates
>>       of them to map correctly.
>>    b. May be problematical to complete in Unicode 4.0
>>       if not levered into current FPDAM for 10646.
>>    c. Preserves normalization stability.
>>    d. Sets new precedent for correction of CJK
>>       compatibility mapping errors.
>> ___________________________________________
>