|
|||||
From time to time the Unicode Consortium seeks wide public review and feedback for certain proposed actions. The purpose of the review is to elicit better information on the practical impact of such proposals on users or implementers as well as broaden the review of technical details. Any feedback on Public Review Issues will be used in the deliberations of the relevant Unicode Consortium technical committee. These open issues are listed here. Each issue has a number, title, summary, and deadline for receipt of public review comments. The link on the title points to a background document if any. When issues are closed, they are moved to the Resolved Issues pages (1-99, 100-199).
Public Review Issues are often targeted at the next version of a particular specification, such as the Unicode Standard. Where the specification is issued by the UTC, the closing date is set to one week before the next quarterly UTC meeting so that any feedback can be reviewed in the meeting. When the specification is due for release only after further meetings, the closing date is typically extended to each subsequent meeting to allow for more feedback.
Organizations and interested individuals are invited to submit public review comments on these issues. Feedback may be submitted via the online contact form; be sure to indicate the number and title of the issue you are providing feedback for, and try to be as explicit as possible in your suggestions. You may also wish to join the Unicode discussion list, where open discussion of all issues related to the Unicode Standard is held.
Material intended for consideration at a Unicode Technical Committee meeting must be submitted at least one week before the start of that meeting. Material intended for consideration by the CLDR Technical Committee should not use the reporting form; instead please see Filing CLDR Bug Reports.
Public Review issues are different from public resolutions of the Unicode Consortium on external issues of particular public importance to the computing industry. Such resolutions are documented as Unicode Consortium Public Positions.
Note: for constraints on proposed changes, see the Unicode Stability Policies.
| 132 | Code Point Name/Label Options | 2009.01.26 |
| After considering the feedback on Public Review Issue #129 on Code Point Labels, the UTC discussed several options, which are now being presented for public review and comment. Details are in the background document. | ||
| 131 | Han Exemplar characters | 2009.01.26 |
| The Unicode Locales (CLDR) contains exemplar characters for each locale/language. These are the characters customarily needed for the language in question. For Han characters, the Unicode CLDR has been using a fairly small set, but there is a request to include more of the commonly used characters. There are a number of possible ways to derive this set, and the CLDR technical committee would like feedback on this. Details are in the background document. | ||
| 130 | Word Break Property for ZWSP | 2009.01.26 |
| The Unicode Technical Committee is considering changing the Word_Break property value for ZWSP from the value WB=Format to the value WB=Other (WB=XX). Details are in the background document. | ||
| 128 | Proposed Update UTS #37: Ideographic Variation Database | 2008.10.27 |
| The purpose of this proposed update is to clarify the conditions under which a glyphic subset is appropriate for a given base character. Details are in the background document. | ||
| 127 | Proposed Update UAX #44: Unicode Character Database | 2009.01.26 |
|
This update is an extensive rewrite of UAX #44 in order to incorporate all of the former content of UCD.html into the annex and consolidate all of the documentation in one place. The material from UCD.html has been reorganized, so that the documentation is clearer and flows better. Substantial new content documenting various aspects of character properties and the UCD has been added as well. Please review the text carefully for correctness. The draft was updated on November 12, 2008. |
||
For closed issues, see the Resolved Issues pages (1-99,
100-199).