Lingoport Wiki:Zip Files For Prep and Import

Localyzer sends files to and from translation via zip files. For some L10n Vendors, such as FTP and local, the zip files are used directly by translation. For other vendors, such as Lingotek and Worldserver, Localyzer will use the zip files to upload files into the L10n Vendors system. By default, when a Localyzer project is prepped, there will be one zip file per locale.

One Zip File per Locale and per Prep Kit Number

The files sent back and forth over FTP have the following characteristics:

• The data files to be translated or returned from translation are sent in a zip file.
• The zip file is named according to this convention: <group-name>.<project-name>.<kit-version>.<locale>.zip. For example, a zip file could be named Queens.Champions.1.fr_fr.zip: The group-name is Queens, the project-name is Champions, the kit version is 1, and the target locale is fr_FR or fr-fr (the locale separator is always an underscore in the zip file name).
• The zip file consists of one top level directory, <group-name>.<project-name>.<kit-version>.<locale>, with all the files to be translated under it.
• There is one zip file per target locale. You may target 10 locales for translation for project "Champions" under group "Queens". You then would have 10 zip files to send to translation.
• A zip file may contain more than one file and more than one file type.
• Each file to be translated has a comment at the top of the file which needs to be kept when returning the file from translation vendor.
• The translated files will be named the same as the original files (so they could be _en.properties even if the content is for French)

One Zip File for all Locales, per Prep Kit Number

If the $JENKINS_HOME/Lingoport_Data/L10nStreamlining/<GROUP>/projects/<PROJECT_NAME>/config_lrm_info.properties is configured with the following property:

   prep.kit.locales.in.one.project=1

And if all the files to be translated are the same (same deltas or same full-files),

then the files sent back and forth over FTP have the following characteristics:

• The data files to be translated are sent in one zip file for all locales.
• The zip file is named according to this convention: <group-name>.<project-name>.<kit-version>.zip. For example, a zip file could be named Queens.Champions.1.zip: The group-name is Queens, the project-name is Champions, and the kit version is 1.
• The zip file consists of one top level directory, <group-name>.<project-name>.<kit-version>, with all the files to be translated under it.
• The zip file contains two files indicating the source locale and the target locales:
• There is one zip file for all target locales. You may target 10 locales for translation for project "Champions" under group "Queens". You then would have 1 zip files to send over FTP, again, if all the files are the same.
• A zip file may contain more than one file and more than one file type.
• Each file to be translated has a comment at the top of the file which needs to be kept when returning the file from translation vendor.
• The translated files will be named the same as the original files (so they could be _en.properties even if the content is for French)
• The translated files will be returned in one zip file per locale, in the form: <group-name>.<project-name>.<kit-version><locale>.zip. For example, a translation for French may be named: Queens.Champions.1.fr.zip.

Two FTP endpoints are necessary: a 'to translation' end point and a 'from translation' endpoint.