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 page.
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.
|51||Proposed Update UAX #29 Text Boundaries||2005.01.31|
|This is a proposed update to a previously approved Unicode Standard Annex. It contains some important changes in categories for some characters and changes in linebreaking rules. The UTC is seeking public feedback on these changes. Note: The text of UAX #29 has been modified slightly to make it clear that level run and directional run refer to the same thing. Re-posted on 2005-01-17.|
|53||Proposed Draft UTR #33 Unicode Conformance Model||2005.01.31|
|This proposed draft Unicode Technical Report explains the issue of conformance relating to the Unicode Standard so that users better understand the contexts in which products are making claims for support of the standard, and implementers better understand how to meet the formal conformance requirements while satisfying the expectations of their users. It does not alter, augment or override the actual Unicode conformance requirements. Rather it attempts to provide a conceptual framework to make it easier for users and implementers to identify and understand the specific conformance requirements.|
|54||Proposed Update UTS #22 Character Mapping Markup Language||2005.01.31|
|This is a proposed update to a previously approved Unicode Technical Report. It will change to a Unicode Technical Standard, so the update includes a new conformance section. Included in the update are many editorial changes and explicit text about multiple-character mappings.|
|56||Proposed Update UAX #14 Line Breaking Properties||2005.01.31|
|This is a proposed update to a previously approved Unicode Standard Annex. It incorporates some changes in Hangul syllable rules, word separators, U+00A0 as a base for combining marks, and other updates. The UTC is seeking public feedback on these changes.|
|57||Changes to Bidi categories of some characters used with Mathematics||2005.01.31|
|The UTC is considering changing the bidi category of seven
compatibility characters from "ET" to "ES":
The UTC is also seeking feedback on the bidi categories of the following characters, and whether to also change these from "ET" to "ES":
All of these characters may be used in connection with mathematical applications. Note: There is no other background document for these proposed changes.
|58||Characters with cedilla and comma below in Romanian language data||2005.01.31|
The CLDR Technical Committee is seeking feedback regarding the relative frequency of use of the characters with comma below and of the characters with cedilla in Romanian language textual material in widespread implementations, such as databases and operating systems, and in published documents and Romanian websites. The purpose for this feedback is to determine which to use in a default set of locale data for Romanian to be specified for CLDR.
The characters in question are:
Please accompany your feedback with information on the source of your data and indicate the extent and nature of your experience with Romanian data processing. Note: There is no other background document for this item.
|59||Disunification of Dandas||2005.01.31|
|The UTC is considering the question of disunifying the characters U+0964 DEVANAGARI DANDA and U+0965 DEVANAGARI DOUBLE DANDA from their counterparts in several other Indic scripts. Feedback on this issue, including evidence, for or against the disunification, is being sought. Details are in the background document linked above. (Note: as with other Public Review Issues, this is not a "vote". Submissions that simply favor one approach or another without giving any evidence either way will not be considered by the committee.)|
|60||Proposed Update UAX #9 Bidirectional Algorithm||2005.01.31|
|A proposed update to UAX #9 for Unicode 4.1.0 is available at the link above. The proposed changes are listed in the Modifications section of the document.|
|61||Proposed Update UAX #15 Unicode Normalization Forms||2005.01.31|
|A proposed update to UAX #15 for Unicode 4.1.0 is available at the link above. The proposed changes are listed in the Modifications section of the document.|
|62||Proposed Update UTS #10 Unicode Collation Algorithm||2005.01.31|
A proposed update for UTS #10: Unicode Collation Algorithm (UCA) for Unicode 4.1.0 is available for public review. The main feature is the update of the repertoire to Unicode 4.1.0 (for synchronization, UCA 4.1.0 will be available within the month after Unicode 4.1.0). Other changes include:
|63||POSIX Data for CLDR||2005.02.07|
|There is a new tool that creates POSIX locale data files from CLDR. It has been used to generate draft POSIX locale data files for public review. The CLDR Technical Committee is seeking review of this data. Details and relevant URLs are in the above-linked background document. Note that the CLDR 1.3 freeze date has also been extended. Please see http://www.unicode.org/cldr/.|
Note: for constraints on proposed changes, see the Unicode