CLDR Change Requests

Unicode CLDR Project‎ > ‎

Requesting Changes

Contents

1 Requesting Changes
2 When Do You Need a Survey Tool Account?
3 Adding New Locales
4 Possible Information Sources

There are two ways to request changes (for bug fixes or new features):

File a Ticket: for

additions of new locales (see Adding New Locales)
defects in the survey tool
adding or changing non-language data (such as currency usage)
additions or changes to data that is not yet handled by the survey tool (collation, segmentation, and transliteration)
feature requests in CLDR or UTS #35: Locale Data Markup Language (LDML).

Use the CLDR Survey Tool: for all other proposed data (new or corrections).

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.

When Do You Need a Survey Tool Account?

With a Survey Tool account, you can make changes only in the locales for which you are specifically enabled, not in arbitrary locales. If you want to report a problem or error in some locale, especially if you are not an expert in that locale, you don't need an account, you can simply file a ticket.

You may wish to obtain a Survey Tool account...

if you are an expert in one or more locales and you need to vote on changes for things you think are incorrect, or to add some new data, in those locales only;
if you wish to add a new locale, and you already have the core data ready for submission.

You probably do not need a Survey Tool account...

if you want to report one bug, or a few bugs, in one or more locales;
if you want to suggest other changes.

Adding New Locales

If you would like to add data for a new locale, please File a Ticket requesting the addition. You should also notify your CLDR contact (see Survey Tool Accounts).

Make sure that you pick the right locale code for the new data. See Picking the Right Language Code
A new locale is only added if someone commits to supplying Core Data for New Locales.
In special cases, XML files in LDML format can be supplied. See Bulk Data Upload.

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

CIA World Factbook

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

http://www.amazon.com/exec/obidos/tg/detail/-/186197535X

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

CLDR - Unicode Common Locale Data Repository

Navigation

Milestone Schedule

Internal Development