Table of Contents
Localizing with the Transifex Client
Before getting started, note there are a number of different JSON formats for localized strings. Transifex currently supports the following formats:
In order to run the Transifex Client from grunt, you will need to set up the grunt-exec package.
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. In order 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' \
--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 |
To download translations once they are complete in Transifex, use:
$ cd myapp
$ tx pull -t -a
Community integrations
Grunt Transifex Resjson via GitHub or Npm Package These tasks have been developed to interact with the Transifex API in a Windows Store JavaScript app project where RESJSON resource files are used for handling different translations.
Grunt Transifex via GitHub Provides a Grunt task that downloads translation strings from Transifex into your project using the Transifex API.