CLDR v36 beta available for testing
Peter Edberg via CLDR-Users
cldr-users at unicode.org
Fri Sep 27 18:28:52 CDT 2019
Dear CLDR users,
The beta version of Unicode CLDR 36 <http://cldr.unicode.org/index/downloads/cldr-36> is available for testing. The final release is expected on October 4.
Unicode CLDR 36 provides an update to the key building blocks for software supporting the world's languages. CLDR data is used by all major software systems <http://cldr.unicode.org/index#TOC-Who-uses-CLDR-> for their software internationalization and localization, adapting software to the conventions of different languages for such common software tasks.
CLDR 36 included a full Survey Tool data collection phase <https://www.unicode.org/cldr/charts/36/supplemental/locale_coverage.html>, adding approximately 32 thousand new translated fields, with significant increases to Basic-level coverage for several languages including az (Azerbaijani, Latin script), qu (Quechua), so (Somali), tg (Tajik, Cyrillic script). Seed data was added for several new languages including cic (Chickasaw), mus (Muscogee), osa (Osage, Osage script).
Enhancements in v36 include:
New Emoji 13 draft candidates’ names and search keywords are included in this release to support smooth adoption of the upcoming Emoji release (scheduled for release in 2020Q1 as part of Unicode 13)
New measurement units and patterns: dot-per-centimeter, dot-per-inch, em, megapixel, pixel, pixel-per-centimeter, pixel-per-inch; decade; therm-us; bar, pascal; and a pattern for combining units in a multiplicative relationship, such as “newton-meter”.
Extended Language Matching to have fallbacks for many encompassed languages.
Added more languageAliases from the BCP47 language subtag registry, for deprecated languages.
There are some infrastructure changes to be aware of, including:
The cldr repository has moved from subversion to git, and queries using Trac no longer work. See CLDR Change Requests <http://cldr.unicode.org/index/bug-reports> for new information.
The data in the cldr repository now preserves votes for inherited data, indicated with “↑↑↑”. In order to generate CLDR in the previous form without “↑↑↑” and with proper minimization, a new tool GenerateProductionData is available.
Note: Release data that has been processed with GenerateProductionData is available in a parallel cldr-staging repository, with the same release tags.
- Peter Edberg for CLDR
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the CLDR-Users