1--- 2title: Requesting Additions/Updates to CLDR Language/Population Data 3--- 4 5# Requesting Additions/Updates to CLDR Language/Population Data 6 7The main purpose of having language/population supplemental data in CLDR is for generating "likely subtags": determining which languages are likely to be useful in different locations. 8 9It is not a goal for this data to cover all possible languages, or even all the languages that might be used in a given country. 10 11Foremost, the data are intended to cover official languages of each country or region. Official languages are not necessarily the most widely used in a given region, but their status makes them necessary. For example, they may be constitutionally mandated, regionally official, official for use in particular application areas, and so forth. The data also cover languages in widespread use for large populations within countries, attempting to cover somewhere near 100% of the country's population when possible. Other languages with smaller user populations may be included based on special status or other perceived cultural importance within the country. 12 13Before adding data for a language and population, the committee needs to know the importance of the addition. It is not enough that a language be "in use". For example, within a country such as the United States, hundreds of languages are used, sometimes by fairly sizable populations, but they are not all useful additions to the CLDR supplemental data. 14 15For CLDR purposes, the language data focus on the usefulness with computer interfaces, rather than general utility as spoken languages. Data for primarily spoken languages are usually included only where the languages have official status. 16 17Requests to add or change language/population data must provide the following basic information: 18 19- language name 20- 2 or 3-letter language code 21- applicable country/region name 22- applicable country/region code 23- official status (and justification) 24- language population in the region 25- literacy in the language, where possible 26- links to reliable sources for population/literacy data 27 28 29Reliable sources for population data and official status are required for population updates and additions. While [Ethnologue](https://www.google.com/url?q=https%3A%2F%2Fwww.ethnologue.com%2F&sa=D&sntz=1&usg=AOvVaw02Rajsyksb8nOu8MESVtKi) may be a good source for "mother tongue" or native speaker data for more common languages, it is not a sufficient source on its own for population data on most languages. Recent government or NGO-sponsored census data are typically better sources. 30 31For language names and codes, some resources are: [Unicode CLDR charts](http://www.google.com/url?q=http%3A%2F%2Fwww.unicode.org%2Fcldr%2Fcharts%2Flatest%2F&sa=D&sntz=1&usg=AOvVaw0IfeZJzXzVdSLQDbkyoE4x), [IANA Language Subtag Registry](https://www.google.com/url?q=https%3A%2F%2Fwww.iana.org%2Fassignments%2Flanguage-subtag-registry%2Flanguage-subtag-registry&sa=D&sntz=1&usg=AOvVaw0KaE5Pb3Bfy7xyMSIiNrbi), and [Wikipedia](https://www.google.com/url?q=https%3A%2F%2Fen.wikipedia.org%2Fwiki%2FMain_Page&sa=D&sntz=1&usg=AOvVaw1NobdoSkQ4MRb3AWb_nNp3) articles on individual languages. 32 33Also for new additions, the request must include a rationale for inclusion and discuss the importance of the addition. 34 35Some examples of CLDR Trac tickets that include sufficient information include these: 36 37http://unicode.org/cldr/trac/ticket/9767 38 39http://unicode.org/cldr/trac/ticket/9680#comment:1 40 41http://unicode.org/cldr/trac/ticket/9609 42 43http://unicode.org/cldr/trac/ticket/9601#comment:2 44 45