henry-torproject

This would we really great improvement for formats that do not have metadata for the "fuzzy" or "translated" states. Such as Android String Resources, and Fluent (probably a lot more...

> Each attribute should become a separate `Unit` and some folding when serializing will be needed. @nijel would it be possible to keep the attributes grouped together within the same...

> There is nothing in Weblate that would fit this. How much work would it take to enable this? Would it be a matter of a few tweaks, or is...

> We already have [Variants](https://docs.weblate.org/en/latest/devel/translations.html#variants) to group related strings, maybe it could be used here as well... Thank you. I'll look into that as an option.

@nijel ok, I will see if I can put together a patch to implement this. I'll read your contributing docs and try at the beginning of next year, so I...

@nijel I can handle this along with https://github.com/translate/translate/issues/4649 which I'm currently working on. It would be easy to throw on `FluentFile.serialize`, but it might be better if we can also...

> Maybe supporting some syntax in the field to allow structuring it? Could a double line break `\n\n` work? > The root cause here is merging two scopes of comments....

> Are actually comments in the translated file desired? Keeping them in sync is an additional effort which would have to be performed on each template file update. @nijel I...

> Sorry, I don't know Fluent enough to decide this. @henry-torproject might be interested in discussing this (please let me know if I should stop bugging you with any Fluent...

Another note: the current [Fluent references check](https://docs.weblate.org/en/latest/user/checks.html#fluent-references) assumes that translations should include the same Terms, so weblate will give an error if the translation is missing a Term or contains...