Contents

1. 1 Downloads
   1. 1.1 Key
2. 2 JSON Data
3. 3 Repository Access
   1. 3.1 Simple Browsing
   2. 3.2 Advanced Git Access
4. 4 Repository Organization
5. 5 POSIX Data
6. 6 TEST Data
7. 7 CLDR 1.0 Release

Each release of the Unicode CLDR is a stable release and may be used as reference material or cited as a normative reference by other specifications. Each version, once published, is absolutely stable and will never change. Implementations may also apply CLDR Corrigenda to a release. Bug reports and feature requests for subsequent versions may be filed at Bug Reports.

Downloads

The following table lists the files for each released version. For license information, see the Unicode Terms of Use; in particular, Exhibit 1. The top two rows have permalinks for the latest version and the latest development version (snapshot). They are followed by the specific release versions.

Key

• The Release Note contains a general description of the contents of the release, and any relevant notes about the release.
• The Data link points to a set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see Repository Organization).
• The Spec is the version of UTS #35: LDML that corresponds to the release.
• The Delta document points to a list of all the bug fixes and features in the release, which be used to get the precise corresponding file changes using BugDiffs.)
• The git tag can be used to get the files in git.

Access to the latest working snapshot of CLDR, and access to data collected for other platforms is available through the web. The SVN Tag can be used to get the contents of the release, as described below.

JSON Data

Repository Access

Note: CLDR has transitioned to Jira/Github.
CLDR files are maintained in a git source code repository at https://github.com/unicode-org/cldr.git .  

Simple Browsing

For browsing a particular file for a particular version, or revision history of a particular file, use the GitHub Browser.  For example:

• Go to the latest French LDML file at https://github.com/unicode-org/cldr/blob/master/common/main/fr.xml.

For more access to the source repository, you can use an git client to check out or export LDML files directory from the repository at https://github.com/unicode-org/cldr.git 

• You will need "git-lfs" installed to be able to compile the CLDR tools. See https://git-lfs.github.com or use the Github Desktop client.

Repository Organization

At the top level of each SVN repository tree, there are a number of special folders, plus a number of platform folders. To see the structure, go to Trac Browser or SVN Browser. The special folders are listed below.

• common — CLDR data corresponding to the release
  • annotations — annotations and TTS names for characters (currently focused on emoji)
  • bcp47 — data for unicode locale extensions
  • casing — intended capitalization for various categories in each language, for use by the Survey Tool
  • collation — collation LDML files
  • dtd — the latest dtd files for the release
  • main — the main locale-dependent LDML files
  • properties — property files in UCD format
    
  • rbnf — rule-based number formats
    
  • segments  — rules for segmenting text
  • subdivisions  — names of region (country) subdivisions (currently just English)
  • supplemental  — additional files with non-linguistic data
  • transforms — data for transliteration and other text transforms
  • uca — customized Unicode collation data
  • validity — data for validating BCP47 identifiers
• exemplars — preliminary exemplar character data for locales outside of common
  
• keyboards —source files for the CLDR keyboard data
  
• seed — preliminary locales that do not yet have sufficient vetted data
• specs — source files for the LDML and rfc specifications
• tools — source for internal tools for processing CLDR data

The common, dtd, and tools folders are in each release.

POSIX Data

Note: Beginning with CLDR v21, the CLDR project will no longer publish POSIX-format locale sources as part of its distribution.  The POSIX locale generation tools will continue to be made available as a part of the release.  Developers who require POSIX compliant locales can generate them using these tools.

CLDR has historically included reference versions of POSIX-format locale source files that are generated using the default options for each supported locale. The reference versions of POSIX source information contain those data fields that are included in the POSIX specification.

Many operating system platforms provide additional extensions to the minimal POSIX required field set. Individual implementations may require addition of the platform-specific fields or a non-default character repertoire in order to provide full functionality on a given POSIX compliant operating system. As of the current release, the POSIX locale generation tools do not generate such platform-specific extensions, but they can be modified to support this.

TEST Data

Note: Beginning with CLDR v21, the CLDR project will no longer publish the conformance test files for CLDR data.  These files were intended to be used to validate behavior for certain fields, but have proven to be difficult to maintain and of limited usefulness.

CLDR 1.0 Release

The 1.0 version of CLDR is described here for historical interest only. It was hosted on the OpenI18N site before the CLDR project moved to the Unicode Consortium.

1.0 Version:	http://www.openi18n.org/spec/ldml/1.0/ldml-spec.htm
1.0 Namespace:	http://www.openi18n.org/spec/ldml
1.0 DTDs:	http://www.openi18n.org/spec/ldml/1.0/ldml.dtd http://www.openi18n.org/spec/ldml/1.0/ldmlSupplemental.dtd