message-format-wg
message-format-wg copied to clipboard
unicode-org
Developing a standard for localizable message strings
Surrogate code units (U+D800 through U+DBFF) cannot be encoded into UTF-8. Ref #268 This covers the most important part of #268, which is UTF-8 compatibility. I would also like to...
Per [`develop` syntax: Quoted Strings](https://github.com/unicode-org/message-format-wg/blob/972dc1f255f7a2f8a494c9abe8ae9f58827c5652/spec/syntax.md#quoted-strings), the only code points that may not appear between a string's opening and closing `"` unescaped are `"` itself and `\`, which means that multi-line...
**Is your feature request related to a problem? Please describe.** There are scenarios where a translation message needs to reference another message which is not statically known. To illustrate, let's...
**Is your feature request related to a problem? Please describe.** With select messages, the case often arises that it's desirable for the selector value (in particular a number) to also...
@markusicu wrote in https://github.com/unicode-org/message-format-wg/pull/230#issuecomment-1116903103: > About the markup syntax: Are these free-form, implementation-dependent tokens? Do you expect them to be HTML or TTS hints or accessibility hints? Without any distinctions,...
@markusicu wrote in https://github.com/unicode-org/message-format-wg/pull/230#issuecomment-1116903103: > The syntax so far is not clear about formatting functions and selection functions. It looks like "number" could be both, but they should be separate....
We've been using all kind of names in our separate proposals, and never managed to unify. But names are important, and it's about time to decide on this. Some examples:...
Metadata
Owner
Metadata
Developing a standard for localizable message strings