Schedule (Tentative)

Date Phase
06.29
 1.7.1 Released
07.01
 1.8 Development starts
10.16 1.8 Data submission starts
12.10   1.7.2 Released
12.13 1.8 Data submission ends - vetting starts
01.13 1.8 Data resolution, data/structure verification and correction starts
02.10 1.8 Final Candidate available
03.10 1.8 Target release date
For details, see Release Schedule.
See also Notification Services.

CLDR Project‎ > ‎

CLDR Change Requests

Requesting Changes

Contents

  1. 1 Requesting Changes
  2. 2 Adding New Locales
  3. 3 Possible Information Sources
    1. 3.1 General
    2. 3.2 Exemplar Characters
    3. 3.3 Language Names
    4. 3.4 Territory / Region Names
    5. 3.5 Currencies
    6. 3.6 Collation
    7. 3.7 Dates and Times
    8. 3.8 Transliteration
    9. 3.9 Mechanical Translations (only for reference)
There are two ways to request changes (for bug fixes or new features):

In CLDR Locale Bug Reports, please try to give as much information as possible to help address the issue, and please group related bugs (such as a list of problems with the LDML specification) into a single bug report.

Collation sequences are particularly tricky; for more information see Collation Guidelines.

Adding New Locales

If you would like to add data for a new locale, please file a bug requesting the addition (see CLDR Change Requests). You should also notify your CLDR contact (see Survey Tool Accounts).
  • A new locale is only added if someone commits to supplying data for at least minimal coverage of the locale.
    • at least basic coverage is strongly encouraged
  • if the locale has a non-Latin script, and there is not already a romanization in CLDR, you are encouraged to submit one.
  • Make sure that you pick the right locale code for the new data. See Picking the Right Language Code
  • In some cases, XML files in LDML format can be supplied. See Bulk Import of XML Data

Possible Information Sources

Sources and references may be standards or can also be dictionaries, journal style guides (such as The Economist Style Guide for English), and other available sources that provide guidance as to common practice. Online sources are preferred where available, since they can be more easily checked.

The goal is to follow common, customary practice. For example, language or territory display names should use the most recognizable name in common usage. This is generally not the official name. For example, one would use "Switzerland" not "Swiss Confederation".

Here are some possible resources for comparison of locale data. This is not an endorsement of the sources, merely a collation of possibly-useful links. To suggest additions to this list, file a Bug Report.

General

For English, The Economist Style Guide (unfortunately only hard copy):

For other languages, there should be similar guides for major publications.

Exemplar Characters

Language Names

Territory / Region Names

Currencies

Collation

Dates and Times

Transliteration

Mechanical Translations (only for reference)