The Unicode CLDR 49 Beta is now available for specification review and integration testing. The release is planned for October 21th, 2026, but any feedback on the specification needs to be submitted well in advance of that date. The beta specification is available at Draft LDML Modifications. See also the Migration section of the new release page.
CLDR provides the key building blocks for software to support the world's languages (dates, times, numbers, sort-order, etc.). All major browsers and all modern mobile phones use CLDR for language support. (See Who uses CLDR?)
Via the Survey Tool, contributors supply data for their languages. This data is a factor in determining which languages are supported on mobile phones and computer operating systems.
The beta has already been integrated into the development versions of ICU 79, and ICU4X . We would especially appreciate feedback from non-ICU consumers of CLDR data and on Migration issues. Feedback can be filed at CLDR Requesting Changes.
The following are some of the most significant changes to the CLDR specification (LDML).
Clarified the process of selecting the best dateFormatItem when there is no exact match, and how to use appendItems to add missing fields.
In the Key/Type Description table, added a description of which keys/types use constructed values and a brief description of the typeValue element.
For plural rules, made it clear that they are evaluated in semantic order (zero, then one,…).
Part 5: Collation will be updated to accurately reflect the changes that were upstreamed into UTS #10 as part of Unicode 18.0.
MessageFormat updates:
- The :currency and :percent functions are now Stable, with the same implementations as previously.
- The u:locale option (previously in Draft) has been dropped from the specification.
- Clarified the computation of the exemplar city for non-location zones.
The following new items were added:
- placeholderBoundarySpacing to allow characters to be inserted where necessary, such as between digits in Chinese dates.
- Added support for ordinal dates with a new dayOfMonth (and parent elements) for days that are not purely numeric. This is used for ordinal dates, like “Sept 13th, 2026”. (Technical Preview.)
- Date-Timezone and Time-Day-Of-Week as fallback options for appendItem in dates.
- intervalFormatRange for constructing ranges (used internally for consistency checks).
- numericDateSeparator and numericTimeSeparator for customization of numeric dates and times (3-10-2031 → 3/10/2031). (Technical Preview.)
- alt (alternative) forms of gmtFormat and gmtUnknownFormat to request use of localized equivalents of the term “UTC” instead of “GMT” (limited locales).
- dualOffsetFormat so that the Localized GMT format can express differences more clearly (e.g., Los Angeles → GMT-8/-7; Phoenix → GMT-7; Denver → GMT-7/-6).
- numberSystem in currency formats to allow for different formats for locales with multiple number systems.
- nestedBracketReplacement (48.2) for constructing locale names with parts that have parentheses, e.g., ”birmanês (Mianmar [Birmânia])”.
For a full list of new elements and attributes, see Delta DTDs. There are many more changes that are important to implementations, such as changes to certain identifier syntax and various algorithms. See the Modifications section of the specification for details.
For more details see the draft CLDR 49 release page, which has information on the changes to data and structure, accessing the data, reviewing charts of the changes, and — importantly — Migration issues.




.png)