LRM and Lingotek

One out of the box integration for the translation system is with Lingotek. The configuration details are described in this page. This page illustrates some of the interactions between Lingoport and Lingotek.

A Developer Changes Resource Files

As part of the development effort, source code and resource bundles are modified or added.

LRM tracks the changes on the resource bundles and shows the overall view in its dashboard. Resource bundles may have issues, such as duplicate keys or keys with missing values. Critical issues prevent a kit from being created. Developers need to correct critical issues in the files to be translated.

The files which do need to be translated will be sent to Lingotek if no critical issues are detected.

Kits and Lingotek Projects

An LRM Kit contains files to be translated for each target locales. Each Kit is stamped with a version number, starting at 1. LRM remembers which files were sent and what keys are expected back from translation. LRM tracks which kit has been sent, when it was sent, and when it is expected back from translation, for each locale. Many kits for the same project can be sent to translation.

When Translators Finish Work on Lingotek

In the Lingotek workbench, translators use the associated workflow and translate resources. The projects created by LRM are typically named <group_name>.<project_name>_<version_number>, for example Lingoport.WorldWind_5, where Lingoport is the group name (often a company name), WorldWind is the name of the project, and 5 is the version number.

Each project uses Lingotek's callback mechanism to notify the Lingoport automation system some action has taken place. One such callback is sent when a file is 100% complete for the workflow. LRM then downloads the file. When all the files for a locale have been downloaded, LRM checks for the correctness and the completeness of the translated files. If issues are detected, the files for that locale are reset to 0% complete and a notification email is sent. If no issues are detected, the files are pushed back in the repository, a notification email is sent, and the dashboard is updated.