Core Data for New Locales

This document describes the minimal data needed for a new locale. There are two kinds of data:

• 1. Core XML Data - This is data that the CLDR committee needs from the proposer before a new locale is added. The proposer is expected to also get a Survey Tool account, and contribute towards the Minimal Data.

  2. Minimal Data Commitment - Data that is expected to be provided for each locale. If it is not supplied in the next Survey Tool cycle, the committee may remove the locale.

(The parenthesis at the start of each line below has the approximate number of strings for each item.)

Core XML Data

First, make sure you have correct language code according to Picking the Right Language Identifier. Then collect and submit the following data, using the Core Data Submission Form.

Note to translators: If you are having difficulties or questions about the following data, please contact us: file a new bug, or post a follow-up to comment to your existing bug.

• 1. (04) Exemplar sets: main, auxiliary, index. [main/xxx.xml]

• • These must reflect the Unicode model. For more information, see tr35-general.html#Character_Elements.

• 1. (02) Orientation (bidi writing systems only) [main/xxx.xml]

  2. (01) Plural rules [supplemental/plurals.xml]

• • For more information, see cldr-spec/plural-rules.

• 1. (01) Default content script and region (normally: normally country with largest population using that language, and normal script for that). [supplemental/supplementalMetadata.xml]

  2. (N) Verify the country data ( i.e. which territories in which the language is spoken enough to create a locale ) [supplemental/supplementalData.xml]

1. (N) Casing information (cased scripts only, according to ScriptMetadata.txt)

   • This will be in common/casing

• 1. (N) Collation rules [non-Survey Tool]

• • For details, see cldr-spec/collation-guidelines.

  • The result will be a file like: common/collation/ar.xml or common/collation/da.xml.

  • Note that the "search" collators (which tend to be large) are not needed initially.

Recommended Core Data

The following are not required, but are strongly recommended:

• 1. (04) Exemplar set: punctuation. [main/xxx.xml]

  2. (01) Ordinal rules [supplemental/ordinals.xml]

• • For more information, see cldr-spec/plural-rules.

• 1. *(N) Romanization table (non-Latin writing systems only) [spreadsheet, we'll translate into transforms/xxx-en.xml]

• • If a spreadsheet, for each letter (or sequence) in the exemplars, what is the corresponding Latin letter (or sequence).

  • More sophisticated users can do a better job, supplying a file of rules like transforms/Arabic-Latin-BGN.xml.

Minimal Data Commitment

This data is to be entered using the Survey Tool except as noted.

• 1. (44+) 4 main Date/Time formats, 12 long&abbreviated, format&stand-alone month-names, 7 long&abbreviated day-names, 2 long day periods.

1. (01) Name of the language in the language.

   1. (N) For any country locales, name of the country in the language, name/symbol for that country's currency. Must be at least one, for the default content locale.

   2. (02) Datetime pattern, intervalFormatFallback

   3. (05) (for Latn) decimal and grouping separators; decimal, currency, percent formats

   4. (N) Names of countries (territories) with that language as official.

   5. (M) Names of exemplarCities in multizone countries with that language as official

   6. (05) Timezone patterns [http://cldr.unicode.org/translation/timezones]

   7. (02) localePattern/Separator [http://cldr.unicode.org/translation/localepattern]

   8. (03) key names

   9. (14) long/short unit names (time intervals)