![[Unicode]](https://www.unicode.org/webscripts/logo60s2.gif){kind=small} Technical Reports
|
| Version | 48 (draft) |
|---|---|
| Editors | CLDR committee members |
For the full header, summary, and status, see Part 1: Core.
This is a partial document, describing only the changes to the LDML since the previous release. For the other parts of the LDML see the main LDML document and the links above.
This is a draft document which may be updated, replaced, or superseded by other documents at any time. Publication does not imply endorsement by the Unicode Consortium. This is not a stable document; it is inappropriate to cite this document as other than a work in progress.
A Unicode Technical Standard (UTS) is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS.
Please submit corrigenda and other comments with the CLDR bug reporting form [Bugs]. Related information that is useful in understanding this document is found in the References. For the latest version of the Unicode Standard see [Unicode]. For more information see About Unicode Technical Reports and the Specifications FAQ. Unicode Technical Reports are governed by the Unicode Terms of Use.
The LDML specification is divided into the following parts:
Changes in LDML Version 48 (Differences from Version 47)
language element menu values core and extension, and alt="menu".
Also revamped the description of how to construct names for locale IDs, for clarity.Hntl compound script. (This is also reflected in the <scriptData> elements in supplementalData.xml.)attribute component in the EBNF to be uattribute for consistency with ufield, etc.
and to reduce confusion with XML attributes.language subelement of languageData, the territory
attribute has been deprecated (and data using it has been removed). A better source for such information is the more detailed data
in Supplemental Territory Information.relative for relative date/times, such as "tomorrow at 10:00",
and updated the guidelines for using the different dateTimeFormat types.gmtUnknownFormat, to indicate when the timezone is unknown.usesMetazone, to specify which offset is considered standard time, and which offset is considered daylight.z timezone format symbol.
There is also now a mechanism for finding the region code from short timezone identifier, which is used for the non-location formats (generic or specific)era attributes in supplemental data, and how to determine the transition point in time between eras.product_unit and added an additional well-formedness constraint for mixed units.FractionalUCA_blanked.txt to the root collation data files.:offset function (previously named :math) is now available as Stable :datetime, :date, and :time draft functions are updated to build on top of semantic skeletons :percent is added as a new draft function display: Noted that a key without output may be indicated by means of the keyId= attribute on the display.layer: Noted the use of the modifiers= attribute for hardware layouts being used as touch layouts.Note that small changes such as typos and link fixes are not listed above. Modifications in previous versions are listed in those respective versions. Click on Previous Version in the header until you get to the desired version.
© 2001–2025 Unicode, Inc. This publication is protected by copyright, and permission must be obtained from Unicode, Inc. prior to any reproduction, modification, or other use not permitted by the Terms of Use. Specifically, you may make copies of this publication and may annotate and translate it solely for personal or internal business purposes and not for public distribution, provided that any such permitted copies and modifications fully reproduce all copyright and other legal notices contained in the original. You may not make copies of or modifications to this publication for public distribution, or incorporate it in whole or in part into any product or publication without the express written permission of Unicode.
Use of all Unicode Products, including this publication, is governed by the Unicode Terms of Use. The authors, contributors, and publishers have taken care in the preparation of this publication, but make no express or implied representation or warranty of any kind and assume no responsibility or liability for errors or omissions or for consequential or incidental damages that may arise therefrom. This publication is provided “AS-IS” without charge as a convenience to users.
Unicode and the Unicode Logo are registered trademarks of Unicode, Inc. in the United States and other countries.