Addison Phillips

A common enough example of this in the current MessageFormat is the SelectFormat: an enumerated data value is used to select between messages (gender is a common example, but it...

I like the *idea* of contextual parameters. In practice, your code wouldn't look like the above examples. The customer's name ("Mikko") would be in a context variable or injected. Otherwise...

@zbraniecki Probably I didn't express it that well. We actually have a `LocalizationContext` object that we use to provide certain kinds of, well, localization-related context to the resource manager. What...

@grhoten Thanks for that summary. > There is a question about localizability. If you allow complex conditions that involves AND, OR, NOT and parentheses, that can make it hard for...

Actually, the translator shouldn't indicate this. It should be a formatting directive. Automatic (language-specific) handling should be part of the text transformation function in the formatter. ICU has some support...

In my opinion, we should seek as many implementations as possible, without favoring any specific one--or insisting on any specific one. So a test suite plus community implementations. There are...

I think my understanding may have evolved somewhat. If we're _only_ creating a pattern string format consumed by the runtime API, then I'm still free to create a resource format...

+1 to providing this by default. Note that when direction metadata is available the FSI should be replaced with the appropriate base-direction isolating control. Note too that @zbraniecki only mentions...

MFv1 selection is "best match", but also is necessarily nested: you can only ever evaluate one item at a time. MFv2 is using a matrix and so might work differently....

Thanks @eemeli for the explanation, which makes sense. I don't necessarily agree with it, since it requires the developer to arrange the matrix vs. letting the algorithm do it. My...