As with uploading the content, you can download your translations:
Reports in Transifex show how many words were translated, edited, and reviewed by your translators, along with the Translation Memory leverage used. You can learn more about this feature here.
If you have an in-house native speaker, someone on your client side, a dedicated country manager, or a language specialist (let’s call them all a “client reviewer”) who reviews the translations before they go live, decide how the feedback loop will be implemented:
Does this client reviewer make changes directly in Transifex or not?
How will you be able to make sure the corrections are implemented across all projects if they do? For example, a client reviewer changed how a particular term was translated on your homepage - will it be updated in your app store description and the app itself?
How do you communicate the feedback to your vendor/translators?
You’re done with one round of translations, but more is to come.
When translating an app or website, you'll likely add and change strings constantly, meaning the files with your source content will also change. Instead of uploading a new file and creating a new resource each time a file changes, you can update an existing resource. You can learn more about how Transifex handles updates here.
Whether your new translations are updates to the existing resource file or an entirely new set of resources to translate, think about and discuss with your translation team (vendor/translators/community/freelancers) how they’ll get to know that there is a new batch of translations available for them:
When you want them to translate a specific project/resource, will you email them?
Will you make team announcements within Transifex?
Or do you just set up a cadence for them to go to Transifex and translate whatever is available?
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.