message-format-wg
message-format-wg copied to clipboard
unicode-org
Developing a standard for localizable message strings
In the 2024-05-20 call, we [assigned an action item](https://github.com/unicode-org/message-format-wg/blob/main/meetings/2024/notes-2024-05-20.md#645-design-dataflow-for-composability-515-645) to "propose a way for functions to interact".
In the 2024-05-20 call, we assigned an action item to create a design document describing the requirements for error handling. This is in the discussion of #795 and based on...
Adds a new "basket" of **_date/time locale options_** that override defaults set in the current locale or an implementation-defined date/time _operand_ value. These are optional, and can be made available...
Closes #838 Adds definitions for `style=currency` and `style=unit` as OPTIONAL for `:number`. Support for compound operand values SHOULD be provided, and the corresponding `currency` and `unit` options MAY be provided....
Closes #784
This is a continuation for the changes of #728, defining a _fallback value_ explicitly as a _resolved value_, and rephrasing the parts of the spec that refer to resolution failures...
Closes #675 The current text depends on "the JSON string representation of the numeric value of `resolvedSelector`", which is rather fuzzy: There is no _the_ JSON string representation of a...
The rule for `content-char` currently looks like this: ``` content-char = %x01-08 ; omit NULL (%x00), HTAB (%x09) and LF (%x0A) ... / %x3001-D7FF ; omit surrogates / %xE000-10FFFF ......
I think the algorithm for variant selection is much too complicated. That is, I think we can structure it in a way that gets the same results, but is not...
Metadata
Owner
Metadata
Developing a standard for localizable message strings