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: Tue May 28 13:45:01 CDT 2024
ReportID: ID20240528134501
Name: Alexei Chimendez
Report Type: Public Review Issue
Opt Subject: 506
The derived property NFC_Quick_Check=N is defined as characters that "cannot (ever) occur in [Normalization Form C]" (UAX15 §9, UAX44 §5.7.5). The definition of NFC (full decomposition followed by full recomposition) guarantees that the only characters that cannot occur in NFC are those with the property Full_Composition_Exclusion=Y, which will only appear in their decomposed form. These two sets are, by definition, always equal. Because this is not immediately obvious, I think it would be of help to implementers to add this fact as a note in UAX15; or alternatively in some other relevant place, such as UAX44, Table 9. Such an annotation can be useful, for example, to people implementing normalization in environments where memory usage is a concern, since they can choose to implement a check for the property Comp_Ex=Y as a lookup in the same table used for NFC_QC=N, or vice versa.
Date/Time: Tue May 28 13:40:01 CDT 2024
ReportID: ID20240528134001
Name: Alexei Chimendez
Report Type: Public Review Issue
Opt Subject: 506
The conformance clause UAX15-C4 states: > A process that purports to transform text according to the Stream-Safe > Text Format must do so in accordance with the specifications in this annex. This should be: > [...] transform text *into* the Stream-Safe Text Format [...] (which is done "according to" a process.)