XTM

Link LRM and XTM

Configure <HOME>/Lingoport_Data/L10nStreamlining/<group name>/config/config_l10n_vendor.properties:

• uncomment l10n.vendor=local
• configure local.out.absolute.path
• configure local.in.absolute.path

Configure <HOME>/Lingoport_Data/L10nStreamlining/config/config_xtm_tofrom.properties:

• configure xtm.to.translation.dir
• configure xtm.from.translation.dir

XTM Configuration

The file information that is needed to upload the files to be translated as well as retrieve translated files is in the :

#Lingotek Attributes
#Contains the host URL and api request formats
lingotek.api.hosturl=https://cms.lingotek.com

#Contains the ids for community, workflow and access token
lingotek.api.id.access.token=
lingotek.api.id.community=
lingotek.api.id.workflow=

#Example callbackURL - replace job name (lingotek) with actual Jenkins job name
lingotek.api.callbackurl=http://jenkins.company.com:8080/buildByToken/buildWithParameters?job=LingotekCallback&token=LINGOSQUARE&

#{0} is the access.token
lingotek.api.bearer=Bearer {0}

XTM Locale Mapping

XTM does not allow language only locales. If there are LRM target locales that are language-only, then a mapping between the LRM locale and the XTM locale should be entered into config_xtm_locale_mapping.properties file if it doesn't already exist.

The default location for the configuration file is at the group level (<HOME>/Lingoport_Data/L10nStreamlining/<group name>/config). The configuration file also exists in the LRM install directory's <HOME>/lingoport/lrm-server-x.y/deploy/templates/dir_structure/group/config folder.

#
#Locale mapping language only locales - Locales should be in the java format (_)
# This is the default mapping. For your community, you'll need to edit this file
# and place it either at the group level or the project level.
#
aa=aa_DJ
ab=ab_GE
af=af_ZA
ak=ak_GH
am=am_ET
...