Stanisław Małolepszy

> Some more thoughts on how this relates to #7: we could introduce our custom @-tags for language-specific meta information which would be ignored by tools like compare-locales In https://github.com/projectfluent/syntax/issues/7#issuecomment-275671311...

In #59 @zbraniecki asked about the possibility of using semantic comments for tags. I'm pasting my reply below to keep the discussion in one place. My understanding of the scope...

> Even before we move forward with this, can we get a consensus on how we'd like such comments to look like (…)? Isn't this the exact goal of this...

Nice work, @zbraniecki! This is very much in line with what I had in mind for this, thanks for adding substance and providing details. > Title line I see your...

> I think there is a value. What's the vale that you're seeing? :) In particular, what is the value over what I suggested: > Pontoon could simply show the...

I'd prefer to keep everything in a single repo and use labels and projects. We can add a new file in the `spec/` directory. There's already a draft there of...

I created a GitHub project for tracking the design and implementation of semantic comments: https://github.com/projectfluent/fluent/projects/5. @zbraniecki, should we close this issue given that we now have separate issues for each...

For comparison, here's the same file without any special alignment of values: https://gist.github.com/stasm/020a827c37004b44dbd61fd3a23817fe

Thanks, I fixed my gist as well. (The vim macro that I used only removed the extra white space _after_ the `=`.)

To make sure we're on the same page, do you mean _private_ as in _not checked by tools like compare-locales_? #62 mentions a grammar solution to this: `--private-term`. If the...