From a5a9678a9e8e8075b01fcb8d13b9cd7b970b1281 Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Tue, 16 Apr 2024 12:20:31 -0500 Subject: [PATCH] CLDR-17529 v45 spec to final --- docs/ldml/tr35-collation.md | 10 +++---- docs/ldml/tr35-dates.md | 10 +++---- docs/ldml/tr35-general.md | 10 +++---- docs/ldml/tr35-info.md | 50 ++++++++++++++++----------------- docs/ldml/tr35-keyboards.md | 10 +++---- docs/ldml/tr35-messageFormat.md | 10 +++---- docs/ldml/tr35-numbers.md | 10 +++---- docs/ldml/tr35-personNames.md | 2 +- docs/ldml/tr35.md | 12 ++++---- 9 files changed, 62 insertions(+), 62 deletions(-) diff --git a/docs/ldml/tr35-collation.md b/docs/ldml/tr35-collation.md index 4dc21bcda07..7ace3fb4e50 100644 --- a/docs/ldml/tr35-collation.md +++ b/docs/ldml/tr35-collation.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 5: Collation -|Version|45 (draft) | +|Version|45 | |-------|----------------| |Editors|Markus Scherer (markus.icu@gmail.com) and other CLDR committee members| @@ -21,12 +21,12 @@ See for up-to-date CLDR release data. ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ diff --git a/docs/ldml/tr35-dates.md b/docs/ldml/tr35-dates.md index 08320011b6f..3d03026ae7d 100644 --- a/docs/ldml/tr35-dates.md +++ b/docs/ldml/tr35-dates.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 4: Dates -|Version|45 (draft) | +|Version|45 | |-------|------------------| |Editors|Peter Edberg and other CLDR committee members| @@ -16,12 +16,12 @@ This is a partial document, describing only those parts of the LDML that are rel ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ diff --git a/docs/ldml/tr35-general.md b/docs/ldml/tr35-general.md index a15ffef2fa8..ee0ae4b5904 100644 --- a/docs/ldml/tr35-general.md +++ b/docs/ldml/tr35-general.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 2: General -|Version|45 (draft) | +|Version|45 | |-------|---------------------| |Editors|Yoshito Umaoka (yoshito_umaoka@us.ibm.com) and other CLDR committee members| @@ -21,12 +21,12 @@ See for up-to-date CLDR release data. ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ diff --git a/docs/ldml/tr35-info.md b/docs/ldml/tr35-info.md index 6b92dc6fcd1..bb3dfb22eb0 100644 --- a/docs/ldml/tr35-info.md +++ b/docs/ldml/tr35-info.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 6: Supplemental -|Version|45 (draft) | +|Version|45 | |-------|-----------| |Editors|Steven Loomis (srloomis@unicode.org) and other CLDR committee members| @@ -21,12 +21,12 @@ See for up-to-date CLDR release data. ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ @@ -828,7 +828,7 @@ For example the following values can be suffixes in a simple_unit identifier suc ``` -This data lists the SI prefixes that can be applied to units (typically limited to prefixable units), +This data lists the SI prefixes that can be applied to units (typically limited to prefixable units), such as the following: ```xml @@ -844,15 +844,15 @@ such as the following: ``` -The information includes the SI prefix and symbol, and the power of 10 or power of 2 +The information includes the SI prefix and symbol, and the power of 10 or power of 2 (for binary prefixes, intended for use with digital units). -Note that the translated short form of a unit prefix is not the same as the localized symbol. -The localized symbol may be the same for most Latin-script languages, +Note that the translated short form of a unit prefix is not the same as the localized symbol. +The localized symbol may be the same for most Latin-script languages, but depending on the customary use in a language they can be in a different script or use different letters even in Latin-script languages. They are, however, the same in the root locale. -The newer prefixes (quecto-, ronto-, -ronna, -quetta) are not yet being translated, +The newer prefixes (quecto-, ronto-, -ronna, -quetta) are not yet being translated, because the appropriate translated versions have not yet been well established across languages. ### Constants @@ -1162,11 +1162,11 @@ The examples in #4 are due to the following ordering of the `unitQuantity` eleme ## Mixed Units -Mixed units, or unit sequences, are units with the same base unit which are listed in sequence. +Mixed units, or unit sequences, are units with the same base unit which are listed in sequence. Common examples are feet and inches; meters and centimeters; hours, minutes, and seconds; degrees, minutes, and seconds. Mixed unit identifiers are expressed using the "-and-" infix, as in "foot-and-inch", "meter-and-centimeter", "hour-and-minute-and-second", "degree-and-arc-minute-and-arc-second." -Scalar values for mixed units are expressed in the largest unit, according to the sort order discussed above in "Normalization". +Scalar values for mixed units are expressed in the largest unit, according to the sort order discussed above in "Normalization". For example, numbers for "foot-and-inch" are expressed in feet. Mixed unit identifiers should be from highest to lowest (eg foot-and-inch instead of inch-and-foot), and that is reflected in the display. @@ -1183,25 +1183,25 @@ Implementations may offer mechanisms to control the precision of the formatted m * Locale A uses decimal degrees and gets 1.53°. * Locale B uses degrees, minutes, seconds, and gets 1° 31′ 31.44″ * Locale B has an unnecessarily precise result: the equivalent of 1.52540 in precision. -* An implementation could allow a percentage precision; - thus 1612 meters with ±1% precision would be represented by **1 mile** rather than **1 mile 9 feet**. +* An implementation could allow a percentage precision; + thus 1612 meters with ±1% precision would be represented by **1 mile** rather than **1 mile 9 feet**. The default behavior is to round the lowest unit to the nearest integer. Thus 1.99959 degree-and-arc-minute-and-arc-second would be (before rounding) **1 degree 59 minutes 58.524 seconds**. -After rounding it would be **1 degree 59 minutes 59 seconds**. +After rounding it would be **1 degree 59 minutes 59 seconds**. If the lowest unit would round to zero, or round up to the size of the next higher unit, then the next higher unit is rounded instead, recursively. Thus 1.999862 degree-and-arc-minute-and-arc-second would be (before rounding) **1 degree 59 minutes 59.5032 degrees**. After rounding the last unit it would be **1 degree 59 minutes 60 seconds**, which rounds up to **1 degree 60 minutes**, which rounds up to **2 degrees**. This behavior can be determined before having to compute the lower units: -for example, where rounding to the second, if the remainder in degrees is below 1/120 degrees or above 119/120 degrees, then the degrees can be rounded without computing the minutes or seconds. +for example, where rounding to the second, if the remainder in degrees is below 1/120 degrees or above 119/120 degrees, then the degrees can be rounded without computing the minutes or seconds. ## Testing -The files in the directory [cldr/common/testData/units/](https://github.com/unicode-org/cldr/tree/main/common/testData/units) are provided for testing implementations. +The files in the directory [cldr/common/testData/units/](https://github.com/unicode-org/cldr/tree/main/common/testData/units) are provided for testing implementations. 1. The [unitsTest.txt](https://github.com/unicode-org/cldr/blob/main/common/testData/units/unitsTest.txt) file supplies a list of all the CLDR units with conversions 2. The [unitPreferencesTest.txt](https://github.com/unicode-org/cldr/blob/main/common/testData/units/unitPreferencesTest.txt) file supplied tests for user preferences -3. The [unitLocalePreferencesTest.txt](https://github.com/unicode-org/cldr/blob/main/common/testData/units/unitLocalePreferencesTest.txt) file provides examples for testing the interactions between locale identifiers and unit preferences. +3. The [unitLocalePreferencesTest.txt](https://github.com/unicode-org/cldr/blob/main/common/testData/units/unitLocalePreferencesTest.txt) file provides examples for testing the interactions between locale identifiers and unit preferences. Instructions for use are supplied in the header of the file. @@ -1229,7 +1229,7 @@ For example: | 4 | en-DE | Celsius | because explicit region is DE | | 5 | en | Fahrenheit | because the likely region for en with no region is US | -If any key-values are invalid, then they are ignored. Thus the following constructs are ignored: +If any key-values are invalid, then they are ignored. Thus the following constructs are ignored: | subtags | reason | | --- | --- | @@ -1240,7 +1240,7 @@ If any key-values are invalid, then they are ignored. Thus the following constru ‡ Only the region portion is currently used, so in -rg-usabcdef the "abcdef" is ignored, whether or not it is valid. -The following algorithm is used to compute the override units, regions, and category. +The following algorithm is used to compute the override units, regions, and category. The latter two items are used in the [Unit Preferences Data](#Unit_Preferences_Data). #### Compute override units @@ -1255,7 +1255,7 @@ If there is no valid -mu value, the following steps are used to determine a regi Otherwise FR is not used. In either case continue with step 2. 2. If there is a valid -rg region, let R be that region, and go to Compute the category. 3. If there is a valid region in the locale, let R be that region, and go to Compute the category. -4. Otherwise, compute the likely subtags for the locale. +4. Otherwise, compute the likely subtags for the locale. 1. If there is a likely region, then let R be that region, and go to Compute the category. 2. Otherwise, let R be 001, and go to Compute the category @@ -1271,7 +1271,7 @@ A **category** is determined as follows from the input unit: 1. From the input unit, use the conversion data in [baseUnit](tr35-info.md#Unit_Conversion) and let the **input base unit** be the baseUnit attribute value. * eg, for `pound-force` the baseUnit is `kilogram-meter-per-square-second`. -2. If there is no such base unit (such as for a an unusual unit like `ampere-pound-per-foot-square-minute`), +2. If there is no such base unit (such as for a an unusual unit like `ampere-pound-per-foot-square-minute`), convert the input unit to a combination of base units, reduce to lowest terms, and normalize. Let the **input base unit** be that value. * eg, `ampere-pound-per-foot-square-minute` ⇒ `kilogram-ampere-per-meter-square-second` @@ -1281,7 +1281,7 @@ A **category** is determined as follows from the input unit: An implementation may also set it to an equivalent metric/SI unit, as in the example below. This terminates the algorithm; there is no need to use the unit preferences information. * For example, for `ampere-pound-per-foot-square-minute` an implementation could return `kilogram-ampere-per-meter-square-second` or `pascal-ampere`. - * That is, an implementation can use shorter metric/SI units as long as long as the combination is equivalent in value. + * That is, an implementation can use shorter metric/SI units as long as long as the combination is equivalent in value. ### Unit Preferences Data @@ -1362,7 +1362,7 @@ The following is the algorithm for computing the preferred output unit from the 1. If the lookup fails, let the **input usage** be its containing usage, and repeat. (This will always terminate is always a 'default' usage for each category.) 2. The containing usage is the result of truncating the last '-' and following text, if there is a '-', and other wise 'default' * For example, land-agriculture-grain ⊂ land-agriculture ⊂ land ⊂ default -3. Let ranked units be the result of a lookup of R in the category-usage preferences. There may be both region values and [containment regions](https://www.unicode.org/cldr/charts/latest/supplemental/territory_containment_un_m_49.html). +3. Let ranked units be the result of a lookup of R in the category-usage preferences. There may be both region values and [containment regions](https://www.unicode.org/cldr/charts/latest/supplemental/territory_containment_un_m_49.html). 1. If the lookup of R fails, set R to its containing region and repeat. (This will always terminate because 001 is always present.) * For example, CH (Switzerland) ⊂ 155 (Western Europe) ⊂ 150 (Europe) ⊂ 001 (World). * This loop can be optimized to only include containing regions that occur in the data (eg, only 001 in LDML 45). @@ -1376,7 +1376,7 @@ The ranked units will be of the following form: yard yard ``` - + * The geq item gives the value for the unit in the element value (or for the largest unit for mixed units). For example, * `...geq="0.5">mile<...` is ≥ 0.5 miles * `...geq="100.0">foot-and-inch<...` is ≥ 100 feet diff --git a/docs/ldml/tr35-keyboards.md b/docs/ldml/tr35-keyboards.md index 4bfbc127ff6..473f807e366 100644 --- a/docs/ldml/tr35-keyboards.md +++ b/docs/ldml/tr35-keyboards.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 7: Keyboards -|Version|45 (draft) | +|Version|45 | |-------|-------------| |Editors|Steven Loomis (srloomis@unicode.org) and other CLDR committee members| @@ -21,12 +21,12 @@ See for up-to-date CLDR release data. ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ diff --git a/docs/ldml/tr35-messageFormat.md b/docs/ldml/tr35-messageFormat.md index 01c873407ce..9726a96bca4 100644 --- a/docs/ldml/tr35-messageFormat.md +++ b/docs/ldml/tr35-messageFormat.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 9: Message Format -|Version|45 (draft) | +|Version|45 | |-------|------------------------| |Editors|Addison Phillips and [other CLDR committee members](tr35.md#Acknowledgments)| @@ -16,12 +16,12 @@ This is a partial document, describing only those parts of the LDML that are rel ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ diff --git a/docs/ldml/tr35-numbers.md b/docs/ldml/tr35-numbers.md index 4c170cbecf5..afd2f946f7d 100644 --- a/docs/ldml/tr35-numbers.md +++ b/docs/ldml/tr35-numbers.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 3: Numbers -|Version|45 (draft)| +|Version|45 | |-------|----------| |Editors|Shane F. Carr (shane@unicode.org) and other CLDR committee members| @@ -16,12 +16,12 @@ This is a partial document, describing only those parts of the LDML that are rel ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._ diff --git a/docs/ldml/tr35-personNames.md b/docs/ldml/tr35-personNames.md index 7917ed346f2..0fdbc0cdc8c 100644 --- a/docs/ldml/tr35-personNames.md +++ b/docs/ldml/tr35-personNames.md @@ -2,7 +2,7 @@ # Unicode Locale Data Markup Language (LDML)
Part 8: Person Names -|Version|45 (draft) | +|Version|45 | |-------|------------------------| |Editors|Mark Davis, Peter Edberg, Rich Gillam, Alex Kolisnychenko, Mike McKenna and [other CLDR committee members](tr35.md#Acknowledgments)| diff --git a/docs/ldml/tr35.md b/docs/ldml/tr35.md index 22fe5cc17cd..1742ebd9a33 100644 --- a/docs/ldml/tr35.md +++ b/docs/ldml/tr35.md @@ -2,10 +2,10 @@ # Unicode Locale Data Markup Language (LDML) -|Version|45 (draft)| +|Version|45 | |-------|----------| |Editors|Mark Davis (markdavis@google.com) and other CLDR committee members| -|Date|2024-04-15| +|Date|2024-04-16| |This Version|https://www.unicode.org/reports/tr35/tr35-72/tr35.html| |Previous Version|https://www.unicode.org/reports/tr35/tr35-71/tr35.html| |Latest Version|https://www.unicode.org/reports/tr35/| @@ -26,12 +26,12 @@ See for up-to-date CLDR release data. ### _Status_ -_This is a draft document which may be updated, replaced, or superseded by other documents at any time. + - +_This document has been reviewed by Unicode members and other interested parties, and has been approved for publication by the Unicode Consortium. +This is a stable document and may be used as reference material or cited as a normative reference by other specifications._ > _**A Unicode Technical Standard (UTS)** is an independent specification. Conformance to the Unicode Standard does not imply conformance to any UTS._