Unicode CLDR 23 has been released, providing an update to the key building blocks for software supporting the world's languages.

Unicode CLDR 23.0 contains data for 215 languages and 227 territories—654 locales in all. This release focused primarily on improvements to the LDML structure and tools, and on consistency of data. It includes substantially improved support for non-Gregorian calendars (such as the Japanese Imperial calendar used extensively in Japan). The data and structure has also been modified to easily permit changing between 12 and 24 hour formats, and between 2 digit and 4 digit years. The new Unicode character is used for the Turkish Lira, and information is provided for currencies that round to 5 cents (or other subunits) in cash transactions. For most languages that use non-Latin scripts, characters in the language’s script now collate before those in other scripts (including A-Z). Language-specific letter-casing changes (Lower, Upper, Title) have been added for Azerbaijani, Greek, Lithuanian, and Turkish. Keyboard data has also been updated for Android. Also, as of this release, the LDML specification is split into multiple parts, each focusing on a particular area.

The release had a short cycle so that we could move to the new regular semi-annual schedule. It thus only included a limited data submission phase, for 4 languages only: Armenian (hy), Georgian (ka), Mongolian (mn), and Welsh (cy). For those languages, the data increased by over 100%.

---

About the Unicode Consortium

The Unicode Consortium is a non-profit organization founded to develop, extend and promote use of the Unicode Standard and related globalization standards. The membership of the consortium represents a broad spectrum of corporations and organizations in the computer and information processing industry. Members are: Adobe Systems, Apple, Google, Government of Andhra Pradesh, Government of Bangladesh, Government of India, IBM, Microsoft, Monotype Imaging, Oracle, SAP, Tamil Virtual University, The University of California (Berkeley), Yahoo!, plus well over a hundred Associate, Liaison, and Individual members. For more information, please contact the Unicode Consortium http://www.unicode.org/contacts.html.

The Unicode® Consortium today announced the start of beta review for the forthcoming Unicode 6.3.0. All beta feedback must be submitted by April 29, 2013.

The main feature of Unicode 6.3 is the update of the Unicode Bidirectional Algorithm and five newly-encoded bidirectional format control characters: U+061C ARABIC LETTER MARK and the isolate span controls U+2066..U+2069. This version also rolls in various minor corrections for errata and other small updates for the Unicode Character Database.

Unicode is the foundation for all modern software and communications around the world, including all modern operating systems, browsers, and smart phones; modern web protocols (HTML, XML,...); and internationalized domain names. Thus it is important to ensure a smooth transition to each new version of the Unicode Standard. Software developers and other experts are strongly encouraged to review the beta data files and documentation for Unicode 6.3.0 carefully, and to provide any feedback regarding errors or other issues to the Unicode Consortium. Software developers can also get an early start in testing their programs with the beta data files so they will be ready for the release of Unicode 6.3.0 in June, 2013.

• See http://www.unicode.org/versions/beta-6.3.0.html, for information about testing the 6.3.0 beta.
• See http://www.unicode.org/versions/Unicode6.3.0/ for the current draft summary of Unicode 6.3.0.

Unicode is a project that has been built by hundreds of people over many decades. Some people involved in this project are no longer with us, and we wish to remember their contributions: http://www.unicode.org/consortium/memoriam.html

The UTC has posted a new Public Review Issue regarding a proposal to specify optional conjuncts in Malayalam.

In Malayalam there are two prevailing orthographies, traditional and reformed. Both are written using the same Malayalam character set. The difference between them is typically manifested only by the font. Traditional orthography accommodates more full conjuncts, while the reformed orthography would use visible virama (Chandrakkala) separated sequences for many of those full conjuncts.

This proposal specifies the further use of ZWJ and ZWNJ in sequences in the Malayalam script to indicate preferences for optional display of conjuncts. Such sequences are intended to indicate the preferences, both for rendering systems that support the reformed Malayalam orthography and for systems that support the traditional Malayalam orthography.

The UTC is seeking feedback on this proposal, regarding its advisability and potential impacts on implementations, as well as any suggestions for alternative approaches to the issues raised in the background document.

A new FAQ page devoted to the topic of private-use characters, noncharacters, and sentinels has been posted on the Unicode web site. This FAQ aims to clear up confusion about whether noncharacters are permitted in Unicode text, and how they differ from ordinary private-use characters. The recently published Corrigendum #9: Clarification About Noncharacters makes it clear that noncharacters are permitted even in interchange, and the new FAQ page addresses some of the fine points about their usage and about differences from other types of Unicode code points. The brief mentions of noncharacters in other FAQ pages have also been updated accordingly.

Are you unclear about what Unicode “noncharacters” even are? The new FAQ page also answers basic questions about noncharacters and private-use characters, and provides a bit of history about how they came to be part of the Unicode Standard.

SUBMISSION DEADLINE: Friday, March 29th

| Submit Abstract Form |

There has been confusion about whether noncharacters were permitted in Unicode text. The new Corrigendum #9: Clarification About Noncharacters makes it clear that noncharacters are permissible even in open interchange, although their intended semantics may not be interpretable in such contexts. ​The UTF-8, UTF-16, UTF-32 & BOM FAQ has also been updated for clarity​, and other informative text about noncharacters will be revised over time​, including the Core Specification.

Background. There are 66 noncharacters permanently reserved for internal use, typically used for some sort of internally-defined control function or sentinel value. They should be supported by APIs, components, and applications that handle (i.e., either process or pass through) all Unicode strings, such as a text editor or string class. Where an application does make internal use of a noncharacter, it should take some measures to sanitize input text from unknown sources. The best practice is to replace that particular noncharacter on input by U+FFFD. (The noncharacter should not be simply deleted, since that can cause security problems. For more information, see Section 3.5 Deletion of Code Points in UTR #36, Unicode Security Guidelines.)

The Internationalization and Unicode Conference (IUC) is the premier event covering the latest in industry standards and best practices for bringing software and Web applications to worldwide markets. This annual event focuses on software and Web globalization, bringing together internationalization experts, tools vendors, software implementers, and business and program managers from around the world.

Expert practitioners and industry leaders present detailed recommendations for businesses looking to expand to new international markets and those seeking to improve time to market and cost-efficiency of supporting existing markets. Recent conferences have provided specific advice on designing software for European countries, Latin America, China, India, Japan, Korea, the Middle East, and emerging markets.

This highly rated conference features excellent technical content, industry-tested recommendations and updates on the latest standards and technology. Subject areas include cloud computing, upgrading to HTML5, integrating with social networking software, and implementing mobile apps. This year's conference will also highlight new features in Unicode Version 6.1 and other relevant standards published this year.
Reasons to Attend Include:

• Tutorials and sessions for beginners, to train you and your staff on basic practices and implementation techniques for creating international software
• Learn recommended solutions to difficult problems or sophisticated requirements from industry leaders and experts in attendance
• Find help from tool and product vendors to get you to market quickly and cost-effectively

Atom