Localizing with the Transifex Client
📝Note: Before getting started, check which file format you need your translations in. See the File Formats section for the complete list of supported formats.
To run the Transifex Client from Jenkins, you must set up the Execute shell task.
Alternatively, you can use a plugin like the Managed script plugin.
The source file will be the foundation for setting up the Transifex Client, which lets you send and receive files over Transifex's REST API. To set up your Transifex Client configuration, you first need a project in Transifex, and the Transifex Client installed.
After finishing all the steps above, follow the set of commands below to set up your repository configuration in a file called .tx/config. In this example, we named our project in Transifex mytxproject.
$ git clone http://git.example.com/git/myapp.git
$ cd myapp
$ tx init
$ tx set --auto-local -r mytxproject.defaultpo 'locale/<lang>/LC_MESSAGES/default.po' Please let me know if you have any further questions and I will be happy to answer them.
--source-lang en --type PO --source-file locale/en/LC_MESSAGES/default.po
You should commit the .tx/config file to your repository so the next time you want to push new source content, you can simply use the following commands:
```
$ cd myapp
$ ./manage.py makemessages -l en
$ tx push -s
```
💡Tip: The tx commands should always be executed from the directory in your repository where the .tx/folder is located.
To download translations once they are complete in Transifex, use the following:
$ cd myapp
$ tx pull -t -a
💡Tip
Looking for more help? Get support from our Transifex Community Forum!
Find answers or post to get help from Transifex Support and our Community.