No Consistency Ensurance for Non-translatable Strings

# No Consistency Ensurance for Non-translatable Strings

When I mark a unit as 'terminology', it fills empty values for all languages. Then users can add translations.
Once I decide later to mark it 'untranslatable', the translations are remaining rather than getting removed (which I would rather expect).

Anyway - the holy-grail question that I still wasn't able to figure out is this:

### What's the intended state of translation data for a non-translatable term?

- Should there be no translation strings for other languages?
That is a bit of a problem, because as soon as I delete the last translation, the source string silently disappears..
- Or should there be empty translations for all languages?
If yes, how to achieve that? Should I mark all as 'terminology' first?
Then wait some hours (don't know how many) until the empty strings have been created, and then unmark terminology and mark as 'untranslatable'?
- Or should all all translations exist and be filled with the same string as the source?
I thought that maybe that is the purpose of the " Fill read-only strings with source" add-on, but it doesn't do anything...?

Btw, that's ultimately annoying that you never know what is happening or what might happen and when it might happen. I'm sitting there, desperately trying to achieve something without success, and suddenly, one or more hours later, all the data has changed silently...