message-format-wg
message-format-wg copied to clipboard
Developing a standard for localizable message strings
During the February meetings, we ended up leaving out the `:number` `style` values `currency` and `unit`, and their related options: `currency`, `currencyDisplay`, `currencySign`, `unit`, `unitDisplay`. Furthermore, we also include this...
Consider the following message: ```mf2 .input {$count :integer} {{You have {$count} apples.}} ``` From my understanding this would be identical to the following message, were it allowed. ```mf2 .local $count...
The WG decided in the 2024-07-01 call not to support the DTD for the function registry as a normative part of the specification. We need to update our various non-normative...
Previously, this stated that markup resolution MUST always succeed. However, resolution of `u:` options can fail, so that wasn't true.
See #1082 for some of the discussion leading to this proposal. This is an alternative to #1077, where instead of `dateStyle` and `timeStyle` we start with the following options: -...
I was re-reading the `MessageValue` example and noticed that it's easy to skip over what the last three methods are for, so I added a reference to the earlier text....
I wanted to spin this off from #866, #1077, #1067, etc., in order to focus on the syntax of the options. I'll focus on date fields, time precision, and zone...
As discussed on the 2025-06-02 call, this PR removes the "Draft" status from the `:datetime`, `:date`, and `:time` functions, while leaving their _field options_ as "Draft". The intent here is...
Currently, `:unit` suffers from many of the same problems as, for example, `u:locale`, explained in #1006. Since the unit being formatted is provided by the `Measure` input type (which I...