Axel Hecht

I've come full circle on this one. I still like the API and its intent, but the implications on the engineering and localization processes are tough. I can see dynamic...

So, Zibi's example is actually interesting in two ways: Firstly, it emulates message references. And message references are easy, and also kinda pointless as they're completely atomic. Secondly, it adds...

I would just go for computed values and retranslations.

Conceptually, I see a term reference as a deep-dive into locale-specific territory. Stepping back out into app territory feels wrong to me. Also, like a term-abuse case, most likely. We...

I see the point, but I'm not sure that the answer lies in the syntax specification. There might be something like implementation notes, where we suggest that parser implementers protect...

So, for the first issue, you could have a term for `-dialog-button-yes`, and use a term reference in each dialog instance. Then a localization could do ``` -dialog-button-yes = Yes...

You can use `fluent.migrate`, which is now on pypi, and add custom parsers to compare-locales. This isn't documented, really, but you can follow what we do in https://github.com/mozilla/bedrock/blob/master/lib/l10n_utils/management/commands/_fluent_ftl.py along with...

You're looking for parametrized terms, https://projectfluent.org/fluent/guide/terms.html. FWIW, terms are not to group information, but to encapsulate terms that might change on context. Branding is one example, and the purpose of...

I smell #80?

@zbraniecki, any idea? I've done a tad of research, and found http://cldr.unicode.org/translation/capitalization and http://cldr.unicode.org/development/development-process/design-proposals/grammar-and-capitalization-for-date-time-elements. Which implies that anything on the CLDR/ICU front would return lower-case strings for Hungarian, even in...