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.
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 [SEW]
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]
Feedback routed to Charts Working Group for evaluation [CHARTS]
Other Reports
(None at this time.)
Date/Time: Sun Jan 04 11:57:58 PT 2026
ReportID: ID20260104115758
Name: Michel Mariani
Report Type: Report Error in Publication/Data
Opt Subject: Error in Core Spec - Tangut Components
• In: "Chapter 18" of the "Unicode Core Spec", in: "18.11.2 Tangut Components: U+18800–U+18AFF", under: "Repertoire", it is written: "In some cases, these single strokes are encoded as components (U+18900..U+18909, U+18D82..U+18D83)", but the first code point range is incorrect, "U+18900..U+18909" should be "U+18800..U+18809" https://www.unicode.org/versions/Unicode17.0.0/core-spec/chapter-18/#G43765 • See: "The Unicode Standard, Version 17.0 - CodeCharts.pdf" Tangut Components One-stroke components 18800 TANGUT COMPONENT-001 18801 TANGUT COMPONENT-002 18802 TANGUT COMPONENT-003 18803 TANGUT COMPONENT-004 18804 TANGUT COMPONENT-005 18805 TANGUT COMPONENT-006 18806 TANGUT COMPONENT-007 18807 TANGUT COMPONENT-008 18808 TANGUT COMPONENT-009 18809 TANGUT COMPONENT-010 Tangut Components Supplement One-stroke components 18D82 TANGUT COMPONENT-771 18D83 TANGUT COMPONENT-772
Date/Time: Sun Jan 08 23:01:12 PT 2026
ReportID: ID20260108230112
Name: Mikhail Merkuryev
Report Type: Report Error in Publication/Data
Opt Subject: Again breaking by hyphen
I’m pleased that you’ve taken my issue to discussion. I suggest writing these things to TR14 section 5.3 Use of Hyphen. Brush up as you wish. Unless you’ve done morphological analysis, we strongly discourage you from: Breaking out one character: 7- / bit, да- / с (Russian: yes milord) And discourage you from: Breaking out two characters: кто- / то (Russian: someone) Breaking out short numbers: 128- / bit No change in formal algorithms.
Date/Time: Thu Jan 12 16:07:38 PT 2026
ReportID: ID20260112160738
Name: Meghan Denny
Report Type: Report Error in Publication/Data
Opt Subject: typo in idna/Idna2008.txt comment
https://www.unicode.org/Public/17.0.0/idna/Idna2008.txt contains the following comment: # Field 1: IDNA2008_Category, consisting of one of these values # "PVALID" - Protocol valid (generally Letters, Digits and Hyphen) # "CONTEXTJ" - Join control # "CONTEXT0" - Other code points requiring context # "DISALLOWED" - The code point is not allowed in IDNA2008 # "UNASSIGNED" - The code point is not assigned in this version "CONTEXT0" should be "CONTEXTO" in the next release as that would reflect the data accurately.
Date/Time: Thu Feb 5 15:56:17 PT 2026
ReportID: ID20260205155617
Name: Sergiusz Wolicki
Report Type: Report Error in Publication/Data
Opt Subject: No HH in field 1 description in LineBreak.txt
https://www.unicode.org/Public/UCD/latest/ucd/LineBreak.txt: # Field 1: Line_Break property, consisting of one of the following values: # Non-tailorable: # "BK", "CM", "CR", "GL", "LF", "NL", "SP", "WJ", "ZW", "ZWJ" # Tailorable: # "AI", "AK", "AL", "AP", "AS", "B2", "BA", "BB", "CB", "CJ", # "CL", "CP", "EB", "EM", "EX", "H2", "H3", "HL", "HY", "ID", # "IN", "IS", "JL", "JT", "JV", "NS", "NU", "OP", "PO", "PR", # "QU", "RI", "SA", "SG", "SY", "VF", "VI", "XX" The new HH property values is missing from the list.
Date/Time: Tue Feb 10 05:15:43 PT 2026
ReportID: ID20260210051543
Name: Ismael RH
Report Type: Report Error in Publication/Data
Opt Subject: Collation of "barred closed omega"
Dear staff, The character "closed omega" is collated as a variant of "o" in IPA Extensions (lowercase) as well as in Latin Extended-F (modifier lowercase). Additional EPA variants (closed omega with long stem; turned closed omega) are also collated as such in the provisional order for EPA letters in Latin Extended-G. In light of this, I would like to request UTC to place "barred closed omega" after "barred eng" so that it is likewise treated as a variant of "o" rather than of "w", in consistency with the rest of encoded (or futurely encoded) barred omegas. Yours truly, Ismael
Date/Time: Mon Feb 9 06:36:22 PT 2026
ReportID: ID20260209063622
Name: Mikhail Merkuryev
Report Type: Report Error in Publication/Data
Opt Subject: Proto-cuneiform: suspect wrong data
Chars 12550…125A7 are Xsux (cuneiform) 12A58…1264B are Pcun (proto-cuneiform) 1264C…12686 are Xsux again? Are you sure what you are doing? Shouldn’t they be all Pcun?
(None at this time.)
(None at this time.)
(None at this time.)
(None at this time.)