On 7/30/14, 12:48 PM, Joe Hildebrand (jhildebr) wrote:
Draft-17 of the precis-framework doc says:
"The PRECIS framework, which is defined in terms of the latest version
of Unicode as of the time of this writing (6.3), treats the character
U+19DA NEW TAI LUE THAM as DISALLOWED. Implementers need to be aware
that this treatment is different from IDNA2008 (originally defined in
terms of Unicode 5.2), which treats U+19DA as PVALID."
RFC 6452 amends IDNA to say:
Actually, RFC 6452 does not update any of the IDNA2008 specification. It
does make note of changes to several Unicode code points, though.
"1.3. U+19DA NEW TAI LUE THAM DIGIT ONE
The GeneralCategory for this character changes from Nd to No. This
implies that the derived property value changes from PVALID to
DISALLOWED."
So the "PVALID" part of the precis draft likely needs to change.
Yes, that paragraph is poorly worded. I suggest the following substitution:
Three Unicode code points underwent changes in their GeneralCategory
between Unicode 5.2 (current at the time IDNA2008 was originally
published) and Unicode 6.0, as described in [RFC6452]. Implementers
might need to be aware that the treatment of these characters differs
depending on which version of Unicode is available on the system that
is using IDNA2008 or PRECIS, and that other such differences are
possible between the version of Unicode current at the time of this
writing (7.0) and future versions.
Further, I get FREE_PVAL for U+19DA, because it now hits the
OtherLetterDigits rule (R), since its general category is No.
Correct.
Peter
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
