This page is a compilation of formal public feedback received so far. See Feedback for further information on this issue, how to discuss it, and how to provide feedback.
Date/Time: Thu May 26 07:46:08 CDT 2016
Name: Mathias Bynens
Report Type: Error Report
Opt Subject: Incorrect example in TR18: \p{General_Category = Not_Assigned}
Both http://www.unicode.org/reports/tr18/#Categories as the latest draft of
this document i.e. http://www.unicode.org/reports/tr18/proposed.html#Categories
list the following example:
\p{General_Category = Not_Assigned}
However, `Not_Assigned` is not a valid `General_Category` name as per the table
here: http://unicode.org/reports/tr44/#GC_Values_Table
Suggested fix: use `Unassigned` instead in the example.
\p{General_Category = Unassigned}
Date/Time: Thu May 26 09:59:53 CDT 2016
Name: Mathias Bynens
Report Type: Error Report
Opt Subject:
http://unicode.org/reports/tr18/#General_Category_Property has the following
paragraph:
Note: Because it is recommended that the property syntax be lenient as to
spaces, casing, hyphens and underbars, any of the following should be equivalent:
\p{Lu}, \p{lu}, \p{uppercase letter}, \p{uppercase letter}, \p{Uppercase_Letter},
and \p{uppercaseletter}
`\p{uppercase letter}` is mentioned twice in a row.
Date/Time: Mon Jun 6 10:29:49 CDT 2016
Name: Mathias Bynens
Report Type: Error Report
Opt Subject: TR18 RL1.2 and the `is` prefix
http://www.unicode.org/reports/tr18/tr18-18.html#RL1.2 says: “The values for these properties must follow the Unicode definitions, and include the property and property value aliases from the UCD. Matching of Binary, Enumerated, Catalog, and Name values, must follow the Matching Rules from [UAX44].” These matching rules, specifically UAX44-LM3, describe the `is` prefix. I’d like to propose changing UAX44-LM3 to make supporting the `is` prefix optional for new implementations for the reasons described here: http://www.unicode.org/mail-arch/unicode-ml/y2016-m06/0003.html This could either be added as an exception to TR18 by changing the above sentence, or by updating UAX44-LM3 itself to make the `is` prefix optional for new implementations. (I’d prefer the latter solution.)
Date/Time: Fri Jun 10 15:12:15 CDT 2016
Name: Mathias Bynens
Report Type: Error Report
Opt Subject: TR18
`Cn` is listed alongside its long form “Not Assigned”. That should be “Unassigned”.