Create Gengo translation jobs using a gettext catalog or JSON files.
- Install
requirements.txt
, requires python 2.7build-virtualenv
. virtualenv/bin/activate
- Create a
configuration.json
- configure against
production
to place orders (configurator gengo-gettext production -l
) - any other env will use gengo's sandbox
- configure against
- Configure projects
cp projects.sample.ini projects.ini
- Run
./gengogettext.py
We use two i18n approaches in our applications: gettext and JSON based translations.
Every project, no matter which i18n approach it uses, can be configured with the following options:
languages
- (string) a list of languages separated by spaceedit_jobs
- (boolean) if truthy, additional "Edit" service will be ordered for each job
Configuration options required by gettext projects:
domains
- (string) a list of gettext domains separated by space<domain-name>
- (string) an absolute directory path where .po file for given domain is stored
Configuration option required by projects with JSON i18n approach:
locale_dir
- (string) an absolute directory path where JSON files with source strings and translations are stored