message-format-wg icon indicating copy to clipboard operation
message-format-wg copied to clipboard

Developing a standard for localizable message strings

Results 249 message-format-wg issues
Sort by recently updated
recently updated
newest added

I investigated using a mock implementation, and there is nothing really standing in the way of adding an offset option to :number. This could be done as an icu:offset option,...

registry
Action-Item
Preview-Feedback
LDML46.1

There have been multiple comments on the need to define the term "resolved value", which we use formally but have defined somewhat informally.

normative
formatting
Seek-Feedback-in-Preview
LDML46

Quoting @macchiati: > 2. For the spec, the plan is: > 1. Steven Loomis will create a Part 9 .md file, with the right header/footer > 2. For Mar 4,...

Action-Item
specification
LDML45

_This is a spin-off from #665, which conflates this issue's nominal topic with a discussion of the `timeZone` options. The text below is an extract of the original by @aphillips._...

functions
LDML48

This partially addresses #661 by allowing the LRM character in message whitespace. This is whitespace **_outside_** pattern `text`. Tools can use this to help ensure that messages are formatted visually...

syntax
specification
LDML46

I was looking at https://github.com/unicode-org/message-format-wg/pull/659/, but found a number of issues in the Registry section before the Default Registry. Capturing them here. In the Conformance and Use: The term 'registry'...

Stale
registry

Our current grammar for markup is this: ```abnf markup = "{" [s] "#" identifier *(s option) *(s attribute) [s] "}" ; open / "{" [s] "#" identifier *(s option) *(s...

syntax
Seek-Feedback-in-Preview
LDML46

After the discussions in https://github.com/unicode-org/message-format-wg/pull/621#discussion_r1480050162 and https://github.com/unicode-org/message-format-wg/pull/621#discussion_r1490144092 as well as our live calls, we ended up leaving out an explicit definition of numerical matching for non-integer values like 0.0 or...

functions
LDML48

In #621 around [here](https://github.com/unicode-org/message-format-wg/pull/621#discussion_r1480118323) I noticed, in response to @eemeli's comment, that [Function Resolution](https://github.com/unicode-org/message-format-wg/blob/main/spec/formatting.md#function-resolution) has a bias towards _formatting_ functions. We also have [Resolve Selectors](https://github.com/unicode-org/message-format-wg/blob/main/spec/formatting.md#resolve-selectors) later, which wants to emit...

specification
formatting
LDML46

_A follow-up to #368._ The current draft of the registry uses named regex patterns to allow defining rules for validating literal arguments and option values. ```xml ``` And then: ```xml...

registry
LDML46