How can I use Transifex in order to automate my localization workflow
Transifex is a translations management platform that focuses on Continuous Localization. The basic idea behind this is that, as soon as new strings are introduced in your application, the localization process starts. When those strings are translated and reviewed, they are ready for you to deploy along with the code that introduced them.
You can use either the Transifex client or the API (in case you need more control) to instruct your CI tool to send new strings to Transifex whenever there is a new commit for translation. When all of your strings are translated, Transifex will ping you back (using a webhook) to let you know that you are ready to download the translations and deploy.
Please note that you can configure a webhook for the translations of your Transifex project so you can get notified, whenever the translation for a file is completed or fully reviewed. You will just need a web server to listen for the webhook calls, and some kind of application to react on those. So the webhook will be triggered when the translation or the review of a specific language reaches 100%.
For instance, if you use Github as a version control system, then you can sync your translations in Transifex using the Github integration we have built. This solution works like this:
– For every change to a source file in Github, the server will update the content in Transifex.
– For every change to a translation in Transifex, the server will create a commit and push it to Github with the new translations.
So, by combining Transifex’s and Github’s webhooks ensures that any change that makes a file completely translated in Transifex will trigger the server to push a new commit to Github with the updated translations files, and any change in Github to the source files will trigger the server to update the source content in Transifex. As you understand, that way you will have the most out of the possible automation on the file updating.