Addison Phillips

You're right, although note that the trailing expression does not use any whitespace it captures. Presumably the reserved body should capture all trailing whitespace, in case it wants it for...

We removed reserved statement, so closing as out-of-scope

> Separately, we probably should add a requirement for functions not to assign any meaning to option order, such that :func foo=42 bar=13 and :func bar=13 foo=42 would always be...

> With maps for options, the serialization of a message becomes unstable in languages where maps keys are unordered. This may result in false positives when comparing serialized messages for...

What I think Mark is trying to ask for is that optional whitespace _inside_ expressions be permitted to contain bidi controls (tools should prefer isolating paired controls for this--specifically LRI/PDI)....

@eggrobin Thanks for this. > I would recommend, whatever you do, to include a conformance statement for https://www.unicode.org/reports/tr31/#R3a, so that there well-understood framework for reviewers and implementers to work with....

I think we should add a statement about R3a conformance. We are specifically an R3a-2 implementation, since we don't allow all of the whitespace characters in R3a-1. We would need...

Although the PR for this exists, the WG decided not to include this in LDML45 because it is late-breaking. See meeting notes [here](https://github.com/unicode-org/message-format-wg/blob/main/meetings/2024/notes-2024-02-26.md#673)

@sffc: in the constructor of what? A currency value should carry its currency code (and not just a number) around. A unit amount should likewise not forget it's unit.

(chair hat ON) Thank you for the feedback! The WG consensus in the [2024-10-28 teleconference](https://github.com/unicode-org/message-format-wg/blob/main/meetings/2024/notes-2024-10-28.md#topic-currency-and-unit-formatting-838-908-915) was to keep percentage formatting in `:number`/`:integer`. The name `style` is taken directly from `Intl.NumberFormat`...