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.
|53||Proposed Draft UTR #33 Unicode Conformance Model||2005.05.03|
|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.|
|59||Disunification of Dandas||2005.05.03|
|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.)|
|63||POSIX Data for CLDR||2005.03.31|
|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/.|
|64||Draft UTR #36: Security Considerations for the Implementation of Unicode and Related Technology||2005.05.03|
|This draft Unicode Technical Report describes security considerations that are important to be aware of when working with Unicode, and provides specific recommendations for dealing with the issues that arise.|
|65||Encoding of Devanagari Eyelash Ra||2005.05.03|
|The UTC is considering the question of encoding a separate character for the Devanagari eyelash RA, (). Reviewers may refer to discussion in The Unicode Standard, Version 4.0, pages 226 and 230. There is no separate background document. Feedback and detailed information on this issue is being sought. (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.)|
|66||Encoding of Chillu Forms in Malayalam||2005.05.03|
|The UTC is considering the question of encoding 5 "chillu" forms in Malayalam. A brief explanation is in the above-linked background document. Feedback and detailed information on this issue is being sought. (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.)|
|67||CLDR Version 1.3 Beta (Updated 2005.04.22)||2005.05.10|
The 1.3 version of CLDR is now at at beta status, and available via http://unicode.org/cldr/version/1.3.html. The new features include addition of data for timezones, UN M.49 regions, POSIX-format data, LDML meta-data, language/script/territory mappings, new tests, and various other fixes and additions of data, and many extensions to the specification. A new survey tool is being used to vet the additions of data. We encourage people to look at the data and provide feedback, especially on the new POSIX-format data and the changes in the specification. For details on accessing CLDR data, see http://unicode.org/cldr/repository_access.html.
NOTE: Feedback should not be provided via the online Unicode forms; instead, use the CLDR bug reporting method: http://unicode.org/cldr/filing_bug_reports.html.
|68||Proposed Update UTS #10 Unicode Collation Algorithm||2005.04.26|
The Unicode Technical Committee has released a beta version of UTS #10 Unicode Collation Algorithm (UCA) Version 4.1.0. It is available for public review until April 26. This is a running beta; the data files may be updated during the course of the beta. This beta provides a data table that is synchronized with the repertoire of Unicode 4.1.0. In addition, it includes:
See: ftp://www.unicode.org/Public/UCA/4.1.0/ for the data files.
Note: for constraints on proposed changes, see the Unicode