Zibi Braniecki

It is not. FTL syntax focuses on error recoverability from any syntactic error ensuring that the parser can find the start of the next entry. In result a compromise had...

> Does CLDR even distinguish this case? AFAICS it doesn't. It does. You can read more about it in https://www.unicode.org/reports/tr35/tr35-numbers.html#Language_Plural_Rules In particular, a lot about operands and CLDR plural rules...

As Axel suggested, in Fluent, this could be: ``` key = { TONE() -> [formal] ... *[informal] ... } ```

probably all intl formatters as well since they may end up using different locale in fallback scenarios and even in a single-locale scenario may require isolation. See https://github.com/tc39/ecma402/pull/290

yeah, that sounds right. @srl295 - do you have any backpointers or experience with interpolation and bidi? If we localize the `NumberLiteral` using `Intl.NumberFormat` to the same locale as the...

Thanks @aphillips ! > Assuming we can get implementations fixed, then yes all placeables should be wrapped in isolating controls. Do you mean *all* placeables, or just the ones we...

> Why do you believe this to be the case? Because they should be in the same locale. MessageReference in Fluent happens in such a case: ```ftl close-window = Close...

While working on https://bugzilla.mozilla.org/show_bug.cgi?id=1435915 I found a use case for this feature. There's an API there which constructs a description of the application handler. It can be a localizable term,...

This would also help with cases where a message value is used as an attribute in another element. Example 1: https://searchfox.org/mozilla-central/rev/588d8120aa11738657da93e09a03378bcd1ba8ec/browser/locales/en-US/browser/preferences/preferences.ftl#35 could be: ```properties pane-general-title = General pane-search-title = Search...

Aaand another use case: ``` language-pl = Polish language-fr = French region-pl = Poland region-us = United States locale-pattern = { $language } ($region}) ```