Most of the users have this question on how to avoid English content bleeding in Translations when releasing a product update.
Those are a few tips to avoid it.
Do you have other ideas? Please share it here:)
- The localization process has to be considered in the product’s release workflow. This is the first challenge that has to be broken! Take into consideration that you will need a couple of days to finish and tweak translations before the release.
- Source strings for Translations have to be based on the staging environment before updates go to production.
- A translator can translate ±2k words per day. So keep in mind the update size to plan accordingly, so translators can delivery the translation in a short time frame. For a significant update, you can contract more translators or gives a heads up to the translation agency so they can plan to have enough translators available.
- If you rely on your community to translate your content, make sure to keep them engaged!
Announce when the new content is available for translation, keep them motivated with different recognition programs, and if you still don’t have 100% of your content translated, you can always order translations to complete it. - last thing: You won’t be the only company that sometimes has English bleeding through translations
It happens, and it is a challenge to all companies to avoid it!
@glezos How have the tips helped you improving your translation process last month? Please feel free to share it, and to add anything that might have helped you