Axel Hecht

I'd argue that this falls into the bucket of https://github.com/projectfluent/fluent/wiki/Good-Practices-for-Developers#prefer-separate-messages-over-variants-for-ui-logic.

I think keeping these as parse errors is good. They're in the way of runtime fallback, they're showing up as translated strings in pontoon, etc.

I'm pretty sure that you'll hit a declension problem, too. That is, the dateformat function will produce "Wednesday" in a grammatical form that's OK for standalone, but not in the...

There's also the point that you can't enforce a localization to actually implement 7 weekdays in one string. That's one of the corner stones of Fluent. Localizations are allowed to...

This sounds like something rather tough to implement for the python parser, is there enough to gain?

I think this discussion would be a great fit for https://discourse.mozilla.org/c/fluent. Mostly, because it's actually a discussion, and also because I am confident that variables are just a small part...

I think we should split this up. This is way too big to reason about at this point. High-level comments: * `@foo`: I don't think that JSDoc is a good...

We talked about moduralization of fluent specs, and I think semantic comments would be a good example. Should we have a repo for just semantic comments (`projectfluent/comments` or `projectfluent/semantic-comments`), with...

Resolver behavior is unspecified, so different behavior between implementations is expected for now. I just filed #294 to propose restrictions on what functions are expected to do. Note, for our...

Interesting idea, though I guess the _small subset_ is the interesting part to nail down. The way that would make sense to me is _a small subset of SGML or...