From Lingoport Wiki
Jump to: navigation, search

Note: Lingotek and Lingoport are not the same company. Lingotek is a TMS provider.

When Lingotek is selected as the L10n ventor, the file is created with the following attributes.

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

#Contains the ids for community, workflow and access token

#Example callbackURL - replace job name (lingotek) with actual Jenkins job name

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

Lingotek Locale Mapping

Lingotek 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 Lingotek locale should be entered into 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.

Lingotek File Format

When sending a file via the API, a format has to be set for each suffix. The list of Lingotek format can be found at: