W3C   Internationalization (I18n) Activity: Making the World Wide Web truly world wide!

i18n resources

Authoring X/HTML/CSS

New! Authoring SVG

Authoring XML

Developing specifications

Setting up a server

Developing schemas

Using the Web

Quick links

Planet Web i18n

Specifications

Articles, tutorials & best practices

I18n tests

About the Activity

Groups: Core, ITS, IG, JLTF

Mission, Contacts

Activity Statement

Participate!

Join a Working Group

Review a W3C specification

Translate a specification or page

Subscribe to the Interest Group list

Search for news

Admin

Unicode Collation Algorithm Version 5.2 Released

23 October 2009

Unicode Collation Algorithm Version 5.2 Released

Version 5.2 of the Unicode Collation Algorithm has been released. This version resynchronizes the Unicode Collation Algorithm with all of the updates for the Unicode Standard, Version 5.2.

The rest of this post is taken from the Unicode Consortium's release notification and details changes and issues for implementations.

  • The text of UTS #10 has been updated. Among other changes, the revised text for UTS #10 makes it clear that the BASE for implicit generation of weights for Han characters does not include unassigned code points.
  • There are small changes in Gujarati, Telugu, Malayalam (including weighting for chillus), Tamil, and Sinhala. While these changes move in the direction of expected behavior, good results will only come from tailoring for particular languages, such as with CLDR.
  • There have been significant changes to the ordering of many combining marks. Many combining marks that are not in customary use in modern languages now have the same secondary weight, and will only be distinguished on a fourth level, by code point ordering. This can be seen by looking at the Unicode Collation Charts (http://unicode.org/charts/collation/). In 5.2, many characters now have a white background, indicating that they sort exactly the same as the previous character, unless a 4th (codepoint) level is used.
  • Implementations of UCA should take note that the increased number of characters may cause overflows if the implementing code makes certain assumptions or optimizations. This can result either from the new character additions (which increase the number of distinct weights in the table) or because of changes in the way the weights, particularly for secondary weight values, are assigned in the table. The latter change may result in unexpected numbers of characters having the same weight.

Comments, Pingbacks:

No Comments/Pingbacks for this post yet...

Comments are closed for this post.


Questions or comments? ishida@w3.org
Powered by b2evolution