translation file uploads do not clear "needs editing" strings if upload has them emptied about weblate HOT 5 OPEN

Yes, you need more permission for that (because it can remove strings as well).

from weblate.

The upload processes only translated strings. What you can do is to use Replace existing translation file instead, that doesn't go to the string level.

from weblate.

What you can do is to use Replace existing translation file instead

There is no "replace" option in the upload page. at least not for us contributor translators.

from weblate.

@nijel, sorry for slow responses, health issues in the family.

this permission requirement takes us back to square one; that for us translators, these options triplet should replace/clear translated-but-needs-editing strings without admin level permissions.

For these option triplet, you may add an extra checkbox with a big warning that if process continues, for example, it may damage the source, and ask the user to double or triple check what they did.

I feel the urge to repeat my original attention in a little bit different way:

When a project's maintainers/admin make changes on translations through scripting, usually po files, they copy old translations into new strings with zero history, and remove old ones with their history.

Somehow on the way, a lot of these translation matches 0% to the source, and thus the truth level drops sharp on the total.

There are no other actively participating translator other than me in the last 6 months, and I was very disfocused aboutt he project. so these needs-editing translations were accumulated over 2000 strings. This loads a huge strain on my nerves as my best was 100-200 per day, and i do not have regular access recently. clearing them there and then is the best way to ease the strain.

another stress is that since this is a po type project, they will use whatever translated string is present without ever proof reading (which is what i do basically) and thus i want to clear all those strings. when no translation is present, they use source strings instead, and it is best to have no translation ever instead of having wrong translations.

you may say why not to ask maintainers for more project permission. but as you may understand, open source projects may not see them around for long, so even if i get access, then the next person i trust the flag may not get such permission in time.

Anyways, I really appreciate you taking your time and bear with us. Thank you very much. If you got more time, I would like to hear more from you about how else could we get a solution. For the moment I am a bit burnt out, so until next time.

from weblate.

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

from weblate.