We have some languages that we would like to translate using Machine Translation, while for other languages (more relevant and important for us) we are willing to invest in human translation to guarantee more quality. How can I do that in Transifex and what is the best practices/workflow to accomplish it?
In case you want to combine both, there are 2 different options you can choose to follow:
1- Turn on Auto-machine translation (available to PRO and Enterprise plans). You can run human reviews for the most important languages only.
2- Go to the editor, select the language you want to translate using Machine Translation, select ALL strings and trigger manually “Machine Translation”. For the other languages, you can order translations via Transifex Order Wizard, or inviting to the language teams for those languages your preferred vendor PM and request translations directly.
For any of them, make sure that you purchased the service with Google translate or Microsoft translator, and set the API key to enable Machine translation.
Let me know if you have further questions
I recommend that you do not publish machine translation without at least some proofreading. Even for languages where the results are generally good, you are bound to have some embarrassing grammar errors in your translation. For some language pairs, quality is so bad that it’s not even worth presenting it as a pre-translation to your localizers.
Machine translation is a supportive tool, it is not ready for creating production-quality copy.
@gunchleoc, Thanks for your comment!
Although we agree that this solution still might affect the translation quality, we’ve seen that the industry has gone more to this direction recently, and we are also looking for solutions where people can have better quality in terms of MT. We are working now on an integration with a QA tool that might help with a more robust review and fixes, for example, slight_smile:
Translators and reviewers will still have a great role here, but a more efficient way to work with MT and fix errors in an easier and quicker manner!
Yes, as I said, having it as a supportive tool is perfectly fine for those language pairs where the translation quality is sufficient that it makes the translators’ life easier.
The problem is that there’s a common misconception out there that you can just use MT and slap it on your publication without post-editing. We are seeing this sort of sub-standard work crop up on everything from official signage to book publication.
OP sounded like they might want to publish for some languages without post-editing. These will probably be some lesser-used languages where MT quality will be pretty low. If you want to know more, check out the following articles: