Difference between revisions of "Prep Kits"

From Lingoport Wiki
Jump to: navigation, search
(→‎How do I prep a kit?)
(→‎Is there a way to create a prep kit zip file that contains files for all the locales rather than just 1 zip file per locale?)
 
(62 intermediate revisions by 2 users not shown)
Line 1: Line 1:
  +
=What is a Baseline?=
  +
  +
A baseline is done when a Localyzer project is created to track the information in the base files and the translated files. If any of those keys and values are modified before a Prep Kit is created, the changes will be caught. For more information see [[Baseline |Baseline]].
  +
 
=What is a Prep Kit? =
  
=What is a Prep Kit? =
   
−
A Prep Kit is what we call the set of resource files that are gathered by LRM, set out for translation, and then integrated back into the source code tree once translated. LRM sets and tracks versions of a Kit so that, as your developers add strings to the base resource files, you can prepare and send out the Kit multiple times. There are a variety of checks that LRM makes on the base resource files to ensure that they are correct, as well as tracking the progress and correctness of the translated resource files.
 +
A Prep Kit is what we call the set of resource files that are gathered by Localyzer, sent out for translation, and then integrated back into the source code tree once translated. Localyzer sets and tracks versions of a Kit so that, as your developers add strings to the base resource files, you can prepare and send out the kit multiple times. There are a variety of checks that Localyzer makes on the base resource files to ensure that they are correct, as well as tracking the progress and correctness of the translated resource files.
   
−
Note: If your project contains translated files, then when prepping your first kit, LRM will not be able to detect if a text change has occurred within a resource string. It will, however, be able to detect added keys or missed translations.
 +
Note: If your project contains translated files, then when prepping your first kit, Localyzer will not be able to detect if a text change has occurred within a resource string. It will, however, be able to detect added keys or missed translations.
   
−
= How do I prep a kit?=
 +
= How do I prep a kit and receive it back from translation?=
   
 
There is a Jenkins job on-boarded. The Lingoport Dashboard is populated and the L10n Vendor has been configured. A Prep Kit can be sent. At this point, the Lingoport Dashboard for the project looks something like:
  
There is a Jenkins job on-boarded. The Lingoport Dashboard is populated and the L10n Vendor has been configured. A Prep Kit can be sent. At this point, the Lingoport Dashboard for the project looks something like:
   
−
[[File:BeforePrepKit.jpg |700px]]
 +
[[File:DashboardPrepKit.png |700px]]
   
   
 
* '''Last Sent Kit''' is '''0''' since no prep kits have been sent yet.
 
* '''Last Sent Kit''' is '''0''' since no prep kits have been sent yet.
 
* All the Locales are at '''0 Percent Complete''' since we only have a base resource file.
  
* All the Locales are at '''0 Percent Complete''' since we only have a base resource file.
−
* Under '''Next Prep Kit Content''', it shows that we are sending '''1 file''' that has '''62 keys''' and '''82 words'''.
+
* Under '''Next Send Translation Content''', it shows that we are sending '''1 file''' that has '''65 keys''' and '''85 words'''.
−
* Since we have not sent anything yet, there is nothing in '''Prep Kit Due Dates'''
 +
* Since we have not sent anything yet, there is nothing in '''Translation Package Due Dates'''
   
 
To send a prep kit, either select the '''Prep Kit''' button on the Dashboard (this runs the '''DashboardPrepKit''' job in Jenkins) or run the PrepKit job in Jenkins called '''<group>.<project>-PrepKit'''.
  
To send a prep kit, either select the '''Prep Kit''' button on the Dashboard (this runs the '''DashboardPrepKit''' job in Jenkins) or run the PrepKit job in Jenkins called '''<group>.<project>-PrepKit'''.
  +
  +
When everything is successful, the Dashboard should look like:
  +
  +
[[File:AfterPrepKit2.png |700px]]
  +
  +
* '''Last Sent Kit''' is '''1''' since we sent Prep Kit #1 to be translated.
  +
* All the Locales are at still at '''0 Percent Complete''' since we have not gotten the translations back, but there is a note: '''There are outstanding prep kits for this locale'''
  +
* Under '''Next Send Translation Content''', there is nothing because everything at this point has been sent.
  +
* '''Translation Package Due Dates''' shows 1 file for each locale was sent and when it is due back.
  +
  +
For the persons that were designated in the Jenkins job to get notifications of prep kits, an email will be sent. When the prep kit is successfully sent out, the email will be an Upload Success. There will be one email for each locale.
  +
  +
[[File:UploadSuccess.jpg |500px]]
  +
  +
This shows just the German (de_DE) locale.
  +
* Note that it shows '''CET.NOAA.1.de_DE''' that is '''<group-name>.<project-name>.<prep kit number>.<locale>'''
  +
* It shows where to find the files on the local machine that were sent to translation.
  +
* It lists the files sent to be translated to German. In this example, there is only '''1 file'''.
  +
  +
  +
When the files have been translated, they are put in a special directory and Jenkins routinely checks for files to be downloaded. The files are downloaded and and then the translated files are pushed to the repository. To do this manually, invoke the '''FTPDownload''' Jenkins job if using FTP. Once the files have been downloaded, the Dashboard will update to reflect the changes.
  +
  +
[[File:AfterImport2.png |700px]]
  +
  +
* '''Next Send Translation Content''' and '''Translation Package Due Dates''' are empty. All files have been translated.
  +
* Each '''Locale''' shows '''100% Complete''' with 0 Files, Keys or Words Remaining.
  +
  +
The code repository will have the translated files.
  +
  +
=What is done when a prep kit is generated? =
  +
  +
After a Localyzer project is created and correctly identifies the base and target resource files, the project needs to be baselined. When the project is baselined, the base resource files are in the system. If any changes happen to them afterward, this will be picked up in the prep kit. This is done in the Jenkins Nightly job or it can be done on the command line.
  +
  +
> java -jar /var/lib/jenkins/lingoport/lrm-server-<version>/lrm-cli.jar --create-baseline --project-name <project-name> -- group-name <group-name>
  +
  +
Localyzer is able to detect modified text as well as missing keys and missing files.
  +
  +
For example let's say you have a project with:
  +
* 3 locales: en_US (base locale), fr_FR and de_DE.
  +
* 2 base files
  +
** file1_en_US.properties (100 keys)
  +
** file2_en_US.properties
  +
* 1 fr_FR file with a missing key
  +
** file1_fr_FR.properties (99 keys)
  +
* 1 de_DE with 2 missing keys
  +
** file1_de_DE.properties (98 keys)
  +
  +
  +
'''Create a prep kit''' for the new Localyzer project by selecting the '''Prep Kit''' button on the Lingoport Dashboard or by running the Jenkins '''<project-name>-PrepKit''' job.
  +
  +
<pre>
  +
> java -jar lrm-cli.jar -pk -pn ProjectName -gn GroupName
  +
The following reports were generated:
  +
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/BaseFileSearch_de_de.xml
  +
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/BaseFileSearch_fr_fr.xml
  +
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/FilesToPrep.xml
  +
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/ProjectName_1_de_de.xml
  +
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/ProjectName_1_fr_fr.xml
  +
Process completed successfully.
  +
</pre>
  +
  +
The base locale resource files are extracted and placed in the appropriate localized prep kit folders. See the '''de_de''' and '''fr_fr''' folders in <code>/var/lib/jenkins/Lingoport_Data/LRM/<GroupName>/prep_kit/<ProjectName>/PREP_KIT_<num></code>.
  +
<pre>
  +
> ls /var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/
  +
BaseFileSearch_de_de.xml FilesToPrep.xml ProjectName_1_fr_fr.xml
  +
BaseFileSearch_fr_fr.xml fr_fr/
  +
de_de/ ProjectName_1_de_de.xml
  +
</pre>
  +
  +
In the '''fr_fr''' folder, are all the files to be translated:
  +
<pre>
  +
> ls /var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/fr_fr/
  +
file1_en_US.properties
  +
file2_en_US.properties
  +
</pre>
  +
  +
For missing files, the entire file will be sent.
  +
For missing keys (or modified text) only the changed keys will be sent.
  +
  +
By default, when prep kits are sent, a zip file is created for each locale with the name: '''<code><GroupName>.<ProjectName>.<prep kit number>.<locale>.zip</code>'''. For example, for Acme project Weather, prep kit 5 and locale 'FR_fr': '''<code>Acme.Weather.5.fr_fr.zip</code>'''. If there is a need to send files for '''all''' the locales in 1 zip file, then the <code>prep.kit.locales.in.one.project</code> flag needs to be changed in configuration file '''<code>config_lrm_info.properties</code>''' which resides in the '''<code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config</code>''' folder. See [[Zip_Files_For_Prep_and_Import | Prep/Import Zip Files]] for more information.
  +
  +
=How can I prevent a file or folder from being included in the prep kit?=
  +
  +
You will need to alter your [[Terms_and_Definitions |project definition file]] and exclude the file/folder from the project.
  +
  +
In Jenkins, select the project you are working on and select '''Configure''' from the menu.
  +
  +
[[File:AddExclude.jpg |600px]]
  +
  +
Scroll down to the Directories section and select the '''Add Exclude Directory File''' button which will create a new entry. Add the directory or file you want to exclude. '''Save''' your project. In this example, we added the <code>**/test/**</code> directory.
  +
  +
When the project is run, the Jenkins output shows:
  +
  +
Creating Project Definition File: /var/lib/jenkins/Lingoport_Data/LRM/<group-name>/reports/<project-name>/ProjectDefinition.xml
  +
  +
If you open the Project Definition File, you should see your new addition(<code><exclude-dir-file>**/test/**</exclude-dir-file></code>) to the excludes:
  +
  +
<excludes>
  +
<exclude-dir-file>**\*_eo.properties</exclude-dir-file>
  +
<exclude-dir-file>**/LRMScans/**</exclude-dir-file>
  +
<exclude-dir-file>**/GlobalyzerScans/**</exclude-dir-file>
  +
<exclude-dir-file>**/sonar-project.properties</exclude-dir-file>
  +
<exclude-dir-file>**/test/**</exclude-dir-file>
  +
</excludes>
  +
  +
= Modified text does not seem to be recognized as a change in my base resource file. What is wrong? =
  +
  +
Modified text can only be detected if there has been a baseline created for the project. In this way, Localyzer can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line. See [[LRM_Commands_Reference#Create_a_project_baseline| Create Project Baseline]] for more information.
  +
  +
=When I prep a kit, what files are created?=
  +
  +
When you prep a kit from either Jenkins or the Lingoport Dashboard and it is successful, the resulting files will be located in :
  +
  +
/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/projects/<project-name>/prepkits/PREP_KIT_<number>
  +
  +
And may contain the following files and directories.
  +
  +
'''<locales>'''
  +
  +
For each locale that needs to be translated, there is a directory named for that locale resource files for that locale. The file may be the whole resource file if no translations exist and will have <code>FULL-FILE</code> in the comment at the top of the file. If the file is just for changes that have occurred since the last translation, it will have just those changes in the file and <code>CHANGES-ONLY</code> in the comment header line.
  +
  +
'''<code>FilesToPrep.xml</code>'''
  +
  +
This file shows what is displayed much more nicely in the Dashboard.
  +
  +
<pre>
  +
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  +
<LRMFilesToPrepTag companyName="Acme" default-locale="en_US" inContextQALicenseEn
  +
dDate="2020-01-15" licenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-v
  +
ersion="5.0.28" projectID="5" projectName="Weather" timezone="GMT" topLevelD
  +
irectory="/var/lib/jenkins/jobs/Acme.Weather/workspace/WeatherWidget-master/resources">
  +
<locales>
  +
<prep-info locale="fr_CA" localeDisplayName="French (Canada)" nbFilesToTrans
  +
late="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
  +
<prep-info locale="de_DE" localeDisplayName="German (Germany)" nbFilesToTran
  +
slate="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
  +
<prep-info locale="fr_FR" localeDisplayName="French (France)" nbFilesToTrans
  +
late="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
  +
<prep-info locale="es_MX" localeDisplayName="Spanish (Mexico)" nbFilesToTran
  +
slate="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
  +
</locales>
  +
<files>
  +
<file-path file="/Weather_en_US.properties"/>
  +
</files>
  +
</LRMFilesToPrepTag>
  +
</pre>
  +
  +
*<code>companyName="Acme"</code>
  +
*<code>default-locale="en_US"</code>
  +
*<code>projectName="Weather"</code>
  +
*<code>topLevelDirectory="/var/lib/jenkins/jobs/Acme.Weather/workspace/WeatherWidget-master/resources"</code>
  +
*For each locale to translate:
  +
**<code>nbFilesToTranslate="1"</code> - number of Files to Translate
  +
**<code>nbKeysToTranslate="62"</code> - number of Keys to Translate
  +
**<code>nbWordsToTranslate="82"</code> - number of Words to Translate
  +
*<code><files></code> - a list of files to translate. The files are shown in the relative path from the topLevelDirectory
  +
  +
'''<code>BaseFileSearch_<locale>.xml</code>'''
  +
  +
This report shows the specifics for the <locale> given. Especially for the list of files.
  +
  +
<pre>
  +
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  +
<LRMBaseFileSearchResults companyName="Acme" inContextQALicenseEndDate="2020-01-1
  +
5" licenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-version="5.0.28"
  +
projectID="5" projectName="Weather" timezone="GMT" topLevelDirectory="/var/l
  +
ib/jenkins/jobs/Acme.Weather/workspace/NOAAWeatherWidget-master/resources">
  +
<locale>de_DE</locale>
  +
<nbKeysToTranslate>62</nbKeysToTranslate>
  +
<nbWordsToTranslate>82</nbWordsToTranslate>
  +
<nbFilesToTranslate>1</nbFilesToTranslate>
  +
<is-prepkit-override>0</is-prepkit-override>
  +
<results>
  +
<result file="/Weather_en_US.properties"/>
  +
</results>
  +
</LRMBaseFileSearchResults>
  +
</pre>
  +
  +
'''<code>IncompletePrepKit.xml</code>'''
  +
  +
This report contains the information used in Dashboard Prep Kit Due dates.
  +
  +
<pre>
  +
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  +
<LRMIncompletePrepKit companyName="Acme" inContextQALicenseEndDate="2020-01-15" l
  +
icenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-version="5.0.28" proj
  +
ectID="5" projectName="Weather" timezone="GMT" topLevelDirectory="/var/lib/j
  +
enkins/jobs/Acme.Weather/workspace/WeatherWidget-master/resources">
  +
<prepkits>
  +
<prepkit completiondate="" sentdate="2019-06-24 21:54:48" versionnum="1">
  +
<results>
  +
<result completiondate="" initialduedate="2019-06-27 21:54:49" locale="f
  +
r_FR" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
  +
<result completiondate="" initialduedate="2019-06-27 21:54:49" locale="fr_CA" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
  +
<result completiondate="" initialduedate="2019-06-27 21:54:49" locale="es_MX" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
  +
<result completiondate="" initialduedate="2019-06-27 21:54:49" locale="de_DE" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
  +
</results>
  +
</prepkit>
  +
</prepkits>
  +
<summaries>
  +
<summary completiondate="" completiondateversionnum="0" locale="fr_CA" local
  +
eDisplayName="French (Canada)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
  +
<summary completiondate="" completiondateversionnum="0" locale="de_DE" local
  +
eDisplayName="German (Germany)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
  +
<summary completiondate="" completiondateversionnum="0" locale="es_MX" local
  +
eDisplayName="Spanish (Mexico)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
  +
<summary completiondate="" completiondateversionnum="0" locale="fr_FR" local
  +
eDisplayName="French (France)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
  +
</summaries>
  +
</LRMIncompletePrepKit>
  +
</pre>
  +
  +
'''<code>OutstandingPrepFiles_<locale>.xml</code>'''
  +
  +
If you send a prep kit and there is already a prep kit that hasn't returned, you will get this file. In the example below, this file was in the <code>PREP_KIT_3</code> folder. Prep kit #1 had been returned, but #2 had not and then prep kit #3 was sent.
  +
  +
<pre>
  +
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
  +
<LRMOutstandingPrepFiles companyName="Acme" inContextQALicenseEndDate="2020-01-15
  +
" licenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-version="5.0.28" p
  +
rojectID="5" projectName="Weather" timezone="GMT" topLevelDirectory="/var/li
  +
b/jenkins/jobs/AcmeWeather/workspace/WeatherWidget-master/resources">
  +
<locale>de_DE</locale>
  +
<prepkits>
  +
<prepkit sentdate="2019-06-26 20:59:26" versionnum="2">
  +
<files>
  +
<file>/Weather_de_DE.properties</file>
  +
</files>
  +
</prepkit>
  +
</prepkits>
  +
</LRMOutstandingPrepFiles>
  +
</pre>
  +
  +
*<code><prepkit sentdate="2019-06-26 20:59:26" versionnum="2"></code> - this was the prep kit that was previously sent.
  +
*<code><files></code> - and the files in the previously sent prep it.
  +
  +
= I have clicked on Prep Kit but I don't want this kit to be translated any more. How do I deactivate the kit? =
  +
When you have pressed the '''Prep Kit''' button, a number of steps were taken. In particular, a prep kit was created, the database was updated, and the files were sent to the configured translation end point.
  +
  +
For example, suppose you have a project Acme.Weather with two prep kits outstanding (#2 and #3), but you want to deactivate #2.
  +
  +
[[File:DeactivateKit.jpg|600px]]
  +
  +
Build With Parameters and run the DeactivateKit job.
  +
This will error:
  +
  +
Error 410: Prep kit version `2` for project `Weather` cannot be activated or deactivated because there are later prep kits.
  +
  +
Specify the latest prep kit (#3)
  +
Prep kit version `3` for project `Weather` was deactivated successfully.
  +
  +
And the Dashboard will be updated to show only Prep Kit #2 sent and the content of Prep Kit #3 is now in Next Prep Kit Content.
  +
  +
[[File:DeactivateKit2.png|700px]]
  +
  +
= I always want to send full files rather than deltas to my vendor. How do I set this up? =
  +
By default, Localyzer sends out deltas in a prep kit (CHANGES-ONLY) unless there is a missing file.
  +
This setting, <code>prep.kit.changes.only</code>, is located in configuration file '''<code>config_lrm_info.properties</code>''' which resides in the '''<code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config</code>''' folder.
  +
  +
<pre>
  +
### Prep Kit Type Setting ###
  +
#Default to changes only prep kits; (1-true, 0-false)
  +
prep.kit.changes.only=1
  +
</pre>
  +
  +
The possible values are:
  +
* 0 - prep files are for full-file
  +
* 1 - prep files can be for changes-only
  +
  +
= When I prep a kit, I get many prep kits instead of just one, why? =
  +
  +
  +
[[File:Build1.png|700px]]
  +
  +
* In your configuration, check the '''Send Unique File Names''' if you want the prep kit files to have unique file names. The default is not to send unique file names. If you have multiple file names that have the same name you may want to check the box. For more information see [[LRM_Unique_File_Names|Localyzer Unique File Names]].
  +
  +
= Is there a way to create a prep kit zip file that contains files for all the locales rather than just 1 zip file per locale? =
  +
If there is a need to send files for '''all''' the locales in 1 zip file, then the <code>prep.kit.locales.in.one.project</code> flag needs to be changed in configuration file '''<code>config_lrm_info.properties</code>''' which resides in the '''<code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config</code>''' folder. The L10n Vendors supporting one prep kit for all locales are '''FTP''', '''Local''' and '''Lingotek'''. See [[Zip_Files_For_Prep_and_Import | Prep/Import Zip Files]] for more information.

Latest revision as of 16:20, 11 May 2022

What is a Baseline?

A baseline is done when a Localyzer project is created to track the information in the base files and the translated files. If any of those keys and values are modified before a Prep Kit is created, the changes will be caught. For more information see Baseline.

What is a Prep Kit?

A Prep Kit is what we call the set of resource files that are gathered by Localyzer, sent out for translation, and then integrated back into the source code tree once translated. Localyzer sets and tracks versions of a Kit so that, as your developers add strings to the base resource files, you can prepare and send out the kit multiple times. There are a variety of checks that Localyzer makes on the base resource files to ensure that they are correct, as well as tracking the progress and correctness of the translated resource files.

Note: If your project contains translated files, then when prepping your first kit, Localyzer will not be able to detect if a text change has occurred within a resource string. It will, however, be able to detect added keys or missed translations.

How do I prep a kit and receive it back from translation?

There is a Jenkins job on-boarded. The Lingoport Dashboard is populated and the L10n Vendor has been configured. A Prep Kit can be sent. At this point, the Lingoport Dashboard for the project looks something like:

DashboardPrepKit.png


  • Last Sent Kit is 0 since no prep kits have been sent yet.
  • All the Locales are at 0 Percent Complete since we only have a base resource file.
  • Under Next Send Translation Content, it shows that we are sending 1 file that has 65 keys and 85 words.
  • Since we have not sent anything yet, there is nothing in Translation Package Due Dates

To send a prep kit, either select the Prep Kit button on the Dashboard (this runs the DashboardPrepKit job in Jenkins) or run the PrepKit job in Jenkins called <group>.<project>-PrepKit.

When everything is successful, the Dashboard should look like:

AfterPrepKit2.png

  • Last Sent Kit is 1 since we sent Prep Kit #1 to be translated.
  • All the Locales are at still at 0 Percent Complete since we have not gotten the translations back, but there is a note: There are outstanding prep kits for this locale
  • Under Next Send Translation Content, there is nothing because everything at this point has been sent.
  • Translation Package Due Dates shows 1 file for each locale was sent and when it is due back.

For the persons that were designated in the Jenkins job to get notifications of prep kits, an email will be sent. When the prep kit is successfully sent out, the email will be an Upload Success. There will be one email for each locale.

UploadSuccess.jpg

This shows just the German (de_DE) locale.

  • Note that it shows CET.NOAA.1.de_DE that is <group-name>.<project-name>.<prep kit number>.<locale>
  • It shows where to find the files on the local machine that were sent to translation.
  • It lists the files sent to be translated to German. In this example, there is only 1 file.


When the files have been translated, they are put in a special directory and Jenkins routinely checks for files to be downloaded. The files are downloaded and and then the translated files are pushed to the repository. To do this manually, invoke the FTPDownload Jenkins job if using FTP. Once the files have been downloaded, the Dashboard will update to reflect the changes.

AfterImport2.png

  • Next Send Translation Content and Translation Package Due Dates are empty. All files have been translated.
  • Each Locale shows 100% Complete with 0 Files, Keys or Words Remaining.

The code repository will have the translated files.

What is done when a prep kit is generated?

After a Localyzer project is created and correctly identifies the base and target resource files, the project needs to be baselined. When the project is baselined, the base resource files are in the system. If any changes happen to them afterward, this will be picked up in the prep kit. This is done in the Jenkins Nightly job or it can be done on the command line. 

 > java -jar /var/lib/jenkins/lingoport/lrm-server-<version>/lrm-cli.jar --create-baseline --project-name <project-name> -- group-name <group-name>

Localyzer is able to detect modified text as well as missing keys and missing files.

For example let's say you have a project with:

  • 3 locales: en_US (base locale), fr_FR and de_DE.
  • 2 base files
    • file1_en_US.properties (100 keys)
    • file2_en_US.properties
  • 1 fr_FR file with a missing key
    • file1_fr_FR.properties (99 keys)
  • 1 de_DE with 2 missing keys
    • file1_de_DE.properties (98 keys)


Create a prep kit for the new Localyzer project by selecting the Prep Kit button on the Lingoport Dashboard or by running the Jenkins <project-name>-PrepKit job. 

> java -jar lrm-cli.jar -pk -pn ProjectName -gn GroupName
The following reports were generated:
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/BaseFileSearch_de_de.xml
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/BaseFileSearch_fr_fr.xml
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/FilesToPrep.xml
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/ProjectName_1_de_de.xml
/var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/ProjectName_1_fr_fr.xml
Process completed successfully.

The base locale resource files are extracted and placed in the appropriate localized prep kit folders. See the de_de and fr_fr folders in /var/lib/jenkins/Lingoport_Data/LRM/<GroupName>/prep_kit/<ProjectName>/PREP_KIT_<num>. 

> ls /var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/
BaseFileSearch_de_de.xml  FilesToPrep.xml      ProjectName_1_fr_fr.xml
BaseFileSearch_fr_fr.xml  fr_fr/
de_de/                     ProjectName_1_de_de.xml

In the fr_fr folder, are all the files to be translated: 

> ls /var/lib/jenkins/Lingoport_Data/LRM/GroupName/prep_kit/ProjectName/PREP_KIT_1/fr_fr/
file1_en_US.properties           
file2_en_US.properties

For missing files, the entire file will be sent. For missing keys (or modified text) only the changed keys will be sent.

By default, when prep kits are sent, a zip file is created for each locale with the name: <GroupName>.<ProjectName>.<prep kit number>.<locale>.zip. For example, for Acme project Weather, prep kit 5 and locale 'FR_fr': Acme.Weather.5.fr_fr.zip. If there is a need to send files for all the locales in 1 zip file, then the prep.kit.locales.in.one.project flag needs to be changed in configuration file config_lrm_info.properties which resides in the /var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config folder. See Prep/Import Zip Files for more information.

How can I prevent a file or folder from being included in the prep kit?

You will need to alter your project definition file and exclude the file/folder from the project.

In Jenkins, select the project you are working on and select Configure from the menu.

AddExclude.jpg

Scroll down to the Directories section and select the Add Exclude Directory File button which will create a new entry. Add the directory or file you want to exclude. Save your project. In this example, we added the **/test/** directory.

When the project is run, the Jenkins output shows: 

Creating Project Definition File: /var/lib/jenkins/Lingoport_Data/LRM/<group-name>/reports/<project-name>/ProjectDefinition.xml

If you open the Project Definition File, you should see your new addition(<exclude-dir-file>**/test/**</exclude-dir-file>) to the excludes: 

<excludes>
     <exclude-dir-file>**\*_eo.properties</exclude-dir-file>
     <exclude-dir-file>**/LRMScans/**</exclude-dir-file>
     <exclude-dir-file>**/GlobalyzerScans/**</exclude-dir-file>
     <exclude-dir-file>**/sonar-project.properties</exclude-dir-file>
     <exclude-dir-file>**/test/**</exclude-dir-file>
 </excludes>

Modified text does not seem to be recognized as a change in my base resource file. What is wrong?

Modified text can only be detected if there has been a baseline created for the project. In this way, Localyzer can detect any modifications to file text. The Jenkins nightly Notification job for a project automatically calls the create baseline command. This command can also be called on the command line. See Create Project Baseline for more information.

When I prep a kit, what files are created?

When you prep a kit from either Jenkins or the Lingoport Dashboard and it is successful, the resulting files will be located in : 

/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/projects/<project-name>/prepkits/PREP_KIT_<number>

And may contain the following files and directories.

<locales>

For each locale that needs to be translated, there is a directory named for that locale resource files for that locale. The file may be the whole resource file if no translations exist and will have FULL-FILE in the comment at the top of the file. If the file is just for changes that have occurred since the last translation, it will have just those changes in the file and CHANGES-ONLY in the comment header line.

FilesToPrep.xml

This file shows what is displayed much more nicely in the Dashboard. 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<LRMFilesToPrepTag companyName="Acme" default-locale="en_US" inContextQALicenseEn
dDate="2020-01-15" licenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-v
ersion="5.0.28" projectID="5" projectName="Weather" timezone="GMT" topLevelD
irectory="/var/lib/jenkins/jobs/Acme.Weather/workspace/WeatherWidget-master/resources">
  <locales>
    <prep-info locale="fr_CA" localeDisplayName="French (Canada)" nbFilesToTrans
late="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
    <prep-info locale="de_DE" localeDisplayName="German (Germany)" nbFilesToTran
slate="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
    <prep-info locale="fr_FR" localeDisplayName="French (France)" nbFilesToTrans
late="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
    <prep-info locale="es_MX" localeDisplayName="Spanish (Mexico)" nbFilesToTran
slate="1" nbKeysToTranslate="62" nbWordsToTranslate="82"/>
  </locales>
  <files>
    <file-path file="/Weather_en_US.properties"/>
  </files>
</LRMFilesToPrepTag>
  • companyName="Acme"
  • default-locale="en_US"
  • projectName="Weather"
  • topLevelDirectory="/var/lib/jenkins/jobs/Acme.Weather/workspace/WeatherWidget-master/resources"
  • For each locale to translate:
    • nbFilesToTranslate="1" - number of Files to Translate
    • nbKeysToTranslate="62" - number of Keys to Translate
    • nbWordsToTranslate="82" - number of Words to Translate
  • <files> - a list of files to translate. The files are shown in the relative path from the topLevelDirectory

BaseFileSearch_<locale>.xml

This report shows the specifics for the <locale> given. Especially for the list of files. 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<LRMBaseFileSearchResults companyName="Acme" inContextQALicenseEndDate="2020-01-1
5" licenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-version="5.0.28"
projectID="5" projectName="Weather" timezone="GMT" topLevelDirectory="/var/l
ib/jenkins/jobs/Acme.Weather/workspace/NOAAWeatherWidget-master/resources">
  <locale>de_DE</locale>
  <nbKeysToTranslate>62</nbKeysToTranslate>
  <nbWordsToTranslate>82</nbWordsToTranslate>
  <nbFilesToTranslate>1</nbFilesToTranslate>
  <is-prepkit-override>0</is-prepkit-override>
  <results>
    <result file="/Weather_en_US.properties"/>
  </results>
</LRMBaseFileSearchResults>

IncompletePrepKit.xml

This report contains the information used in Dashboard Prep Kit Due dates. 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<LRMIncompletePrepKit companyName="Acme" inContextQALicenseEndDate="2020-01-15" l
icenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-version="5.0.28" proj
ectID="5" projectName="Weather" timezone="GMT" topLevelDirectory="/var/lib/j
enkins/jobs/Acme.Weather/workspace/WeatherWidget-master/resources">
  <prepkits>
    <prepkit completiondate="" sentdate="2019-06-24 21:54:48" versionnum="1">
      <results>
        <result completiondate="" initialduedate="2019-06-27 21:54:49" locale="f
r_FR" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
        <result completiondate="" initialduedate="2019-06-27 21:54:49" locale="fr_CA" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
        <result completiondate="" initialduedate="2019-06-27 21:54:49" locale="es_MX" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
        <result completiondate="" initialduedate="2019-06-27 21:54:49" locale="de_DE" nbFiles="1" nbWordsToTranslate="82" revisedduedate="2019-06-27 21:54:55" status="INCOMPLETE"/>
      </results>
    </prepkit>
  </prepkits>
  <summaries>
    <summary completiondate="" completiondateversionnum="0" locale="fr_CA" local
eDisplayName="French (Canada)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
    <summary completiondate="" completiondateversionnum="0" locale="de_DE" local
eDisplayName="German (Germany)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
    <summary completiondate="" completiondateversionnum="0" locale="es_MX" local
eDisplayName="Spanish (Mexico)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
    <summary completiondate="" completiondateversionnum="0" locale="fr_FR" local
eDisplayName="French (France)" sentdate="2019-06-24 21:54:48" sentdateversionnum="1"/>
  </summaries>
</LRMIncompletePrepKit>

OutstandingPrepFiles_<locale>.xml

If you send a prep kit and there is already a prep kit that hasn't returned, you will get this file. In the example below, this file was in the PREP_KIT_3 folder. Prep kit #1 had been returned, but #2 had not and then prep kit #3 was sent. 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<LRMOutstandingPrepFiles companyName="Acme" inContextQALicenseEndDate="2020-01-15
" licenseEndDate="2020-01-15" licenseNumOfProjects="1000" lrm-version="5.0.28" p
rojectID="5" projectName="Weather" timezone="GMT" topLevelDirectory="/var/li
b/jenkins/jobs/AcmeWeather/workspace/WeatherWidget-master/resources">
  <locale>de_DE</locale>
  <prepkits>
    <prepkit sentdate="2019-06-26 20:59:26" versionnum="2">
      <files>
        <file>/Weather_de_DE.properties</file>
      </files>
    </prepkit>
  </prepkits>
</LRMOutstandingPrepFiles>
  • <prepkit sentdate="2019-06-26 20:59:26" versionnum="2"> - this was the prep kit that was previously sent.
  • <files> - and the files in the previously sent prep it.

I have clicked on Prep Kit but I don't want this kit to be translated any more. How do I deactivate the kit?

When you have pressed the Prep Kit button, a number of steps were taken. In particular, a prep kit was created, the database was updated, and the files were sent to the configured translation end point.

For example, suppose you have a project Acme.Weather with two prep kits outstanding (#2 and #3), but you want to deactivate #2.

DeactivateKit.jpg

Build With Parameters and run the DeactivateKit job. This will error: 

Error 410: Prep kit version `2` for project `Weather` cannot be activated or deactivated because there are later prep kits.

Specify the latest prep kit (#3) 

Prep kit version `3` for project `Weather` was deactivated successfully.

And the Dashboard will be updated to show only Prep Kit #2 sent and the content of Prep Kit #3 is now in Next Prep Kit Content.

DeactivateKit2.png

I always want to send full files rather than deltas to my vendor. How do I set this up?

By default, Localyzer sends out deltas in a prep kit (CHANGES-ONLY) unless there is a missing file. This setting, prep.kit.changes.only, is located in configuration file config_lrm_info.properties which resides in the /var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config folder. 

### Prep Kit Type Setting ###
#Default to changes only prep kits; (1-true, 0-false)
prep.kit.changes.only=1

The possible values are:

  • 0 - prep files are for full-file
  • 1 - prep files can be for changes-only

When I prep a kit, I get many prep kits instead of just one, why?

Build1.png

  • In your configuration, check the Send Unique File Names if you want the prep kit files to have unique file names. The default is not to send unique file names. If you have multiple file names that have the same name you may want to check the box. For more information see Localyzer Unique File Names.

Is there a way to create a prep kit zip file that contains files for all the locales rather than just 1 zip file per locale?

If there is a need to send files for all the locales in 1 zip file, then the prep.kit.locales.in.one.project flag needs to be changed in configuration file config_lrm_info.properties which resides in the /var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config folder. The L10n Vendors supporting one prep kit for all locales are FTP, Local and Lingotek. See Prep/Import Zip Files for more information.

Retrieved from "http://wiki.lingoport.com/index.php?title=Prep_Kits&oldid=96259"