Overwritten Weblate component translations (language specific)

[salvador-pena]

AFAIU english man pages for components are extracted from src/components/*.comp and eventually processed to original source strings for Weblate.

I have noticed that some of my (spanish) translations are overwritten;
so it looks like there is something in between that besides to original strings updating, updates spanish translations too.

I have two cases:

1. Characters added. For example, in this string, the "transformation":

   • adds index entry triple rounded brackets, which are inconsistent with original source string.
   • adds a period at the end of string, which fires a 'Mismatched full stop' failing check in Weblate.

   Apparently, this happens for french translations too.

2. Overwritten string. For example in this string , where my translation is overwritten, from where?.

[smoe]

Are your translations still in weblate? If so, then I understand these are not lost. Maybe there are two very similar English entries (with and without a period at the end?).

Weblate provides .po files. And weblate should be the source of the perfect translation. The .po files in the source tree are newly generated when the documentation changes, which then triggers the .pot file and also adjusts the .po files in the archive. Only the updated .pot file should then be committed to the archive and weblate will update the .po files from there. Unless someone borked and also updated the .po files in the archive to then force-feed them back to weblate, what you described should not happen.

To avoid any larger confusions, it is good practive to lock the editing in weblate whenever an update of the .pot file is prepared for weblate to see. @hansu? @petterreinholdtsen?

[salvador-pena]

Fortunately, those are simple translations that can be reverted or re-applied, basically are component/parameter descriptions, but I had to correct more than 600 strings. I thought they were new strings, but nearly the end I noticed that I was reworking.

Please take a look into the sample strings history, so you can see what (and when) is happening and maybe point out where are those rewrites coming from.