PRI #184: Proposed Update UTS #37, Unicode Ideographic Variation Database

The Unicode Technical Committee has posted a new issue for public review and comment. Details are on the following web page:

http://www.unicode.org/review/

Review periods for the new items close on July 25, 2011.

Please see the page for links to discussion and relevant documents. Briefly, the new issue is:

184 Proposed Update UTS #37, Unicode Ideographic Variation Database (IVD)

This update to UTS #37 will clarify how Ideographic Variation Sequences (IVSes) can be shared across IVD collections, that no IVD collection has special status, and that implementers can support any subset of the registered IVSes.

It will further amend the specification to allow duplicate sequence identifiers within an IVD collection under particular circumstances, and to allow registrants to supply multiple representative glyphs for IVSes in their IVD collections. Finally, the registration procedures will be strengthened to require registrants to supply representative glyphs for registered IVSes and to supply a data file as part of a submission.

If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page:

http://www.unicode.org/reporting.html

If you wish to discuss issues on the Unicode forum or the Unicode mail list, then please use the following links to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration.

http://www.unicode.org/forum/
http://www.unicode.org/consortium/distlist.html

Unicode Releases Common Locale Data Repository, Version 2.0

Mountain View, CA, May 25, 2011 - The Unicode® Consortium announced today the release of a new version of the Unicode Common Locale Data Repository (Unicode CLDR 2.0), providing key building blocks for software to support the world's languages. The main features of CLDR 2.0 are improved data for top 55 languages, with an increase of over 45% in data fields. The details are found in the CLDR 2.0 Release Note (http://cldr.unicode.org/index/downloads/cldr-2-0).

Unicode CLDR is by far the largest and most extensive standard repository of locale data. This data is used by a wide spectrum of companies for their software internationalization and localization: adapting software to the conventions of different languages for such common software tasks as formatting of dates, times, time zones, numbers, and currency values; sorting text; choosing languages or countries by name; transliterating different alphabets; and many others. Unicode CLDR 2.0 is part of the Unicode locale data project, together with the Unicode Locale Data Markup Language (LDML: http://unicode.org/reports/tr35/). LDML is an XML format used for general interchange of locale data, such as in Microsoft's .NET.

For web pages with different views of CLDR data, see http://cldr.unicode.org/index/charts. For more information about the Unicode CLDR project (including charts) see http://cldr.unicode.org/.

Extended Public Review Issues, 177, 179, 182

The review periods for three public review issues have been extended to July 25, 2011, for review at the August UTC meeting.

The affected PRIs are:

177 Proposed Update UTS #46: Unicode IDNA Compatibility Processing

179 Changes to Unicode Regular Expression Guidelines

182 Proposed Update UTS #18: Unicode Regular Expressions

There is an updated version of the proposed update for UTS #18, Unicode Regular Expressions available at http://unicode.org/reports/tr18/proposed.html . The update only has editorial changes; the UTC did not have enough time to review all of the feedback on this document at its last meeting, and will be reviewing it at the August meeting.

If you have comments for official UTC consideration, please post them by submitting your comments through our feedback & reporting page:

http://www.unicode.org/reporting.html

If you wish to discuss issues on the Unicode forum or the Unicode mail list, then please use the following links to subscribe (if necessary). Please be aware that discussion comments on the Unicode mail list are not automatically recorded as input to the UTC. You must use the reporting link above to generate comments for UTC consideration.

http://www.unicode.org/forum/
http://www.unicode.org/consortium/distlist.html