After the last Unicode Technical Committee meeting, there were some public 
review issues <https://www.unicode.org/review/> posted. PRIs are a way that UTC 
uses to solicit input and feedback on specific proposals or work in progress. 
The input period for these PRIs ends January 2, 2024. (Time is needed before 
the next UTC meeting to process the feedback.) That means we're almost halfway 
through the public review period.

Here's a summary of the five open PRIs:

PRI #483: <https://www.unicode.org/review/pri483/> Proposed Update UAX #38, 
Unicode Han Database (Unihan)<https://www.unicode.org/review/pri483/> — UAX #38 
describes the many properties Unicode provides for CJK ideographs. This is a 
draft update of this spec for Unicode 16.0.

PRI #484: <https://www.unicode.org/review/pri484/> Proposed Update UAX #50, 
Unicode Vertical Text Layout <https://www.unicode.org/review/pri484/> — UAX #50 
describes how characters should be adjusted between horizontal and vertical 
layout. This is a draft update of this spec for Unicode 16.0.

PRI #485: <https://www.unicode.org/review/pri485/> Draft UTR #56, Unicode 
Cuneiform Sign Lists<https://www.unicode.org/review/pri485/> — This is a draft 
for a new technical report that will provide additional data that will aid in 
the use of the Unicode encoding for Sumero-Akkadian Cuneiform 
script<https://www.unicode.org/charts/PDF/U12000.pdf>.

PRI #486: <https://www.unicode.org/review/pri486/> Stabilization of UAX #42, 
Unicode Character Database in XML 
(UCDXML)<https://www.unicode.org/review/pri486/> — UAX #42 provides the data 
for the Unicode Character Database in XML format. (UCD is character property 
data for use in processing algorithms that is provide with each version of 
Unicode. This PRI is for feedback on a planned UTC action to freeze UAX #42 as 
of Unicode 15.1.

PRI #487: Proposed Update UAX #53 Unicode Arabic Mark 
Rendering<https://www.unicode.org/review/pri487/> — This specification was 
previously published as a Unicode Technical Report. This is a draft for 
changing the status of the spec, to make it formally part of The Unicode 
Standard as a Unicode Standard Annex (UAX) starting in Unicode 16.0.


UTC invites you to please take a look and provide feedback on these issues.


Peter Constable
UTC Chair


Reply via email to