New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
i18n: Merge Transifex translations #2942
Conversation
I might have missed
Maybe, we should skip the last "check for new translations"? |
The problem you mention isn't clear to me. But the po files look good, thanks for your work. After merge, weblate will simply update from GitHub and then we continue from there and close our transifex project? |
My script above overwrote any merged PO files with the current PO if they don't have any new translation from Transifex to avoid unnecessary commits. This check is simply see if there are any
we missed it. A simple solution would be to skip this check and commit everything even including those same msgstr with simply different line wrapping. Then, we would see a lot of false changes. I think this latter method should be preferred if Weblate can handle massive line-wrapping-only changes.
At least, that's my plan if everything goes smoothly. |
Let's go for this. If Weblate rejects it we may go for the other way. |
* i18n: Merge Transifex translations * Add transifex_merge_2.sh * msgcat without checking msgstr "new translation" * Resync with Weblate
This PR merges additional translations from Transifex. The merging process was approximately as follows: