Task #3581
closed
It’s very important to ensure Weblate is set to push to its Git buffer-repository on a daily basis, for backup.
Added by Adolfo Jayme Barrientos about 2 years ago.
Updated almost 2 years ago.
Description
I’ll explain.
When too much time happens between Weblate (i.e. translators) updates, and Cloph in the meantime updates the templates for new strings, if translators have worked with strings that are near an updated string, a merge-conflict process will mean that the translation work is lost because it was never pushed anywhere.
It has happened to me that I have translated strings in Catalan, Asturian and Spanish and a template update has overwritten the changes, SILENTLY. And it’s annoying to find out, years later. See, for an example, the history of this string: https://translations.documentfoundation.org/translate/libo_help-master/textshared01/es/?checksum=8977ee3a3749f214#history I’ve had to make the same change to it THREE F***ING TIMES! Now I’m afraid to make fixes to the original strings because it may cause the work to be lost when the POTs are updated! And since I work on three languages, it TRIPLICATES my efforts. What do I have to do, circumvent Weblate entirely, as Martin Srebotnjak does?
- Assignee set to Christian Lohmaier
You're jumping to conclusions. The commits to the repo/the update against templates has nothing to do with the string requiring multiple edits.
I always submit/push pending commit from weblate to the repo before running the update, and weblate (or rather git) will loudly complain and lock the repo in case of merge conflicts.
It also is not the update against the templates itself that would revert the string, you can verify both in the actual git repository.
The string with ID Ppsst was added with the initial import, and the last time the string was touched in the repository was on August 19 2019 - and that was when the key-IDs were added to the po files. That string had the "Espacio" translation since the initial import three years ago.
In other words: The files have been flushed/committed many, many times in between, and most certainly always before an update against new templates.
- Status changed from New to Resolved
Did look more closly into the history, and the problem is not the daily sync, that wouldn't have prevented the problem, but it is a problem of translating at the same time while an update is done.
I consider this also solved, since for the last updates I already did switch to locking the projects when there is an update. I did it mainly to prevent merge conflicts, but it will also prevent the overlapping edit events.
(Besides there was and still is the max-age of 24h for changes configured in weblate, and weblate is pushing changes multiple times a day to cover the different components/projects, just look at https://github.com/LibreOffice/translations-weblate/commits/master )
- Status changed from Resolved to Closed
Please re-open if problem happens again
Update: it’s now happened, but the fact that the interval is not regular is kinda nerve-inducing, given the precedent.
Also available in: Atom
PDF