-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
The translation workflow isn't optimal #75
Comments
There's something else bothering me: why don't we have easy i18n of simple strings like button labels? Those translations have been done lots of times already in other projects, we shouldn't have to spend time on them. |
A translator working while I was reviewing and merging translations has led to a git conflict. :-/ |
The worst part: the conflict was only in those fucking useless PO file headers. |
Regarding the merge conflict issue, maybe this kind of setup could offer a solution ? |
It looks similar to what we do now, except we don't put a lock. We also don't use a script to merge PO headers (it's rare enough to be handled manually). We can't automatically push new translations to master because we need to review them first (we use Git's builtin tools to do that since Weblate doesn't give us a way to do it). |
One thing that could be improved is adding an explanation. That could be of help in strings like this, where some translators translated the article title, which in my opinion is not the proper approach. The explanation could here say "the article is only in English. Do not translate the title. If you want, add the language of the linked article as an clarification". |
Issues with Weblate:
its locking can be annoying (Improve auto locking WeblateOrg/weblate#245).po
files to avoid Git noiseThe text was updated successfully, but these errors were encountered: