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

Developing a standard for localizable message strings

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

**Is your feature request related to a problem? Please describe.** In addition to issue https://github.com/unicode-org/message-format-wg/issues/16, it's helpful to be able to detect grammatical gender, grammatical number and even grammatical case...

requirements

**Is your feature request related to a problem? Please describe.** Some message formatting APIs only allow you to make a single choice with respect to language/locale. This single choice is...

requirements

**Is your feature request related to a problem? Please describe.** Currency and its format is already documented to some extent by Unicode but to my knowledge, MessageFormat support is not...

requirements

This thread is a spin-off from [the requirements gathering (issue #3)](https://github.com/unicode-org/message-format-wg/issues/3) about the way timezone is handled in formatting a date/time value. **Original description:** > The way a timezone adjustment...

requirements

As we gather the requirements, I'd like to start the discussion about something slightly broader: design principles. By that I mean statements and guidelines which we want to follow and...

design

Historically, localization was always predominantly a server-side, relatively static operation. Majority of (non-l10n) engineers I worked with usually start with a concept that l10n is a phase done **as early...

requirements

_A dedicated issue for discussing a newly proposed design dimension, similar to those proposed in #50._ **Data Model vs. Syntax** Do we focus our efforts on agreeing to a data...

design

In the data model, are we okay with treating functions as first-class data, such that we can include functions as a part of the data model for MF input? @zbraniecki...

design

_A dedicated issue for discussing one of the design dimensions proposed in #50._ #### People-Friendly vs. Machine-Friendly If we end up defining the syntax for messages, who should the target...

design

_A dedicated issue for discussing one of the design dimensions proposed in #50._ #### Resilient vs. Strict How far do we want to go to provide fault tolerance in case...

design