Acquiring Translated Files
Translated files are first acquired from the translation vendors.
Contents
FTP
For FTP, the files are read from the ftp.in.location.path
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. See Flow and Jobs for more information about FTP Jenkins jobs.
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. See Flow and Jobs for more information about Lingotek Jenkins jobs.
The files retrieved from Lingotek are placed under a staging directory:
Lingoport_Data/LRM/download/lingotek
Worldserver
For Worldserver, the files are read from the worldserver.in.location.path
configuration in config_l10n_vendor.properties
. The files found in the FTP endpoint are moved to
Lingoport_data/LRM/download/worldserver/
They must conform to the zip structure and naming convention.
At that point, the files are ready to be imported. The Jenkins WSDownload
is in charge of that job.See Flow and Jobs for more information about Worldserver Jenkins jobs.
Follow up
In all cases, the files are then moved to this location:
Lingoport_Data/LRM/stating/importkits/lingotek|ftp|worldserver/<GroupName>/<ProjectName>/TRANSLATED_KIT_x_loc
and are ready to be checked and moved to the repository by the import job.