L2/22-245
Editorial Committee Report and Recommendations for UTC #173 Meeting
Source: Editorial Committee
Date: October 26, 2022
A. Unicode Release Topics
A1. Unicode 15.0.0 Publication Report
FYI: The Unicode 15.0 core specification was published as scheduled on September 13, 2022, along with the Version 15.0 of the Unicode Standard, including all its associated annexes and correlated Unicode Technical Standards.
Leading up to and during the release of Version 15.0 of the Unicode Standard, the Editorial Committee was heavily involved in the release management process itself, but has now passed off most of that responsibility to UTC's newly formed Release Management Group. For future releases, the Editorial Committee will be focused primarily on delivering updates for the core specification and on editorial quality of the various annexes and other technical reports.
A2. Unicode 15.1.0 Report
FYI: The Editorial Committee is currently proceeding on the assumption that Unicode 15.1 will be released in 2023 without a separate update of the core specification. The focus of the Editorial Committee work for 15.1 will be on editorial review of updates to the text of the various Unicode Technical Reports.
A3. Core Specification Future Development
FYI: The work on transitioning the core specification to a new publication framework has reached a new milestone. The 15.0 (and earlier) editorial work was handled in FrameMaker, with publication based on pdf files generated from FrameMaker and then tweaked further for publication using Acrobat. The 15.0 FrameMaker source has been completely archived, along with all figures and fonts used for the publication. So the Editorial Committee has a reference archive, but that particular production pipeline has now been end-of-lifed.
The TUS Future task group has been holding regular meetings, on a roughly monthly basis now, since mid-spring, 2022, to plan out the many additional enhancements that will be required to get to a complete, quality core specification publication in the 16.0 time frame. This work will be continuing through 2023.
The complete content of the 15.0 core specification has been recovered from FrameMaker mif files and converted to HTML source, which has been accessioned into a new GitHub repository for this work. The Editorial Committee is now working on a dual track process, which will enable us to make routine progress on content correction and updates for the core specification aimed at an eventual 16.0 core specification, while simultaneously working out details of next generation content management, font resource management, structure, and formatting of the text.
As noted below in our responses to various feedback on the core specification, the Editorial Committee can already deal with routine updates to correct typos and other errors reported, as well as other small content updates going forward.
Currently the TUS Future work is proceeding in a private repository, as the Editorial Committee is not yet in a position to open up this work for wide public collaboration. We anticipate, however, that by the time frame for the Unicode 16.0 beta review, it should be possible to make the entire content of the core specification public in a reviewable state, so that it can become part of the beta review process, unlike prior releases, in which there has generally been no chance to review core specification updates outside the Editorial Committee.
We will do a brief show and tell for the UTC about some of the current work underway.
B. Website Topics
B1. Website Status
FYI: The Unicode technical website has remained stable since our last report.
B2. Website Content Maintenance
FYI: The Editorial Committee continues to provide minor maintenance of pages on the Unicode technical website.
B2.1. Technical Website Color Theme Makeover
FYI: Participants in the UTC will undoubtedly have noticed the recent makeover of the colors used on the technical site. This is part of an initiative undertaken by the Communications Group and executive management of the Unicode Consortium to converge the user experience between the home.unicode.org website (currently WordPress based) and the older technical site that most UTC participants are familiar with. Ken Whistler and Rick McGowan participated in the updates of the CSS used on the technical site, to enable the color retheming (to match home.unicode.org), without otherwise impacting the functioning of the technical site.
The Editorial Committee is reporting on this to the UTC in the context of its general responsibility for maintenance of the Unicode technical site.
B3. FAQ Updating
FYI: Since the last UTC meeting the FAQ of the Fortnight project led by Ben Yang and Asmus Freytag has been busy reviewing and updating the Unicode FAQ pages.
This work has resulted in many, many improvements to our existing FAQ pages, along with new content for many pages. The project participants meet regularly and focus on detailed review of particular FAQ pages. The latest enhancement pioneered by Asmus is automated addition of glossary links to significant terms cited in FAQ entries.
C. Editorial Committee Process Issues
FYI: The Editorial Committee continues to meet regularly. Our meetings have recently changed to a biweekly schedule, with shorter meetings than we used to hold.
This report to the UTC includes feedback from the Editorial Committee meetings held on August 11, September 8, September 22, October 6, and October 20, 2022.
Public-facing infomation about the Editorial Committee and its work is maintained on the Unicode Editorial Committee page on the website. The Editorial Committee also maintains an internal subsite for use by the committee. People who would like to find out more about the work of the Editorial Committee or contribute to that work should contact the Chair, Julie Allen.
D. UTR Topics
FYI: The Editorial Committee has nothing to bring up separately about various UTRs at this time.
E. PRI Topics
E1. Public Feedback on PRIs for Unicode Technical Reports
FYI: The Editorial Committee has no new feedback on the only currently open PRIs, for UTR #17 and UTR #23. Given the lack of public feedback on those two PRIs, we recommend that the UTC go ahead and close PRI #458 and PRI #459 and publish the two updated UTRs.
AI Rick McGowan, UTC. Close PRI #458.
AI Ken Whistler, EDC. Prepare Revision 9 of UTR #17 for publication.
AI Rick McGowan, UTC. Publish Revision 9 of UTR #17.
AI Rick McGowan, UTC. Close PRI #459.
AI Ken Whistler, EDC. Prepare Revision 15 of UTR #23 for publication
AI Rick McGowan, UTC. Publish Revision 15 of UTR #23.
E2. Public Feedback [Items noted for Editorial Committee attention]
Date/Time: Tue Jul 19 14:30:32 CDT 2022
Name: Ivan Panchenko
Report Type: Error Report
Opt Subject: UTR #54
UTR #54 contains the mistake “a one of several” (instead of just “one of several”) and a needless comma here: “Separation of the glyph variant information and documentation of all the associated contextual rules and their interaction with the Mongolian text model, from the production of versioned code charts would also make it possible to update this information much more quickly.”Discussion: We agree that these typos should be corrected.
EC-UTC173-R1: The Editorial Committee recommends that:
The UTC authorizes a proposed update of UTR #54, to correct typos and to update the style of the document to reflect current practice for technical reports.AI Ken Whistler, EDC. Correct the typos in UTR #54 as noted in L2/22-245 [Ivan Panchenko Tue Jul 19 14:30:32 CDT 2022] and prepare a proposed update of the document.
AI Rick McGowan, UTC. Post a proposed update for UTR #54, to close January 16, 2023.
Date/Time: Sun Aug 7 06:29:40 CDT 2022
Name: Yasuhiro Inukai
Report Type: Error Report
Opt Subject: Unicode Standard Version 14.0 Core Specification
There is an error in Figure 13-7 on p.556 of Unicode Standard Version 14.0 Core Specification (https://www.unicode.org/versions/Unicode14.0.0/UnicodeStandard-14.0.pdf). Under “cherig”, the example glyph just to the right of “1821” is not correct. It shows U+1822 (MONGOLIAN LETTER I)-like glyph instead of U+1821 (MONGOLIAN LETTER E). Thanks,Discussion: We agree that this is an issue in the figure. This correction should be undertaken in the context of a general update needed to bring the Mongolian text representation model forward.
AI Liang Hai, EDC. Correct Figure 13-7, Mongolian Gender Forms, as noted in L2/22-245 [Yasuhiro Inukai Sun Aug 7 06:29:40 CDT 2022] in a future revision of the core specification.
Date/Time: Wed Sep 14 09:09:43 CDT 2022
Name: David Corbett
Report Type: Other Document Submission
Opt Subject: Typo in chapter 9
Chapter 9 includes the word “AARABIC” in the “High Hamza” section.Discussion: This typo has been corrected in the current draft. No action needs to be recorded.
Date/Time: Sun Sep 18 12:29:03 CDT 2022
Name: Mark Longley
Report Type: Error Report
Opt Subject: Unicode Standard Version 15.0 Core Specification
In the Unicode Standard - Version 15.0 - Core Specification in section 23.9 Tag Characters on page 945 there is a minuscule error in the second subsection Deprecated Use for Language Tagging. It is stated that "In Version 8.0, all but the language tag identification character were un-deprecated" whereas in fact U+E007F CANCEL TAG was still deprecated in Version 8.0 and was not un-deprecated until Version 9.0.Discussion: We agree that the wording about this is insufficiently precise and should be corrected.
AI Ken Whistler, EDC. Correct the discussion of the deprecation status of U+E007F CANCEL TAG in Section 23.9 of the core specification, in a future revision of the draft. Ref. L2/22-245 [Mark Longley Sun Sep 18 12:29:03 CDT 2022]
Date/Time: Fri Sep 23 22:38:51 CDT 2022
Name: Pablo Sebastián Viola
Report Type: Error Report
Opt Subject: UnicodeStandard-15.0.pdf
I am reading the file stored in https://www.unicode.org/versions/Unicode15.0.0/UnicodeStandard-15.0.pdf. In page xxiii I see that the Unicode version 15.0 is referred, what confirms that I am reading the right file. However, in many places, the document refers to itself as the version 14.0. I found mentions to the version 14.0 that probably are wrong, in pages: 75, 76, 77, 83. In the Index there are entries referred to Version 14.0 that probably should be 15.0: "Characters, .... number encoded in version 14.0.... p.3", "Version 14.0..... p.77". There are other places where the version 14.0 is mentioned, but they are probably right.Discussion: This was a serious oversight in the copyediting of the 15.0 version of the core specification. An erratum notice was posted on 2022-09-28 at: Updates and Errata. The current draft of the core specification has already been corrected, so no action item needs to be recorded.
Date/Time: Tue Oct 11 15:20:10 CDT 2022
Name: Markus Scherer
Report Type: Error Report
Opt Subject: core spec 2.9 Details of Allocation vs. plane 3
Figure 2-13 Unicode Allocation ( https://www.unicode.org/versions/Unicode15.0.0/ch02.pdf#G286741 page 47) still shows the U+3xxxx plane as Reserved. We have had CJK characters there since Unicode 13. This plane should be shaded for Graphic characters. The text on page 51 about "Plane 3 (TIP)" might be fine, but I suspect that its statement that it "is dedicated to encoding additional unified CJK characters" also predates Unicode 13. At a minimum, we should add a comma after the "(TIP)" in the paragraph, but it probably wants to read more like the text for plane 2.Discussion: Note that the allocation figure is intended to already show the impact of the encoding of Extension G on Plane 3, although at the scale used in the figure, the plane boundaries are unclear. The figure could be tweaked a bit to emphasize the plane boundary and show the impact of the encoding of Extension H. The text in the section does need some minor revision to update the facts about allocation on Plane 3. Those textual changes have already been made in the current draft of the core specification, so the remaining fix to be made is simply adjustment of the allocation figure.
AI Rick McGowan, EDC. Adjust the details of Figure 2-13, Unicode Allocation, to better show the impact of the encoding of Extension H, in a future revision of the core specification draft. Ref. L2/22-245 [Markus Scherer Tue Oct 11 15:20:10 CDT 2022]
Date/Time: Thu Oct 13 07:15:03 CDT 2022
Name: Mark Longley
Report Type: Error Report
Opt Subject: The Unicode® Standard Version 15.0 – Core Specification
There is a typographical error in Chapter 22 Symbols in section 22.10 Enclosed and Square in subsection Enclosed Alphanumeric Supplement: U+1F100–U+1F1FF in subsubsection Creative Commons License Symbols on page 910. The first of the two character code ranges is given as “U+1F10D..U+1F10FF” when the end of this range should in fact be “U+1F10F”, i.e. there is a spurious duplicated terminal ‘F’ hexadecimal digit.Discussion: This typo has been corrected in the current draft. No action needs to be recorded.
G. Miscellaneous Topics
G1. (None noted)