One specific question below...
On 12/7/14, 8:49 PM, Peter Saint-Andre - &yet wrote:
On 11/23/14, 7:58 AM, Patrik Fältström wrote:
4.2.1. Valid
o Code points traditionally used as letters and numbers in
writing systems, i.e., the LetterDigits ("A") category first
defined in [ RFC5892] and listed here under Section 8.1 .
o Code points in the range U+0021 through U+007E, i.e., the
(printable) ASCII7 ("K") rule defined under Section 8.11 . These
code points are "grandfathered" into PRECIS and thus are valid even
if they would otherwise be disallowed according to the
property-based rules specified in the next section.
Note: Although the PRECIS IdentifierClass re-uses the LetterDigits
category from IDNA2008, the range of characters allowed in the
IdentifierClass is wider than the range of characters allowed in
IDNA2008. The main reason is that IDNA2008 applies the Unstable
category before the LetterDigits category, thus disallowing
uppercase characters, whereas the IdentifierClass does not apply
the Unstable category.
You must remove the code points of class ("C") in RFC5892.
The only difference between class "C" (IDNA2008) and class "M" (PRECIS)
is that in PRECIS we allow white space code points in the FreeformClass.
Thus we use "C", not "M".
Or to state things differently. If one look at the Unicode tables,
the following combination of matches exists for code points that
matches category "A" and at least one more category, for Unicode
7.0.0:
AB ABC ABF AC ACI AD AE AF AI
There are several of these combinations that is given this definition
is valid which I would not say is recommended for use for
identifiers.
OK, I will look at this more closely.
I don't quite understand your concern here.
Are you saying that there are code points that match, say, the
LetterDigits category ("A") and the IgnorableProperties category ("C")
and the OldHangulJamo category ("I")?
Peter
_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis
