message-format-wg
message-format-wg copied to clipboard
unicode-org
Developing a standard for localizable message strings
#474 pivoted into a discussion about variant patterns. Consequently, we now lack a good design doc about the text-first mode, _a.k.a._ unquoted simple patterns. I can recall a few arguments...
(Creating a task to do some cleanup on our repo)
I want to come up with a good example that shows the use of case inflections. (I realize that is not in scope for the MVP coming up, and don't...
CC @mradbourne, who should be added to the repo. As [discussed yesterday](https://github.com/unicode-org/message-format-wg/blob/main/meetings/2024/notes-2024-04-22.md#738), our error categories could be improved. This PR effects the categorisation we discussed, with "Message Function Error" introduced...
As initially observed at https://github.com/unicode-org/message-format-wg/pull/774#discussion_r1578160893
Fixes #736, Works on #747 This design document describes the effect of selectors on subsequent pattern placeholders of the same operand. It presents several alternatives. This is still in "DRAFT"...
During publication of v45, I found that we were missing a number of terms that we actively use in the specification. Among these are: - variable - external variable -...
As discussed during today's call, we should communicate more clearly that using undefined options may allow for writing currently-errorfree messages that later turn into errors.
This PR adds a schema for the JSON test files and refactors the existing test files to match the schema. The schema is designed for easy interoperability with the `unicode/conformance`...
CC @mradbourne Given that we shouldn't rely on `:number` and `:datetime` producing exact results but we still want to ensure that our interfaces with them work, let's add `:test:number` and...
Metadata
Owner
Metadata
Developing a standard for localizable message strings