From 54af6dc96c5fb67bb5c9db45f8ce8616ac39102e Mon Sep 17 00:00:00 2001 From: Addison Phillips Date: Wed, 18 Sep 2024 11:28:47 -0700 Subject: [PATCH] Update note on exact numeric match for v46 Addresses #887 Non-normative changes to the notes specifically part of LDML46 --- spec/registry.md | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/spec/registry.md b/spec/registry.md index e6f5169b95..d89b957055 100644 --- a/spec/registry.md +++ b/spec/registry.md @@ -488,11 +488,11 @@ for examples. #### Determining Exact Literal Match > [!IMPORTANT] -> The exact behavior of exact literal match is only defined for non-zero-filled +> The exact behavior of exact literal match is currently only well defined for non-zero-filled > integer values. > Functions that use fraction digits or significant digits might work in specific > implementation-defined ways. -> Users should avoid depending on these types of keys in message selection. +> Users should avoid depending on these types of keys in message selection in this release. Number literals in the MessageFormat 2 syntax use the @@ -502,10 +502,19 @@ if, when the numeric value of `resolvedSelector` is serialized using the format the two strings are equal. > [!NOTE] -> Only integer matching is required in the Technical Preview. -> Feedback describing use cases for fractional and significant digits-based -> selection would be helpful. -> Otherwise, users should avoid using matching with fractional numbers or significant digits. +> The above description of numeric matching contains +> [open issues](https://github.com/unicode-org/message-format-wg/issues/675) +> in the Technical Preview, since a given numeric value might be formatted in +> several different ways under RFC8259 +> and since the effect of formatting options, such as the number of fraction +> digits or significant digits, is not described. +> The Working Group intends to address these issues before final release +> with a number of design options +> [being considered](https://github.com/unicode-org/message-format-wg/pull/859). +> +> Users should avoid creating messages that depend on exact matching of non-integer +> numeric values. +> Feedback, including use cases encountered in message authoring, is strongly desired. ## Date and Time Value Formatting