Axel Hecht

I think it makes sense to look at our options in a post-TS world again.

I agree that we should do this, and that we should make it opt-in. > 1. Should we allow more elements by default, including block elements? Any translation would be...

This is how it's designed to work. See also https://projectfluent.org/fluent/guide/terms.html. The reasoning is that the variations of Terms are something internal to the localization, and thus shouldn't be visible to...

For technical-minded people, it's common to think about refactors and coding patterns. For translators, in our experience, that mindset is far fetched, and they're much better off with a sequence...

You're talking about https://github.com/projectfluent/fluent.js/blob/8ed4e4b235d27daed2db697c1d18f67e8b8baba1/fluent-dom/src/overlay.js#L77-L83 ? Yes, I think that can go away, at least in a gecko context where we know that we ran compare-locales.

We have a thread open on discourse on what to do on broken references, see https://discourse.mozilla.org/t/on-message-and-termreferences/53217. On top of that, @stasm, do you remember how much of the optimism is...

From my perspective, Fluent parsing is always successful. That's also how the spec is built, and both js parsers and the python parser implement it like that. Even if one...

Yuck. Before we go too much into the technical detail of solving this, we should make sure that UX really likes the way this works right now. @zbraniecki, can you...

Right, it might be a bit trickier to get right. We'd need to keep `open-foo`, `open-foo[var]` and `open-foo.bar` distinct.

This has come up again in the light of [bug 1498444](https://bugzilla.mozilla.org/show_bug.cgi?id=1498444), where we need a pre- and post-label around a drop-down with localized entries. There are two issues here, AFAICT:...