The sections below contain links to permanent feedback documents for the open Public Review Issues as well as other public feedback as of July 2, 2024, since the previous cumulative document was issued prior to UTC #179 (April 3, 2024).
The links below go directly to open PRIs and to feedback documents for them, as of July 2, 2024.
The links below go to locations in this document for feedback.
Feedback routed to CJK & Unihan Working Group for evaluation [CJK]
Feedback routed to Script Encoding Working Group for evaluation [SAH]
Feedback routed to Properties & Algorithms Working Group for evaluation [PAG]
Feedback routed to Emoji Standard & Research Working Group for evaluation [ESC]
Feedback routed to Editorial Working Group for evaluation [EDC]
Other Reports
Date/Time: Tue Apr 16 18:21:27 CDT 2024
ReportID: ID20240416182127
Name: Paul Masson
Report Type: Error Report
Opt Subject: kMandarin for U+941F 鐟
This character appears to have an alternate pronunciation tì which is not reflected in the database.
(None at this time.)
(None at this time.)
(None at this time.)
Date/Time: Mon Apr 29 08:45:22 CDT 2024
ReportID: ID20240429084522
Name: Wuzzy Wuzzard
Report Type: Error Report
Opt Subject: Core Specification 15.0
I think I found an error in the Core Specification 15.0.
Link: https://www.unicode.org/versions/Unicode15.0.0/UnicodeStandard-15.0.pdf
On page 51 (real page number, not PDF page), it says:
Plane 15 and Plane 16 are allocated, in their entirety, for private use. Those two planes con-
tain a total of 131,068 characters, to supplement the 6,400 private-use characters located in
the BMP.
All other planes are reserved; there are no characters assigned in them. The last two code
positions of all planes are permanently set aside as noncharacters. (See Section 2.13, Special
Characters).
This seems to be a contradiction. If Planes 15 and 16 are *entirely* for private use, then the
last two code positions cannot be noncharacters. If the last two code positions are
noncharacters, then Planes 15 and 16 cannot be *entirely* for private use.
The reason why I think this is a contradiction because of another section. Here is an explanation
of "noncharacter" on page 938:
In effect, noncharacters can be thought of as application-internal private-use code points.
Unlike the private-use characters discussed in Section 23.5, Private-Use Characters, which
are assigned characters and which are intended for use in open interchange, subject to
interpretation by private agreement, noncharacters are permanently reserved (unassigned)
and have no interpretation whatsoever outside of their possible application-internal pri-
vate uses.
If this definition is what was actually intended by the spec, I conclude that all
codepoints it defines as "noncharacters" can never be considered "for private use"
at the same time because "for private use" implies interchangability, while "noncharacter"
means "not for interchange"/"internal-only".
Therefore, the statement "Plane 15 and Plane 16 are allocated, in their
entirety, for private use." must be false. The word "entirety" is the problem here.
(None at this time.)