Stanisław Małolepszy

Here's another example from Firefox ([source](https://hg.mozilla.org/l10n/gecko-strings/file/6ed6a4050107/browser/chrome/browser/browser.properties#l769)). Thanks to @flodolo for helping me find it. ```properties # %S is the website origin (e.g. www.mozilla.org) getUserMedia.sharingMenuCamera = %S (camera) getUserMedia.sharingMenuMicrophone = %S...

I ended up opening an issue in this repo, since it's more of a Fluent Design question. See #80.

I've moved this to the spec repo, as we'd need to make a change to the syntax in order to make this work.

I'm having seconds thoughts on this one. What can top-level whitespace do that calculating spans between entries (in tooling parsers) can't?

As per the OTP triage, I moved this out of the Syntax 0.7 scope into `FUTURE`. There aren't strong drivers for this feature right now. At Mozilla, `compare-locales` and `cross-channel`...

Thanks for sharing your thoughts, @hkasemir. I understand the internal conflict you're describing. Whenever I write JS and then go back to Fluent, I don't find `:` too bad. But...

Yes, the simplification of the syntax is worth the extra effort. Especially with #176, requiring the `$` sigil in argument names will result in consistency in syntax between the caller...

Moving this out of the Syntax 0.8 milestone, which shipped in mid-December. I'm keeping this issue open for now to make it easier to find in case it's relevant to...

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: @meta masculine brand-name...

We could also introduce versioning for messages . This would allow making small changes to the original copy without having to change the identifier. The default and implicit revision would...