Difference between revisions of "TradosEnterprise"
(→Configure and Enable XTM Jenkins Jobs) |
|||
| Line 39: | Line 39: | ||
</ol> |
</ol> |
||
| − | ===XTM Configuration=== |
||
| − | Configure the XTM settings in the '''config_xtm_vendor.properties''' (which can be specified at the group or project config level). |
||
| − | <pre> |
||
| − | # |
||
| − | # Contains configuration for xtm |
||
| − | # |
||
| − | # Note: this file should be placed in ~/Lingoport_Data/L10nStreamlining/<group>/config |
||
| − | # or ~/Lingoport_Data/L10nStreamlining/<group>/projects/<project>/config |
||
| − | # |
||
| − | # Run the following command to get the token: |
||
| − | # java -jar lingoport-xtm-cli.jar --get-token -s <server> -c <client> -u <userId> -p <password> |
||
| − | # |
||
| − | # Run the following command to get the customerId: |
||
| − | # java -jar lingoport-xtm-cli.jar --get-customer-id -s <server> -t <token> -cn <customerName> |
||
| − | # |
||
| − | # Run the following command to get the templateId (if using a template): |
||
| − | # java -jar lingoport-xtm-cli.jar --get-template-id -s <server> -t <token> -ci <customerid> -tn <templatename> |
||
| − | # |
||
| − | # Run the following command to get the workflowId (if using a workflow id): |
||
| − | # java -jar lingoport-xtm-cli.jar --get-workflow-id -s <server> -t <token> -wn <workflowname> |
||
| − | # |
||
| − | # Required to configure either a workflow name, workflow id, or template id |
||
| − | # |
||
| + | ===Trados Enterprise Locale Mapping=== |
||
| − | # the following are required |
||
| + | Configure '''config_trados_enterprise_locale_mapping.properties''' (which can be specified at the group or project config level).<br> |
||
| − | xtm.api.hostURL=https://api-test.xtm-intl.com |
||
| + | This file maps locales from LRM to Trados Enterprise. For example, LRM supports the language only locale '''fr''', which must be mapped to '''fr-FR''' for Trados Enterprise. |
||
| − | xtm.api.token= |
||
| − | xtm.api.id.customer= |
||
| − | xtm.api.source.locale=en_US |
||
| − | |||
| − | # optional |
||
| − | #xtm.api.proxyHost=example.proxy.com |
||
| − | #xtm.api.proxyPort=3128 |
||
| − | |||
| − | # one of the following must be configured |
||
| − | xtm.api.name.workflow= |
||
| − | xtm.api.id.workflow= |
||
| − | xtm.api.id.template= |
||
| − | |||
| − | # configure proper URL for your company |
||
| − | xtm.api.callbackURL=http://jenkins.company.com/jenkins/buildByToken/buildWithParameters/build?job=XTMCallback&token=<the_token_configured_in_XTMCallback> |
||
| − | |||
| − | # |
||
| − | # You can test your callback configuration using curl on the command line (note the escaped & before token): |
||
| − | # curl http://jenkins.company.com/jenkins/buildByToken/buildWithParameters/build?job=XTMCallback\&token=<the_token_configured_in_XTMCallback> |
||
| − | # A successful curl command simply returns. |
||
| − | # An unsuccessful curl command will display an error. |
||
| − | # |
||
| − | </pre> |
||
| − | |||
| − | ===One XTM Project for all Prep Kit Locales or One XTM Project for each Prep Kit Locale === |
||
| − | This setting is available for XTM starting with the Japan release (LRM 9.0.20). See [[Zip_Files_For_Prep_and_Import#One_Zip_File_for_all_Locales.2C_per_Prep_Kit_Number| Projects and Locales]] |
||
| − | |||
| − | When sending files to XTM for a prep kit, projects are created in XTM via the XTM API. A setting allows to have one project for all the locales where the files sent to translation are the same. |
||
| − | |||
| − | By default, when a Localyzer project is prepped, there will be one TMS project (or one zip file) per locale. If there is a need to send files for '''all''' the locales in one TMS project (or one 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>''' |
||
| − | |||
| − | This configuration file may reside under the group or the project config folder: |
||
| − | * <code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config</code> |
||
| − | * <code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config/<project-name></code> |
||
| − | |||
| − | ===XTM Locale Mapping=== |
||
| − | Configure '''config_xtm_locale_mapping.properties''' (which can be specified at the group or project config level).<br> |
||
| − | This file maps locales from LRM to XTM. For example, LRM supports the language only locale '''fr''', which must be mapped to '''fr_FR''' for XTM. |
||
<pre> |
<pre> |
||
# |
# |
||
| − | #Locale mapping language only locales - |
+ | #Locale mapping language only repo locales <--> Trados Enterprise Locales |
| + | aa=aa-DJ |
||
| − | # This is the default mapping. For your community, you'll need to edit this file |
||
| + | ab=ab-GE |
||
| − | # and place it either at the group level or the project level. |
||
| + | af=af-ZA |
||
| − | # |
||
| + | ak=ak-GH |
||
| − | aa=aa_DJ |
||
| + | am=am-ET |
||
| − | ab=ab_GE |
||
| − | af=af_ZA |
||
| − | ak=ak_GH |
||
| − | am=am_ET |
||
... |
... |
||
</pre> |
</pre> |
||
| − | |||
| − | ===LRM Resource Types Supported by XTM=== |
||
| − | |||
| − | XTM supports the following LRM resource types: |
||
| − | * .html, .htm |
||
| − | * .json |
||
| − | * .po |
||
| − | * .properties |
||
| − | * .resx |
||
| − | * .rc |
||
| − | * .rxml |
||
| − | * .strings |
||
| − | * strings.xml |
||
| − | * .txt |
||
| − | * .yaml, .yml |
||
| − | |||
| − | |||
| − | XTM does <b>not</b> support the following LRM resource types: |
||
| − | * .rjs |
||
| − | * .msg |
||
| − | |||
| − | ===XTM Special Instructions - parameters (e.g. %d, etc)=== |
||
| − | XTM expects parameters in '''.strings''' resource files to be numbered. |
||
| − | If not numbered, XTM will provide numbers during translation, which will result in a parameter mismatch error during LRM import. |
||
| − | To avoid the error, number of the parameters in the base resource file. |
||
| − | <br> |
||
| − | For example, if you have the following in a .strings resource file: |
||
| − | "Test.Key" = "Test %d and %d"; |
||
| − | It should be changed to: |
||
| − | "Test.Key" = "Test %1$d and %2$d"; |
||
| − | |||
| − | Note: a single parameter must be numbered. For example: |
||
| − | "Test.Key_Single" = "Test %1$d"; |
||
Revision as of 17:36, 27 May 2022
Link LRM and Trados Enterprise
To begin working with Trados Enterprise, create or use the following directories on the Linux file system:
/var/lib/jenkins/lingoport/translations/tradosEnterprise/to_translation/var/lib/jenkins/lingoport/translations/tradosEnterprise/from_translation- Create an Trados Enterprise local vendor in Jenkins:
- Select Manage Jenkins->Configure System
- Scroll down to the LRM L10n Vendor Setup section and select Add Local Vendor
- Provide a unique vendor name
- Select Group or Project; if group, select group name from drop down list
- Configure Prep Kit Files Directory:
/var/lib/jenkins/lingoport/translations/tradosEnterprise/to_translation - Configure Imported Files Directory:
/var/lib/jenkins/lingoport/translations/tradosEnterprise/from_translation - Save
- Configure your Jenkins job to use Trados Enterprise local vendor:
- Select the Jenkins job you want to use Trados Enterprise
- Click Configure
- Scroll down to the L10n Vendor section of your LRM configuration
- Choose Group or Project; if project, click Local Vendor and then select the Local Vendor Name from the list
- Save
Configure and Enable Trados Enterprise Jenkins Jobs
- Enable the TradosEnterpriseUpload Jenkins job.
- Enable the TradosEnterpriseDownload Jenkins job.
- Make sure the Jenkins job TradosEnterpriseUpload trigger Build after other projects are built after DashboardPrepkit.
- Modify the Jenkins job LocalVendorDownload and check Build after other projects are built and then in Projects to watch, type in TradosEnterpriseDownload.
Trados Enterprise Locale Mapping
Configure config_trados_enterprise_locale_mapping.properties (which can be specified at the group or project config level).
This file maps locales from LRM to Trados Enterprise. For example, LRM supports the language only locale fr, which must be mapped to fr-FR for Trados Enterprise.
# #Locale mapping language only repo locales <--> Trados Enterprise Locales aa=aa-DJ ab=ab-GE af=af-ZA ak=ak-GH am=am-ET ...
