1--- 2title: Coverage Levels 3--- 4 5# Coverage Levels 6 7There are four main coverage levels as defined in the [UTS \#35: Unicode Locale Data Markup Language (LDML) Part 6: Supplemental: 8 Coverage Levels](https://www.unicode.org/reports/tr35/tr35-info.html#Coverage_Levels). They are described more fully below. 8 9## Usage 10 11You can use the file **common/properties/coverageLevels.txt** (added in v41\) for a given release to filter the locales that they support. For example, see [coverageLevels.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/coverageLevels.txt). (This and other links to data files are to the development versions; see the specific version for the release you are working with.) For a detailed chart of the coverage levels, see the [locale\_coverage.html](https://unicode-org.github.io/cldr-staging/charts/43/supplemental/locale_coverage.html) file for the respective release. 12 13The file format is semicolon delimited, with 3 fields per line. 14 15 16```Locale ID ; Coverage Level ; Name``` 17 18Each locale ID also covers all the locales that inherit from it. So to get locales at a desired coverage level or above, the following process is used. 19 201. Always include the root locale file, **root.xml** 212. Include all of the locale files listed in **coverageLevels.txt** at that level or above. 223. Recursively include all other files that inherit from the files in \#2\. 23 - **Warning**: Inheritance is not simple truncation; the **parentLocale** information in [supplementalData.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/supplementalData.xml) needs to be applied also. See [Parent\_Locales](https://www.unicode.org/reports/tr35/tr35.html#Parent_Locales). 24 - For example, if you include fr.xml in \#2, you would also include fr\_CA.xml; if you include no.xml in \#2 you would also include nn.xml. 25 26### Filtering 27 28To filter "at that level or above", you use the fact that basic ⊂ moderate ⊂ modern, so 29 301. to filter for basic and above, filter for basic\|moderate\|modern 312. to filter for moderate and above, filter for moderate\|modern 32 33### Migration 34 35As of v43, the files in **/seed/** have been moved to **/common/**. Older versions of CLDR separated some locale files into a 'seed' directory. Some implementations used for filtering, but the criteria for moving from seed to common were not rigorous. To maintain compatibility with the set of locales used from previous versions, an implementation may use the above process for Basic and above, but then also add locales that were previously included. For more information, see [CLDR 43 Release Note](https://cldr.unicode.org/index/downloads/cldr-43). 36 37## Core Data 38 39**The data needed for a new locale to be added. See [Core Data for New Locales](https://cldr.unicode.org/index/cldr-spec/core-data-for-new-locales) for details on Core Data and how to submit for new locales.** 40 41**It is expected that during the next Survey Tool cycle after a new locale is added, the data for the Basic Coverage Level will be supplied.** 42 43## Basic Data 44 45**Suitable for locale selection and minimal support, eg. choice of language on mobile phone** 46 47This includes very minimal data for support of the language: basic dates, times, autonyms: 48 491. Delimiter Data —Quotation start/end, including alternates 502. Numbering system — default numbering system \+ native numbering system (if default \= Latin and native ≠ Latin) 513. Locale Pattern Info — Locale pattern and separator, and code pattern 524. Language Names — in the native language for the native language and for English 535. Script Name(s) — Scripts customarily used to write the language 546. Country Name(s) — For countries where commonly used (see "Core XML Data") 557. Measurement System — metric vs UK vs US 568. Full Month and Day of Week names 579. AM/PM period names 5810. Date and Time formats 5911. Date/Time interval patterns — fallback 6012. Timezone baseline formats — region, gmt, gmt\-zero, hour, fallback 6113. Number symbols — decimal and grouping separators; plus, minus, percent sign (for Latin number system, plus native if different) 6214. Number patterns — decimal, currency, percent, scientific 63 64## Moderate Data 65 66**Suitable for “document content” internationalization, eg. content in a spreadsheet** 67 68Before submitting data above the Basic Level, the following must be in place: 69 701. Plural and Ordinal rules 71 - As in \[supplemental/plurals.xml] and \[supplemental/ordinals.xml] 72 - Must also include minimal pairs 73 - For more information, see [cldr\-spec/plural\-rules](https://cldr.unicode.org/index/cldr-spec/plural-rules). 742. Casing information (only where the language uses a cased scripts according to [ScriptMetadata.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/scriptMetadata.txt)) 75 - This will go into [common/casing](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/casing/) 763. Collation rules \[non\-Survey Tool] 77 - This can be supplied as a list of characters, or as rule file. 78 - The list is a space\-delimited list of the characters used by the language (in the given script). The list may include multiple\-character strings, where those are treated specially. For example, if "ch" is sorted after "h" one might see "a b c d .. g h ch i j ..." 79 - More sophisticated users can do a better job, supplying a file of rules as in [cldr\-spec/collation\-guidelines](https://cldr.unicode.org/index/cldr-spec/collation-guidelines). 804. The result will be a file like: [common/collation/ar.xml](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/collation/ar.xml) or [common/collation/da.xml](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/collation/da.xml). 81 82The data for the Moderate Level includes subsets of the Modern data, both in depth and breadth. 83 84## Modern Data 85 86**Suitable for full UI internationalization** 87 88Before submitting data at the Moderate Level, the following must be in place: 89 901. Grammatical Features 91 1. The grammatical cases and other information, as in [supplemental/grammaticalFeatures.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/grammaticalFeatures.xml) 92 2. Must include minimal pair values. 932. Romanization table (non\-Latin scripts only) 94 1. This can be supplied as a spreadsheet or as a rule file. 95 2. If a spreadsheet, for each letter (or sequence) in the exemplars, what is the corresponding Latin letter (or sequence). 96 3. More sophisticated users can do a better job, supplying a file of rules like [transforms/Arabic\-Latin\-BGN.xml](https://home.unicode.org/basic-info/projects/#!/repos/cldr/trunk/common/transforms/Arabic-Latin-BGN.xml). 97 98The data for the Modern Level includes: 99 100**\#\#\# TBD** 101 102## References 103 104For the coverage in the latest released version of CLDR, see [Locale Coverage Chart](https://unicode-org.github.io/cldr-staging/charts/latest/supplemental/locale_coverage.html). 105 106To see the development version of the rules used to determine coverage, see [coverageLevels.xml](https://github.com/unicode-org/cldr/blob/main/common/supplemental/coverageLevels.xml). For a list of the locales at a given level, see [coverageLevels.txt](https://github.com/unicode-org/cldr/blob/main/common/properties/coverageLevels.txt). 107 108