The Unicode Common Locale Data Repository provides the largest standard repository of locale data for software internationalization.
CLDR is the Unicode Common Locale Data Repository, which provides the largest and most extensive standard repository of locale data available. It supplies key building blocks for software internationalization and localization, enabling applications to adapt to the conventions of different languages and regions. The data is used for common software tasks that require cultural and linguistic adaptation.
Software developers, internationalization engineers, and companies building applications that need to support multiple languages and cultural conventions. It's particularly valuable for organizations with global software deployments.
Developers choose CLDR because it offers the most comprehensive and standardized locale data available, ensuring consistent internationalization across different platforms. Its wide industry adoption and Unicode backing provide reliability and interoperability that proprietary solutions cannot match.
The home of the Unicode Common Locale Data Repository
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides the largest and most extensive standard repository of locale data available, as highlighted in the README, ensuring support for a vast array of languages and cultural conventions.
Backed by Unicode and used by a wide spectrum of companies, offering a trusted, standardized foundation for internationalization that ensures interoperability across platforms.
Supplies key building blocks for adapting software to different conventions, enabling consistent localization for common tasks like date, time, and number formatting.
Released under Unicode's terms and license, promoting transparency and avoiding vendor lock-in, which is essential for long-term maintainability in global software.
Offers data files rather than ready-to-use APIs, requiring significant parsing and integration effort, as developers must handle the XML/JSON structures directly.
Data is released in versions (e.g., CLDR 49 in development, not for production use), meaning fixes or new locale support require waiting for scheduled releases, limiting agility.
Requires a Contributor License Agreement (CLA) for contributions, as noted in CONTRIBUTING.md, which can deter community input and slow down issue resolution.
Building and running CLDR tools involves Maven dependencies and separate licenses, adding complexity to setup and maintenance beyond simple data usage.