L2/25-088
Source: Editorial Working Group
Date: March 27, 2025
The Editorial Committee continues its review of new content planned for the eventual 17.0 publication of the core specification. In particular, our contributing editors are continuing their review and editing of the following sections, numbered as they will appear in the revised new 17.0 text:
Section 6.2.9 (Other Punctuation), Section 7.1 (Latin), Section 7.9.2 (Combining Diacritical Marks Extended), Section 8.17 (Sidetic), Section 9.2 (Arabic)
Section 12.2 (Bengali), Section 12.7 (Telugu), Section 12.8.2 (Principles of the Kannada Script), Section 12.8.3 (Rendering Kannada), Section 12.9.3 (Rendering Malayalam), Section 13.24 (Tolong Siki), Section 13.25 (Chisoi), Section 15.3 (Sharada), Section 16.15 (Tai Yo), Section 18.1 (Han), Section 18.11.2 (Tangut Components), Section 19.9 (Adlam)
Section 21.2.1 (Musical Symbols), Section 22.5 (Mathematical Symbols), 22.7.4 (Symbols for Legacy Computing), Section 22.9.10 (Chess Symbols)
Certain scripts and their sections received links to UTRs and UTNs that reference them:
9.3 Syriac (under "Languages Using the Syriac Script", fourth bullet)
16.4 Khmer (under "Implementation Guidelines")
17.4 Javanese (under "Implementation Guidelines")
17.9 Kawi (under "Implementation Guidelines")
19.1 Ethiopic (under "19.1.2 Ethiopic Extensions")
19.3 Tifinagh (under "Implementation Guidelines")
19.9 Adlam (under "Evolution of Letterforms")
There is also ongoing work to do routine upkeep of the core specification and to stay current with bug reports and other small tweaks to core specification content mandated by the UTC.
Our release schedule can be consulted in this earlier report.
Chisoi is in progress, and every other script/block is ready for publication.
Based on our current progress and working group reviews, we are confident that we will meet the release schedule. Most items are either complete or have drafts available for review. In the unlikely event that any text misses the final release deadline, we will insert placeholders in the core specification as a fallback measure.
The Editorial Working Group continues its periodical review and general maintenance of Unicode web pages, both out of its own initiative and public feedback.
FYI: The Editorial Working Group continues to meet regularly. Our meetings are generally held on a biweekly schedule, except when holidays or other events coincidence, such as UTC meetings. This report to the UTC includes feedback from the Editorial Working Group meetings held on February 6, 2025, February 13, 2025, February 20, 2025, February 27, 2025, March 6, 2025, March 13, 2025, March 20, 2025, and March 27, 2025.
FYI: Public-facing information about the Editorial Working Group and its work is maintained on the Unicode Editorial Working Group Page on the website. The Editorial Working Group also maintains an internal subsite for use by the committee. People who would like to find out more about the work of the Editorial Working Group or contribute to that work should contact the Chair, Louka Ménard Blondin (louka@unicode.org).
In February and March, additional extraordinary meetings were allocated in between our existing biweekly meetings to tackle our accumulating backlog. This was a successful effort, and the Editorial Working Group is now back on track.
The Editorial Working Group is in ongoing need of volunteer editors with copyediting experience. People who are interested in learning more about this work and potentially take it up should contact the Chair for more information.
Work is ongoing on improving the public documentation about the Editorial Working Group for potentially interested contributors both inside and outside of Unicode. We eventually plan to document and chart the internal processes of the committee to help newcomers better understand our work.
FYI: During this cycle, the Editorial Working Group has been lightly reviewing UAXes and UTSes.
Date/Time: Wed Feb 05 22:51:46 CST 2025 ReportID: ID20250205225146 Name: kirk miller Report Type: Public Review Issue Opt Subject: 514
x1ACF is listed under the header 'Tone mark used in IPA'. It could just as easily be merged under the following header, 'Compound tone diacritics',because like those it is a compound tone diacritic. No need IMO for two headers; the 2nd works for both.1AD0..1AD0 - the hyphenation is odd in the names. E.g. COMBINING VERTICAL-LINE-ACUTE looks like a combination of three elements [vertical +line + acute] when it's a combination of two [vertical line + acute]. But probably not bothering with at this point.1AE2 COMBINING MINUS SIGN ABOVE - might want to add a disambiguating annotation,→ 0304 combining macron.1AE5 COMBINING SEAGULL ABOVE - might want to add a disambiguating annotation,→ 1AE7 combining double arch above.1AE7 COMBINING DOUBLE ARCH ABOVE - might want to add a disambiguating annotation,→ 1AE5 combining seagull above.A7F1 has the note 'also used as a phonetic and phonemic wildcardcharacter'. That note applies equally to all characters under the heading 'Modifier letters for Chatino (México)', and so would be betterplaced under the header.
We do not think it is a good idea to be changing draft names for new characters after the alpha review has begun unless there has been an obvious mistake. The names as they are are reasonably descriptive and unique.
Action item for Ken Whistler, EDC: Take the annotation suggestions under consideration for updates to NamesList.txt. [Reference: Section E1 of L2/25-088]
Date/Time: Thu Feb 06 12:35:37 CST 2025 ReportID: ID20250206123537 Name: Bryndan Meyerholt Report Type: Public Review Issue Opt Subject: 514
xxxxxxxxxxThe third Honorific word ligatures should go above U+FD90 instead of U+FD50
Action item for Ken Whistler, EDC: Correct the location of the subheader along with the notice line. [Reference: Section E1 of L2/25-088]
Date/Time: Wed Jan 29 08:21:45 CST 2025 ReportID: ID20250129082145 Name: Hu Xiangyou Report Type: Error Report Opt Subject: Core Spec
xxxxxxxxxxIn Chapter 2 General Structure, in the Core Spec, Unicode Version 16.0, the "Figure 2-5. Writing Direction and Numbers"is missing Example ⑤, which should be "1123ページをみてください。" in horizontal Japanese.
This has already been fixed.
Date/Time: Mon Mar 17 18:00:23 CDT 2025 ReportID: ID20250317180023 Name: Tatsunori Uchino Report Type: Website Problem Opt Subject: Glossary lacks the entry of "surrogate code unit"
xxxxxxxxxxhttps://www.unicode.org/glossary/The Glossary has the entries of "high-surrogate code unit" and "low-surrogate code unit", but lacks the entry of "surrogate code unit".I want to make links to the description on "surrogate code unit" in my specifications website, but I cannot. I mention "isolatedsurrogate code units" there. It would be appreciated if you would add the term "isolated surrogate code unit" to Glossary becauseveteran major languages (C/C++ wchar_t in Windows & Java and other JVM-based languages & C# and other .NET-based languages& JavaScript/TypeScript) have adopted UTF-16 as their character expression.
Action item for Ken Whistler, EDC: Update the glossary as suggested. [Reference: Section E1 of L2/25-088]
N/A