From bbb69f51328ab6c01b13b601353718817d8a386d Mon Sep 17 00:00:00 2001 From: "Steven R. Loomis" Date: Wed, 25 Oct 2023 17:46:12 -0500 Subject: [PATCH] CLDR-17145 v44: link fix for specs (#3363) --- docs/ldml/tr35-dates.anchors.json | 1 + docs/ldml/tr35-general.anchors.json | 3 +++ docs/ldml/tr35-general.md | 11 +++++----- docs/ldml/tr35-info.anchors.json | 3 +++ docs/ldml/tr35-info.md | 8 +++---- docs/ldml/tr35-keyboards.md | 4 ++-- docs/ldml/tr35-numbers.md | 2 +- docs/ldml/tr35-personNames.anchors.json | 4 ++++ docs/ldml/tr35.anchors.json | 28 ++++++------------------- docs/ldml/tr35.md | 12 +++++------ 10 files changed, 36 insertions(+), 40 deletions(-) diff --git a/docs/ldml/tr35-dates.anchors.json b/docs/ldml/tr35-dates.anchors.json index f65280af8c7..06d4b5ba02b 100644 --- a/docs/ldml/tr35-dates.anchors.json +++ b/docs/ldml/tr35-dates.anchors.json @@ -52,6 +52,7 @@ "elements-months-days-quarters-eras", "eras", "fallbackFormat", + "first-day-overrides", "Fixed_periods", "fixed-periods", "goals", diff --git a/docs/ldml/tr35-general.anchors.json b/docs/ldml/tr35-general.anchors.json index 0a3f5f1cf5a..2ee16dfc74d 100644 --- a/docs/ldml/tr35-general.anchors.json +++ b/docs/ldml/tr35-general.anchors.json @@ -132,6 +132,7 @@ "Transform_Rules_Syntax", "transform-rules", "transform-rules-syntax", + "transform-syntax-characters", "transforms", "Transforms", "Typographic_Names", @@ -139,10 +140,12 @@ "unicode-locale-data-markup-language-ldmlpart-2-general", "unicode-technical-standard-35", "Unit_Elements", + "Unit_Identifier_Uniqueness", "Unit_Identifiers", "Unit_Preference_and_Conversion", "Unit_Sequences", "unit-elements", + "unit-identifier-uniqueness", "unit-identifiers", "unit-preference-and-conversion-data", "unit-sequences-mixed-units", diff --git a/docs/ldml/tr35-general.md b/docs/ldml/tr35-general.md index 66e32fa592a..f0ca0aca64e 100644 --- a/docs/ldml/tr35-general.md +++ b/docs/ldml/tr35-general.md @@ -1003,7 +1003,7 @@ Some of the constraints reference data from the unitIdComponents in [Unit_Conver or <unitIdComponent type="per">.
  • Constraint: must not have a prefix as an initial segment.
    • -
  • Constraint: no two different base_components will share the first 8 letters. +
  • Constraint: no two different base_components will share the first 8 letters. (For more information, see Unit Identifier Uniqueness.)
    • @@ -1214,7 +1214,8 @@ For temperature, there is a special unit ``, wh For duration, there are special units such as `` and `` for indicating the age of a person, which requires special forms in some languages. For example, in "zh", references to a person being 3 days old or 30 years old would use the forms “他3天大” and “他30岁” respectively. -### Compound Units + +### Compound Units A common combination of units is X per Y, such as _miles per hour_ or _liters per second_ or _kilowatt-hours_. @@ -1848,7 +1849,7 @@ If the direction is `forward`, then an ID is composed from `target + "-" + sourc The `visibility` attribute indicates whether the IDs should be externally visible, or whether they are only used internally. -Note: In CLDR v28 and before, the rules were expressed as fine-grained XML. +Note: In CLDR v28 and before, the rules were expressed as fine-grained XML. That was discarded in CLDR version 29, in favor of a simpler format where the separate rules are simply terminated with ";". The transform rules are similar to regular-expression substitutions, but adapted to the specific domain of text transformations. The rules and comments in this discussion will be intermixed, with # marking the comments. The simplest rule is a conversion rule, which replaces one string of characters with another. The conversion rule takes the following form: @@ -2158,7 +2159,7 @@ Conversion rules can be forward, backward, or double. The complete conversion ru > b | c ← e { f g } h ; > ``` -The `completed_result` | `result_to_revisit` is also known as the `resulting_text`. Either or both of the values can be empty. For example, the following removes any a, b, or c. +The `completed_result` | `result_to_revisit` is also known as the `resulting_text`. Either or both of the values can be empty. For example, the following removes any a, b, or c. ``` [a-c] → ; @@ -2291,7 +2292,7 @@ Because the order of rules matters, the following will not work as expected c → s; ch → kh; ``` -The second rule can never execute, because it is "masked" by the first. +The second rule can never execute, because it is "masked" by the first. To help prevent errors, implementations should try to alert readers when this occurs, eg: ``` Rule {c > s;} masks {ch > kh;} diff --git a/docs/ldml/tr35-info.anchors.json b/docs/ldml/tr35-info.anchors.json index beba361e4e6..a215768227d 100644 --- a/docs/ldml/tr35-info.anchors.json +++ b/docs/ldml/tr35-info.anchors.json @@ -8,6 +8,7 @@ "Contents", "contents-of-part-6-supplemental", "conversion-data", + "conversion-mechanisms", "Coverage_Level_Data_Requirements", "Coverage_Level_Default_Values", "Coverage_Level_Definitions", @@ -18,6 +19,7 @@ "default-content", "default-values", "definitions", + "derived-unit-system", "discarding-offsets", "duplicate-units", "exceptional-cases", @@ -77,6 +79,7 @@ "Unit_Identifier_Normalization", "Unit_Preferences", "Unit_Preferences_Data", + "Unit_Preferences_Overrides", "unit-conversion", "unit-identifier-normalization", "unit-parsing-data", diff --git a/docs/ldml/tr35-info.md b/docs/ldml/tr35-info.md index 0cbae158968..9be4dbe9ffc 100644 --- a/docs/ldml/tr35-info.md +++ b/docs/ldml/tr35-info.md @@ -91,7 +91,7 @@ The LDML specification is divided into the following parts: * [Mixed Units](#mixed-units) * [Testing](#testing) * [Unit Preferences](#Unit_Preferences) - * [Unit Preferences Overrides](#Unit_Preferences_Data) + * [Unit Preferences Overrides](#Unit_Preferences_Overrides) * [Unit Preferences Data](#Unit_Preferences_Data) * [Constraints](#constraints) * [Caveats](#caveats) @@ -930,9 +930,9 @@ The systems attributes also apply to compound units, and are computed in the fol 1. The intersection of {… si …} and {… si_acceptable … } is {… si_acceptable …} 2. The intersection of {… metric …} and {… metric_adjacent … } is {… metric_adjacent …} -Examples: +Examples: ``` -systems(liter-per-hectare) +systems(liter-per-hectare) = {si_acceptable metric} ∪ {si_acceptable metric} = {si_acceptable metric} systems(meter-per-hectare) @@ -1119,7 +1119,7 @@ The [unitsTest.txt](https://github.com/unicode-org/cldr/blob/main/common/testDat Different locales have different preferences for which unit or combination of units is used for a particular usage, such as measuring a person’s height. This is more fine-grained than merely a preference for metric versus US or UK measurement systems. For example, one locale may use meters alone, while another may use centimeters alone or a combination of meters and centimeters; a third may use inches alone, or (informally) a combination of feet and inches. -### Unit Preferences Overrides +### Unit Preferences Overrides The determination of preferred units depends on the locale identifer: the keys mu, ms, rg, their values, the base locale (language, script, region) and the user preferences data. diff --git a/docs/ldml/tr35-keyboards.md b/docs/ldml/tr35-keyboards.md index 3eda4a9bec0..003dbdaf7a8 100644 --- a/docs/ldml/tr35-keyboards.md +++ b/docs/ldml/tr35-keyboards.md @@ -12,7 +12,7 @@ For the full header, summary, and status, see [Part 1: Core](tr35.md). > This is a technical preview of a future version of the LDML Part 7. See [_Status_](#status), below. > -> There are breaking changes, see [Compatibility Notice](#Compatibility_Notice) +> There are breaking changes, see [Compatibility Notice](#compatibility-notice) ### _Summary_ @@ -173,7 +173,7 @@ Some non-goals (outside the scope of the format) currently are: 2. Unification of platform-specific virtual key and scan code mapping tables. 3. Unification of pre-existing platform layouts themselves (e.g. existing fr-azerty on platform a, b, c). 4. Support for prior (pre 3.0) CLDR keyboard files. See [Compatibility Notice](#compatibility-notice). -5. Run-time efficiency. [LDML is explicitly an interchange format](./tr35.md#Introduction), and so it is expected that data will be transformed to a more compact format for use by a keystroke processing engine. +5. Run-time efficiency. [LDML is explicitly an interchange format](tr35.md#Introduction), and so it is expected that data will be transformed to a more compact format for use by a keystroke processing engine.