L10n Vendors

Supported L10n Vendors

Currently, LRM supports 3 paths for sending files to be translated. They are:

• FTP
• Lingotek
• Worldserver

The type of L10n Vendor is defined in the config_l10n_vendor.properties that can exist at either the group or project level. See Group Configuration Files

The default location of the config_l10n_vendor.properties file is at the group level. The default settings do not define a vendor so that an error will occur when prepping a kit, forcing the user to chose a vendor. The global L10n Vendor attributes are:

• l10n.vendor=lingotek - uncomment if using Lingotek
• l10n.vendor=worldserver - uncomment if using Worldserver
• l10n.vendor=ftp - uncomment if using FTP
• l10n.vendor.nonsupported.extensions - a vendor may not support a specific extension such as .json. Enter any extensions that are not supported by the vendor but are supported by LRM. See LRM Fixing Issues for LRM supported extensions. An error will occur if there is no conversion protocol for a non-supported extension.

Example file:

#Default to 'no vendor defined'
#l10n.vendor=lingotek
#l10n.vendor=worldserver
#l10n.vendor=ftp

l10n.vendor.nonsupported.extensions=

FTP

To choose FTP as the vendor, uncomment the l10n.vendor=ftp in the config_l10n_vendor.properties file.

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

#FTP Attributes
## FTP inbound attributes for import kit files
ftp.in.host=
ftp.in.location.path=
ftp.in.password=
ftp.in.port=
#SSH, SSL or empty
ftp.in.protocol=
ftp.in.username=
# FTP outbound attributes for prep kit files
ftp.out.host=
ftp.out.location.path=
ftp.out.password=
ftp.out.port=
ftp.out.protocol=
ftp.out.username=

Lingotek

To choose FTP as the vendor, uncomment the l10n.vendor=lingotek in the config_l10n_vendor.properties file.

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

#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}

Worldserver

To choose Worldserver as the vendor, uncomment the l10n.vendor=worldserver in the config_l10n_vendor.properties file.

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

#WORLDSERVER Attributes
## Worldserver attributes for import kit files
#worldserver.in.host=
#worldserver.in.location.path=
#worldserver.in.password=
#worldserver.in.port=22
#SSH, SSL or blank (for FTP)
#worldserver.in.ftp.protocol=SSH
#worldserver.in.username=
##Zip file name that contains the translated files needs to one of the following options.
## Option #1 for zip file prefix
#worldserver.in.file.name.prefix=${groupname}.${projectname}.${kitversion}.${lrmlocale}
## Option #2 for zip file prefix
#worldserver.in.file.name.prefix=${groupname}.${projectname}.${kitversion}.${wslocale}
## Option #3 for zip file prefix
#worldserver.in.file.name.prefix=${groupname}.${projectname}.${kitversion}.${lrmlocale}.${wslocale}

## Worldserver attributes for send kit files
#worldserver.out.url=
#worldserver.out.user=
#worldserver.out.password=
#worldserver.client=
## Available tokens ${groupname},${projectname},${kitversion},${lrmlocale}, ${wslocale}
#worldserver.out.project.name=${groupname}.${projectname}.${kitversion}.${lrmlocale}