The following are the files for this release. For a description of their purpose and format, see the Key; for more details see CLDR Releases (Downloads).
Unicode CLDR 21.0.2 is an update release, with no new translations. It contains only additional BCP47 data for the T extensions approved by the committee (see New BCP47 Extension T Fields) and a deprecation of one U extension: "direct" collation.
These new T Extension fields and subfields [RFC 6497] are now available for use in BCP47 and Unicode Locale/Language Identifiers. The CLDR committee approved new fields of the T extension for different domains, allowing users of the T extensions to ignore types of subfields that are not relevant to them, and to group related subfields in an organized fashion. The new T extension fields and subfields are defined in the following files, as part of the CLDR 21.0.2 release:
- "zh-t-i0-pinyin", to indicate Chinese text generated with a pinyin input method
- "en-t-k0-dvorak", to identify a Dvorak keyboard for English
- "it-t-k0-osx-extended", to request an extended Mac keyboard for Italian
The private use subfields can be used for private agreements, such as:
- "ru-t-en-x0-mobile", to indicate a translation from English to Russian for use on a mobile device, or
- "ja-t-de-t0-und-x0-medical", to identify a machine translation from German to Japanese with a specialized dictionary for medical terms.
For more information on what else has changed since the 2.0.1 release, see the CLDR 21 Release Note and the CLDR 21.0.1 Release Note.
- The Release Note contains a general description of the contents of the release, and any relevant notes about the release.
- The Data link points to a set of zip files containing the contents of the release (the files are complete in themselves, and do not require files from earlier releases -- for the structure of the zip file, see Repository Organization).
- The Spec is the version of UTS #35: LDML that corresponds to the release.
- The Delta document points to a list of all the bug fixes and features in the release, which be used to get the precise corresponding file changes using BugDiffs.)
- The SVN Tag can be used to get the files via Repository Access.