Francesco Lodolo

> I think nobody will want to have to type smart quotes every time in order to satisfy this rule. Or am I thinking about this part wrong? Yes, you...

Just stumbled upon this. We moved away from gitbook for the l10n docs, and it was pretty straightforward. Hard to point to a single commit, but you can get an...

> I think keeping these as parse errors is good. +1. Without concatenations, I don't expect us to have a lot of use cases for empty strings, most of the...

A couple of thoughts on point 1: * We don't know what Pontoon is going to look like with Translate.Next. But we know a lot of localizers coming from Pootle...

Please don't ping random people, I'm not a developer for this add-on.

If the goal is to parse comments, and extract information about parameters, I feel like we should enforce `@param`. If it's only about documenting the parameters, that your last example...

#### Title Line 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...

> If I read your statement correctly it starts with "I don't understand" and finishes with "and thus I believe the proposal is invalid" :) I'm happy to answer your...

> Please remember that we're designing syntax not just for Gecko. I think that's one point that I tend to forget in such discussions. And translation memory seems definitely an...

I'm also surprised that identifiers cannot start with a number (I don't think I've ever seen it mentioned in docs?) https://github.com/projectfluent/fluent/blob/master/spec/fluent.ebnf#L86