Continuous Localization
One of the guiding principles of Zing is enabling continuous localization.
Provided projects are already setup in the Zing server, the general idea for such a workflow would be to:
- Pull translations from Zing to the filesystem.
- Run your localization toolchain. This must take care of:
- Merging the latest translations with the latest localizable resource files from your development repositories.
- Placing the resulting files in the translation directory.
- Push the updated translations to the Zing database.
The first and last steps are covered by Zing. The intermediate step is up to your particular process. Nonetheless, localization is hard, so are its processes, that's why we suggest using Serge for this matter.
Continuous Localization with Serge
Serge is a command-line tool that helps us remove the burden of having to deal with multiple localization file formats, version control systems, exotic directory layouts and locale codes, as well as other minor details that affect global localization projects. Serge is extensible too, so that if some of the built-in features or behaviors do not suffice, you can adapt it to your own needs.
Integration
In order to integrate the Serge localization workflow with our Zing translation server, we first need to install Serge in the same server as Zing.
After that, we will need to configure a Serge
job and specify we want to use the
pootle plugin. Along with that, we need to define the path to the zing
executable in our server, as well as the project code we are using for the
project described by the job we are configuring.
To learn more about how to configure Serge, please refer to the Serge + Pootle integration guide which is part of the Serge documentation.