Those 18 incomplete strings are all empty values. But I’m not able to set their translation as “completed”.
I’m a bit proud that with lots of work I had fullfilled german translations to 100 %. It’s a matter of accessibility that I care a lot. So I subscribed to all regarding german translations to fix changes as fast as possible. Now new cases are “polluted” with a lot of noise.
Is there any possibility to set those empty values to “completed” translations? Why do they have to exist if they are empty? Why didn’t they affect my subscriptions before (if they existed before)?
As @surli commented two of those 18 empty values maybe you know some answers to my questions?
Regards, Simpel
I will try to see what I can do, but right now I have no idea how to do that.
So I know some of them are there for historical reasons (in particular in XWiki Core Resources), but I’m indeed not sure why we keep adding some, for example I find image.style.administration.liveData.emptyvalue a bit weird, but I guess there’s a technical reason behind it, maybe @mleduc or @mflorea could explain.
I have no idea where to set the keys for empty strings to read-only. But I guess that has to be done at Weblate and will be only possible for accounts with special privileges? I see a “Flags” section in the right panel “String information” if something is set there. (As with the empty values in english.)
These strings are missing the text, for instance, in the Ukrainian section, if I export the component as a ZIP file and open ApplicationResources_uk.properties, I can find this line ### Missing: xe.userdirectory.emptyvalue=
I assume what can be done is to mark these values as a comment not remove(delete) due to the fact probably it’s old functionality or option which currently doesn’t exist.