Difference between revisions of "Acquiring Translated Files"
(Created page with "Translated files are first acquired from the translation vendors. ==FTP== For FTP, the files are read from the <code>in</code> configuration in <code>config_l10n_vendor.prop...") |
(→Lingotek) |
||
| Line 13: | Line 13: | ||
In case all the files were not correctly retrieved from Lingotek (network problem for instance), <code>CheckCallbacks</code> will sweep for files to be retrieved later on. |
In case all the files were not correctly retrieved from Lingotek (network problem for instance), <code>CheckCallbacks</code> will sweep for files to be retrieved later on. |
||
| + | |||
| + | The files retrieved from Lingotek are placed under a staging directory: |
||
| + | |||
| + | Lingoport_Data/LRM/download/lingotek |
||
Revision as of 21:57, 27 April 2015
Translated files are first acquired from the translation vendors.
FTP
For FTP, the files are read from the in configuration in config_l10n_vendor.properties. The files found in the FTP endpoint are moved to
Lingoport_data/LRM/download/ftp/
They must conform to the zip structure and naming convention.
At that point, the files are ready to be imported. The Jenkins FTPDownload is in charge of that job.
Lingotek
For Lingotek, a callback from the Lingotek workbench to Jenkins LingotekCallback lets the system know some files are ready for download. The files are retrieved from Lingotek.
In case all the files were not correctly retrieved from Lingotek (network problem for instance), CheckCallbacks will sweep for files to be retrieved later on.
The files retrieved from Lingotek are placed under a staging directory:
Lingoport_Data/LRM/download/lingotek
