Common Locale Data Repository
Nowadays, Common Locale Data Repository has become a topic of general interest that has captured the attention of a wide public. The relevance of Common Locale Data Repository has generated a debate that ranges from political and social spheres to everyday conversations. For decades, Common Locale Data Repository has been the subject of study and research in different fields of knowledge, which has given rise to vast accumulated knowledge about its importance and impact on modern society. In this article, we will explore the various facets of Common Locale Data Repository and its influence on our daily lives, analyzing its evolution over time and its future implications.
 |
| Common Locale Data Repository | |
|---|---|
| Developed by | Unicode Consortium |
| Initial release | CLDR 1.0 (19 December 2003[1]) |
| Latest release | |
| Container for | XML[3] |
| Website | cldr |
The Common Locale Data Repository (CLDR) is a project of the Unicode Consortium to provide locale data in XML format for use in computer applications. CLDR contains locale-specific information that an operating system will typically provide to applications. CLDR is written in the Locale Data Markup Language (LDML).
CLDR is maintained by a technical committee which includes employees from IBM, Apple, Google, Microsoft, and some government-based organizations. The committee is chaired by John Emmons, of IBM; Mark Davis, of Google, is vice-chair.[4]
Details
Among the types of data that CLDR includes are the following:
- Translations for language names
- Translations for territory and country names
- Translations for currency names, including singular/plural modifications
- Translations for weekday, month, era, period of day, in full and abbreviated forms
- Translations for time zones and example cities (or similar) for time zones
- Translations for calendar fields
- Patterns for formatting/parsing dates or times of day
- Exemplar sets of characters used for writing the language
- Patterns for formatting/parsing numbers
- Rules for language-adapted collation
- Rules for spelling out numbers as words
- Rules for formatting numbers in traditional numeral systems (such as Roman and Armenian numerals)
- Rules for transliteration between scripts, much of it based on BGN/PCGN romanization
The information is currently used in International Components for Unicode, Apple's macOS, LibreOffice, MediaWiki, and IBM's AIX, among other applications and operating systems.
CLDR overlaps somewhat with ISO/IEC 15897 (POSIX locales). POSIX locale information can be derived from CLDR by using some of CLDR's conversion tools.
The CLDR covers 400+ languages.[5]
References
- ^ "CLDR Releases/Downloads". cldr.unicode.org.
- ^ "Release 48". 29 October 2025. Retrieved 11 November 2025.
- ^ Updating DTDs, CLDR makes special use of XML because of the way it is structured. In particular, the XML is designed so that you can read in a CLDR XML file and interpret it as an unordered list of <path,value> pairs, called a CLDRFile internally. These path/value pairs can be added to or deleted, and then the CLDRFile can be written back out to disk, resulting in a valid XML file. That is a very powerful mechanism, and also allows for the CLDR inheritance model.
- ^ "Unicode CLDR - CLDR Process".
- ^ "Locale Coverage".
External links
- Common Locale Data Repository, the informational webpage of the CLDR project
- Locale Data Markup Language
