Since GravityView launched in 2014, we have used Transifex to manage translations. Our process has always relied on a single translation resource file, and we’ve had the same flow over time:
- Create an update with new strings
- Upload the translation file to Transifex
- Release the update
- In the next minor release, include any new translations from translators
Transifex recently made it easy to create resource branches using their Command Line Interface (CLI). You can read more about creating branches on their site.
We’re about to release Version 2.0 of GravityView, which includes new strings that I want to have translated before we launch, so I created a branch of the resource.
Here’s how to do it—this assumes you have Transifex installed and configured.
- Switch to the branch of your plugin you want translated
- Update the translation file to have the new strings (we use the excellent
grunt-wp-i18nGrunt package to generate our plugin automatically) - Run
tx --versionand make sure you see0.13.xor higher. If you’re running0.12.x, it won’t work - Push the new resource to Transifex using this format:
tx push -s -b "Your Branch Name"– for example, ours wastx push -s -b "2.0"because our branch name was2.0 - That will now create the resource on Transifex. Go to Transifex and confirm the resource’s name. For our
2.0branch, the resource name was2-0--gravityview - Update your Transifex config file in the plugin’s
.txdirectory’sconfigfile. Change the setting to use the new resource name. For example, instead of[gravityview.gravityview]({name of project}.{name of resource}), it is now[gravityview.2-0--gravityview] - Commit the changes to your repo (see GravityView’s here)
I’m going to be adding a new develop branch as well, so that translators will be able to translate the plugin before it’s released, instead of waiting until later.
The post Translating Multiple Branches of Your Premium Plugin with Transifex appeared first on Katz Web Services.