Untranslatable glossary should be per language

[timothyqiu]

Describe the issue

Marking a glossary term as untranslatable in one language affect all other languages.

One term is untranslatable in one language does not mean it is untranslatable in another. For example,
McDonald's the brand name is almost always untranslatable except in Chinese. This is also true for many tech terms.

Users often set a term to read-only simply because it cannot be translated in their own language. Users of other languages who find that a term they need to translate is marked as read-only will in turn unmark it read-only. It goes back and forth.

I already tried

• I've read and searched the documentation.
• I've searched for similar filed issues in this repository.

Steps to reproduce the behavior

1. Go to some glossary term.
2. Tools > Mark as untranslatable.
3. Check this term in another language.

Expected behavior

Untranslatable is a per language setting, not per glossary term.

[nijel]

Presently, the flags (which define this) are per source string. There is no technical limitation why this could not be done for translations as well, but having two user editable origins for flags would make it confusing (we see that with explanation, which can be set on both source and translation).

[github-actions]

This issue has been put aside. It is currently unclear if it will ever be implemented as it seems to cover too narrow of a use case or doesn't seem to fit into Weblate.

Please try to clarify the use case or consider proposing something more generic to make it useful to more users.

[nijel]

#12779 is related to this (also wants per-translation flags).