Zibi Braniecki

@mathjazz @Pike @stasm @flodolo @adngdb @hkasemir - can I get your feedback here please? I'd like to start unifying our comments around those concepts if they're approved.

> (Title Line) I'm not sure this practice needs to be codified as a rule. I think there is a value. > IIUC any such derivation will make our comments...

> I don't see a great advantage in having a title for section comments. In case, I would prefer something more explicit than relying on position and empty lines, i.e....

> I'm not sure that would work, from a legal perspective, given that we had to copy and paste the same license header to all files for a while now....

Based on conversation with Stas I added an example for meta-data about `simple` strings to instruct CAT to warn against using any placeables in a given file/group/message.

Separated out into issues. Skipped colors for now.

The reason is of course math, and the fact that we handle numbers. The answer is in https://github.com/projectfluent/fluent/blob/master/spec/fluent.ebnf but we can probably document is more in the guide

Yes, math. Math is the reason, if you want to support math, you have to support substraction operator which in most cases, including Fluent is going to be "-". Once...

Umm, I'm not as concerned as you. We can reason and explain our positions and I don't find it concerning. Math operations and operators are frequently made available for the...

`key = { SELECTOR(1-key2) - > *[if] Foo [else] faa }` The reason is not just compliance. It's to protect our ability to extend syntax by adding likely operations. We...