message-format-wg
message-format-wg copied to clipboard
unicode-org
Developing a standard for localizable message strings
I am currently working on implementing the mf2 spec in Python and I'm trying to understand why `FunctionExpression` and `UnsupportedExpression` are two separate entities in the data model. Could we...
Add user-stories and examples to the expression attributes design.
The current spec ([`spec/errors.md`](https://github.com/unicode-org/message-format-wg/blob/main/spec/errors.md#error-handling)) says: > In all cases, when encountering a runtime error, > a message formatter MUST provide some representation of the message. > An informative error or...
An observation from [implementing](https://github.com/messageformat/messageformat/compare/mf2-source-bidi) bidi isolation as proposed in #781, but which also applies to the currently proposed design for [bidi usability](https://github.com/unicode-org/message-format-wg/blob/main/exploration/bidi-usability.md): Isolating quoted patterns on the outside adds LRI,...
An observation from [implementing](https://github.com/messageformat/messageformat/compare/mf2-source-bidi) bidi isolation as proposed in #781, but which also applies to the currently proposed design for [bidi usability](https://github.com/unicode-org/message-format-wg/blob/main/exploration/bidi-usability.md): Requiring the pairing of `open-isolate` and `close-isolate` sets...
The core idea is to provide explicit and well-defined support for `u:id`, `u:locale`, and `u:dir` when used as function or markup options, and to thereby clarify that expression attributes have...
In #753 , @echeran brought up the example of a custom function `getSystemTimeInMillisNow()` that would return the current time. In the [spec intro](https://github.com/unicode-org/message-format-wg/blob/main/spec/formatting.md#introduction) we currently have the language: "This specification...
In [this comment](https://github.com/unicode-org/message-format-wg/pull/774#discussion_r1592459297) I noted that the current spec contains untestable normative requirements about certain types of error (such as emitting syntax/data model errors "as early as possible"). My proposal...
Context: #523 This moves the accepted & rejected design docs to a more likely location under `docs/design/`, and fixes their titles & metadata. A README is added to that folder....
Maintaining the list of normative changes during tech preview.
Metadata
Owner
Metadata
Developing a standard for localizable message strings