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 Mar 3 10:57:55 CST 2022
Name: Andrew West
Report Type: Public Review Issue
Opt Subject: 445
Note: This feedback was resolved during UTC #171.
UTC-00340;V;U+846C;140.9;;⿱艹㘸;kLau 1560a;;; I think it should be U;U+585F
Date/Time: Sun May 15 08:16:57 CDT 2022
Name: Ken Lunde
Report Type: Public Review Issue
Opt Subject: 445
Please consider the following three UAX #45 suggestions: 1) At some point in the future, the single-letter status field identifiers (aka Field 1) for CJK Unified Ideographs extensions will collide with other single-letter status field identifiers, the first being N, which indicates that the ideograph is planned to be submitted for a future extension. I therefore suggest that the following single-letter status field identifiers be changed as follows: A → ExtA B → ExtB C → ExtC D → ExtD E → ExtE F → ExtF G → ExtG H → ExtH U → URO 2) In order to highlight status field identifiers "N" (Earmarked to be included in a proposal from the UTC to the IRG for a future extension), "W" (Not suitable for encoding as a CJK Unified Ideograph), and "X" (Appropriate disposition has not been determined) for easier identification, I suggest that they be changed to characters that display as emoji: N → ✅ (U+2705 WHITE HEAVY CHECK MARK) W → ❌ (U+274C CROSS MARK) X → ❓ (U+2753 BLACK QUESTION MARK ORNAMENT) Of course, the second suggestion makes the purpose of the first suggestion moot. However, there is still a benefit of the first suggestion: the affected status field identifiers are more explicit. 3) I noticed that the description of Field 2 in the header of USourceData.txt doesn't really match the descriptions in the table in Section 2.1 of UAX #45 itself: # If the status is V (Field 1), the code point in Field 2 specifies # the encoded character for which this entry is a variant. Otherwise, the # code point specifies the encoded character for this entry. The table in Section 2.1 of UAX #45 states that the same is true of other status field values, such as N, W, X, and so on. Perhaps the following is a more accurate description: The code point in Field 2 specifies the encoded character for this entry. Otherwise, the code point specifies the encoded character to which this entry is related, generally as a variant. That is all.