|
|||||
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.
| 127 | Proposed Update UAX #44: Unicode Character Database | 2008.10.27 |
|
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. |
||
| 126 | Proposed Update UTR #17: Unicode Character Encoding Model | 2008.10.27 |
| This technical report is being updated to correct the titles for various references. The model has been resynched to bring it back up to date for Unicode 5.0. The text has also been edited fairly extensively for readability and consistency. | ||
| 125 | Proposed Update UTR #33: Unicode Conformance Model | 2008.10.27 |
| This technical report is being updated to correct the titles for various references. The text has also been lightly edited. | ||
| 124 | Proposed Update UTR #23: The Unicode Character Property Model | 2008.10.27 |
| This proposed update has a new note about constraints on new property additions. Titles of some references have been updated, along with other minor editing. Draft updated 2008-08-27. | ||
| 123 | Bengali Currency Numerator Values | 2008.10.27 |
| The UTC has recently decided to encode some new fraction characters. For the new sets of fraction characters, the UTC has approved fractional numeric values consistent with the usage of the characters to represent fractions. However, the current numeric values associated with historically related Bengali characters U+09F4..U+09F8 are inconsistent with those numeric value assignments. UTC proposes to update the numeric values. Details are in the background document. | ||
For closed issues, see the Resolved Issues pages (1-99,
100-199).