Locale Data Summary for et [Estonian]

Notes:

1. CLDR nr is white for the few languages present in ver 1.4, red for newly added language names.
2. 1.4 must be corrected - language names must be lowercase
3. English is a bit better off omitting 'language'. In Estonian, 99% entries silently assume 'language' in the end
4. 1.5 recommendation - use only 3-letter acronyms, 1.4 is a bit of a mess
5. Comments have parallel names, which are also possible
6. the entries have mixed types: language, language group, group/territory+other, meta (root, no linguistic content)
7. language itself can be dead or artificial
8. root is not translated
9. similar languages may not be adjacent when the list is sorted. Is it better to sort (Other) together?
10. there is a strange Finno-Ugric (other) present here, using only Latin script. Why?
11. if ALL languages are presented as a choice in e.g pulldown menu, the user is overwhelmed with data and in difficulties
12. Finnish data

These supply localized names for these items for use in user-interfaces for displaying lists of locales and scripts. Examples are given below. Translation of deprecated codes into other languages is discouraged. Where present, the display names must be unique; that is, two distinct code would not get the same display name. (There is one exception to this: in timezones, where parsing results would give the same GMT offset, the standard and daylight display names can be the same across different timezone IDs.) Any translations should follow customary practice for the locale in question. For more information, see [Data Formats]. languages: This contains a list of elements that provide the user-translated names for language codes, as described in Section 3, Identifiers. The type can actually be any locale ID as specified above. The set of which locale IDs is not fixed, and depends on the locale. For example, in one language one could translate the following locale IDs, and in another, fall back on the normal composition. Thus when a complete locale ID is formed by composition, the longest match in the language type is used, and the remaining fields (if any) added using composition.