Difference between revisions of "Acquiring Translated Files"
(→Lingotek) |
|||
Line 17: | Line 17: | ||
Lingoport_Data/LRM/download/lingotek |
Lingoport_Data/LRM/download/lingotek |
||
+ | |||
+ | = Follow up= |
||
+ | In both cases, the files are then moved to this location: |
||
+ | |||
+ | Lingoport_Data/LRM/stating/importkits/<lingotek|ftp>/<GroupName>/<ProjectName>/TRANSLATED_KIT_x_loc |
||
+ | |||
+ | and are ready to be checked and moved to the repository by the import job. |
Revision as of 22:01, 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
Follow up
In both cases, the files are then moved to this location:
Lingoport_Data/LRM/stating/importkits/<lingotek|ftp>/<GroupName>/<ProjectName>/TRANSLATED_KIT_x_loc
and are ready to be checked and moved to the repository by the import job.