W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2006

Re: FW: New Public Review Issue: UAX #15

From: Felix Sasaki <fsasaki@w3.org>
Date: Mon, 16 Jan 2006 22:06:09 +0900
To: "Richard Ishida" <ishida@w3.org>, public-i18n-core@w3.org
Message-ID: <op.s3g2oji9x1753t@ibm-60d333fc0ec.mag.keio.ac.jp>

On Mon, 16 Jan 2006 19:07:32 +0900, Richard Ishida <ishida@w3.org> wrote:

>
> FYI

I'm currently having a look at this. The main changes concern versioning,  
see section 3  
( http://www.unicode.org/reports/tr15/tr15-26.html#Versioning ).

I don't see an issue in section 3.1 "Stability of Normalized Forms" which  
says "A normalized string is guaranteed to be stable: that is, once  
normalized, a string is normalized according to all future versions of  
Unicode.".

I don't see an issue in section 3.3 "Guaranteeing Process Stability",  
which describes how corrigenda between versions of Unicode should be  
handled.

Corrigenda 2 and 3 (changes in normalization behavior of the character  
U+FB1D HEBREW LETTER YOD WITH HIRIQ, and U+F951 Normalization) are two  
example corrigenda which fall under section 3.3.

" Corrigendum #5: Normalization Idempotency fixed a problem in the  
description of the normalization process for some instances of particular  
sequences. Such instances never occur in meaningful text.". As a  
background to this corrigendum, there is a public review issue  
http://www.unicode.org/review/pr-29.html . It proposes the following  
change to definition D2:

"D2. In any character sequence beginning with a starter S, a character C  
is blocked from S if and only if there is some character B between S and  
C, and either B is a starter or it has the same or higher combining class  
as C."
The change is the insertion of "or higher".

The description of this corrigendum  
(http://www.unicode.org/versions/corrigendum5.html) mentions that problems  
arising from the old definition D2 have no "realistic scenarios [...] that  
would present such problems.".

I'm not sure about this corrigendum. I will take a closer look. Let's talk  
about it on a call.

Regards, Felix.

>
> -----Original Message-----
> From: unicore-bounce@unicode.org [mailto:unicore-bounce@unicode.org] On
> Behalf Of Rick McGowan
> Sent: 14 January 2006 01:03
> To: unicode@unicode.org
> Subject: New Public Review Issue: UAX #15
>
> The Unicode Technical Committee has posted a new issue for public review  
> and
> comment. Details are on the following web page:
>
> 	http://www.unicode.org/review/
>
> Review period for the new item closes on January 31, 2005
>
> Please see the page for links to discussion and relevant documents.
> Briefly, the new issue is:
>
>
> Issue #86: UAX #15: Unicode Normalization Forms
>
> There are no substantive changes in this version of UAX #15. Sections  
> were
> added to clarify stability and versioning issues, and to make some
> formatting changes for Unicode 5.0.
>
> 	http://www.unicode.org/reports/tr15/tr15-26.html
>
>
> If you have comments for official UTC consideration, please post them by
> submitting your comments through our feedback & reporting page:
>
>     http://www.unicode.org/reporting.html
>
> If you wish to discuss issues on the Unicode mail list, then please use  
> the
> following link to subscribe (if necessary). Please be aware that  
> discussion
> comments on the Unicode mail list are not automatically recorded as  
> input to
> the UTC. You must use the reporting link above to generate comments for  
> UTC
> consideration.
>
>     http://www.unicode.org/consortium/distlist.html
>
> Regards,
> 	Rick McGowan
> 	Unicode, Inc.
>
>
>
Received on Monday, 16 January 2006 13:06:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:50 GMT