I have erased all pre-filled English (en-US) text from the locale files for this add-on.
The reason is that any non-en-US locale file updated with English text, and then uploaded
to BabelZilla, will look like it is 100 % translated if you fill in the new strings (Image 1),
and we (the translators) must search through all text to find the new strings. That is not
so difficult when the locale files are short (like yours are), but e.g. hotkeys, access keys
and abbreviated strings are harder to find.
The only files you have to update before you upload a new version of your add-on is
the en-US locale files. If you do that, BabelZilla will automatically insert the new strings
into the other locales' language files, with the English string text as the translation
source text. That will also make the new strings red and easy to find in the translation
editor interface (Image 2). If you want all locale files to include all strings, even if some
are untranslated, you can download the locale files with the missing/untranslated strings
pre-filled or empty (Image 3).
Well, that's all for me Lakrits
With en-US text pre-filled in a non-en-US locale file.Image 2:
With en-US text not pre-filled in any non-en-US locale file.Image 3:
Downloading locale files with different options for e.g. untranslated strings.