Axel Hecht

A few thoughts: Yes, documentation is lacking, and the biggest item of work we have planned for Fluent 1.0. The target of 1.0 will be tooling developers, so even then,...

Thanks for the example, I was looking for one. I finished up the brand.ftl part in https://gist.github.com/Pike/c1301c217e8fdb4246e55334049a5863#file-workload-low-ftl-L747

On a general note, I'm not a fan of putting linting rules into the implementation of serializers. It's mostly an even political opinion on mine, humans are right, machines are...

In the case of multi-variant branding, I think it's OK for some variations to have sub-optimal term shapes. Think of an online shop system (or Firefox/Thunderbird). I'd say that all...

I mean private in the sense that * they're localizer-generated (i.e., pontoon), * or even reference-localization specific (i.e. pontoon would not require a localization thereof), interesting problem around what to...

For ace/github, we'll need to see what the conflicts over the file extension `.ftl` means. Are there other extensions with multiple modes already? There's a starting point for Atom, too,...

I'd stick to the realm of semantic comments, whether we require it or not. Effectively, one could treat `# @syntax` the same way as `#!`, in particular in a well-known...

Should we already start adding them to tests that use 0.8 features? Namely call expressions and then also 6-hex unicode escapes? Also tests that check for non-`\` text, astrals, etc?

We could do that, too.

I think there are use-cases for the program to tell the localization which precision to use. A pretty simple one would be currency values. Probably also the case where things...