Hi,
I noticed that my own new translations in arabic are cleared and emptied. This happened not just once. I thought I was having Alzheimer, nope, someone is not pulling translation right from Git to Weblate.
Make test, go to arabic on Weblate translate a test string, remember that string and then you will notice that in the next push/pull via/from Git, your translation will be null.
Ok, we lost the Backend now :( https://weblate.joinmastodon.org/projects/mastodon/backend/ar/
Hi.
Maybe, have you added the same translation as "user_count_after" to "about / user_count_after / one" ?
"user_count_after": https://github.com/tootsuite/mastodon/blob/master/config/locales/ar.yml#L36 )
"about / user_count_after / one": https://weblate.joinmastodon.org/translate/mastodon/backend/ar/?checksum=12b00029438dda8e#history
This happened twice even in a Japanese translation as far as I know, too.
Perhaps it seems that Weblate gets an error if you add the same translation after splitting what was not translated in singular or plural form.
All my changes on Weblate. I have a role of a translator on Weblate. Cannot delete all the strings.
My history : https://weblate.joinmastodon.org/changes/?page=1&user=ButterflyOfFire
@nightpool It is occurring in Weblate. I can only do git merge, so I do not know the details.
Have we reset weblate to master since #8420?
I do not know because I am not an administrator of Weblate.
@Gargron Dou you know?
I'll get this fixed and/or ping gargron to do so.
On Sun, Aug 26, 2018, 1:39 PM ButterflyOfFire notifications@github.com
wrote:
Check : 5538ad9#r30292166
https://github.com/tootsuite/mastodon/commit/5538ad99db455580ecc0997140b0eb5b544e4608#r30292166â
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/tootsuite/mastodon/issues/8451#issuecomment-416055678,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAORV0IIaBgNsjMPVnk8eo_Bq2KGrwAPks5uUt1ngaJpZM4WMqpd
.
thanks for flagging the issue!
On Sun, Aug 26, 2018, 1:45 PM Evan G eg1290@gmail.com wrote:
I'll get this fixed and/or ping gargron to do so.
On Sun, Aug 26, 2018, 1:39 PM ButterflyOfFire notifications@github.com
wrote:Check : 5538ad9#r30292166
https://github.com/tootsuite/mastodon/commit/5538ad99db455580ecc0997140b0eb5b544e4608#r30292166â
You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub
https://github.com/tootsuite/mastodon/issues/8451#issuecomment-416055678,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAORV0IIaBgNsjMPVnk8eo_Bq2KGrwAPks5uUt1ngaJpZM4WMqpd
.
The same here, I have to redo the latest translations on the Backend :O
It's not the first time.
Ăa comment Ă ĂȘtre agaçant quand mĂȘme =/
Another one ? https://github.com/tootsuite/mastodon/pull/8483
I noticed two different sets of issues on weblate:
The first one is that sometimes weblate completely removes a file. It used to happen very often with simple_form in some languages.
The second one is that if we merge differences from weblate into the project, weblate needs to be reset because of the indentation differences. If between the creation of the PR and merge/reset of weblate there's new translations, those translations are reset too.
Are the forked repos synched and updated with Master before you merge ?
It's annoying that none verifies the number of deleted strings.
We translators/localizers are eating the sh** on Weblate :))
The process is simple :
Translate only on Weblate.
My flow to merging weblate translations usually is:
Checkout latest master, start new branch, checkout weblate master, merge weblate master into translation branch, solve conflicts, normalize translations, revert removed files by weblate, normalize translations again
Weblate reformats translation files, adding two extra spaces for indentation in the json files, and breaks some lines in the yml ones.
This causes conflicts when merging back files coming from the project (and makes merging back from weblate harder)
I will try getting some time to look into this again: http://widerin.net/blog/weblate-i18next-json-parser/
The author suggests using a script in the pre-commit script hook that weblate provides to avoid these issues. If we could use a docker image with modifications so that we can use that script and match the codebase indent, I think it would reduce a lot the problems we have with weblate.

Did this issue resolve by upgrading Weblate?
We need to wait until we recieve new strings to translate to confirm.
cc @Quenty31 have you lost a lot of translation in Occitan?
It seems somebody wants to close the issue quickly.
Non, pas ce coup-ci !
Si je comprends bien, ça n'arrivera plus ce désagrément ?
Merci :)
Thank you !