Wednesday, July 27, 2011

PRI #201 - Proposed Update UTR #45 now available

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/pri201/

A proposed update for UTR #45 has been posted. This update corrects the syntax of U-source identifiers to match ISO/IEC 10646 data files. It also introduces a new syntax with "UCI" labels to identify U-sources for unified ideographs which have been "orphaned" of their original sources.

Note that the review period for the proposed update has been compressed, so that the updated U-source listing and syntax will be available for use in the 10646 3rd Edition. Review feedback should be posted in time for consideration at the UTC meeting scheduled for August 1 - 5, 2011.

To supply feedback on this issue, see http://www.unicode.org/review/#feedback

Monday, July 25, 2011

Proposed Updates to Unicode Standard Annexes for Unicode 6.1

The proposed update documents for some Unicode Standard Annexes have been updated. These updates include:

UAX #15: Added an implementation note about using 255 as an implementation specific value for optimization of tables containing Canonical_Combining_Class values.

UAX #29: Updated the discussion of legacy grapheme clusters for Thai. Moved the section on Hangul syllable boundary determination to a new section in this UAX, from Chapter 3 of the Core Specification. Made other small editorial fixes.

UAX #31: Supplied the recommended usage for identifiers for new scripts encoded in Unicode 6.1. Clarified the status of lists of Other_ID_Start and Other_ID_Continue characters.

Call for Bulldog Award Nominations

Dear Unicode community,

As many of you already know, the Unicode Consortium sponsors an annual award for outstanding personal contributions to the philosophy and dissemination of the Unicode Standard. Known as the "Bulldog Award," it is presented at the Unicode conference to recognize "those tenacious champions of Unicode who have produced solid achievements in promoting its use around the globe".

The Consortium invites the Unicode community to nominate up to two people they believe are most deserving of this award. Nominations should include a brief rationale why the candidate would be a good choice. Please check http://unicode.org/conference/bulldog.html to see a list of past winners and send nominations to magda@unicode.org with "Bulldog Award nomination" in the subject line by August 29, 2011.

Executive officers and staff of the Unicode Consortium are not eligible for the award.

Thank you for your time.

Magda Danish

Senior Administrative Director

The Unicode Consortium

Monday, July 18, 2011

Unicode Releases Common Locale Data Repository, Version 2.0.1

Mountain View, CA, July 18, 2011 - The Unicode® Consortium announced today the release of a new version of the Unicode Common Locale Data Repository (Unicode CLDR 2.0.1), providing key building blocks for software to support the world's languages.

CLDR 2.0.1 is an minor release, with no new translations. It includes about 80 changes that were not ready for CLDR 2.0, including fixes for collation, number spellout, format consistency, and metazone (timezone) data. It also now provides descriptions for all of the bcp47 data items in CLDR. For more information on what else has changed since the 2.0 release, see the CLDR 2.0.1 Release Note.

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.1 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/.

Wednesday, July 13, 2011

PRI #200: Draft UTR #49, Unicode Character Categories

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 period for the new item closes on July 27, 2011.

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


PRI #200 Draft UTR #49: Unicode Character Categories

This document presents an approach to the categorization of Unicode characters, and documents data files that implementers can use for defining and labeling Unicode character categories.


To supply feedback on this issue, please see http://www.unicode.org/review/#feedback

Thursday, July 7, 2011

Proposed Update UAXes for Unicode 6.1

Proposed updates for most Unicode Standard Annexes for Version 6.1 of the Unicode Standard have been posted for public review. See http://www.unicode.org/review/ for details and links to the various documents.

Review periods for provision of feedback on these proposed updates close on July 25, 2011 for the August UTC meeting, but there will be further opportunities for feedback on the annexes after that August meeting.

To supply feedback on these issues, please see http://www.unicode.org/review/#feedback

Tuesday, July 5, 2011

PRI #187: Second registration of sequences for the Hanyo-Denshi collection

The Unicode Consortium has posted a new issue for public review and comment.

Public Review Issue #187: A submission for the "Second registration of sequences for the Hanyo-Denshi collection" has been received by the IVD registrar. This submission is currently under review according to the procedures of UTS#37, Ideographic Variation Database, with an expected close date of 2011-10-05.

Please see the submission page for details and instructions on how to review this issue and provide comments: http://www.unicode.org/ivd/pri/pri187/

For further information on Public Review Issues, please see: http://www.unicode.org/review/

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. You must use the reporting link above to generate comments for consideration.

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

Friday, July 1, 2011

PRI #186: Word-Joining Hyphen

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 period for the new item closes on July 27, 2011.

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

PRI #186 Word-Joining Hyphen

The Unicode Standard has different character properties for line-break and word-break behavior that reflect differences in behavior. The standard specifies that U+2011 NON-BREAKING HYPHEN disallows line breaks. The Unicode Technical Committee is currently considering whether this non-breaking behavior should be broadened to also affect word breaking behavior.

Details concerning this proposal are in the PRI itself:
http://www.unicode.org/review/pri186/

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

PRI #185: Revision of UBA for improved display of URL/IRIs

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 period for the new item closes on July 27, 2011.

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

PRI #185 Revision of UBA for improved display of URL/IRIs

The Unicode Bidirectional Algorithm (UBA), specified in UAX #9, was designed for handling ordinary text, and predated the rise of the web. Unfortunately, IRI/URLs are not ordinary text; they are syntactically complex in ways that don't work well with the UBA. That causes IRIs that contain right-to-left text (such as Arabic or Hebrew) to appear jumbled, to the point where the IRIs are either uninterpretable, misleading, or ambiguous. In particular the ambiguous displays could cause security problems.

The background document for this PRI provides a detailed description of the problem, and proposes a solution. The Unicode Technical Committee would like feedback on the feasibility of the proposal, and in particular, on the open issues listed in the background document.

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

PRI #184: Proposed update UTS 37 has been updated

The proposed update for UTS #37 has been updated with a minor change in section 3. Please see: http://www.unicode.org/review/pri184/ and the draft for details.
http://www.unicode.org/reports/tr37/tr37-6.html