Difference between revisions of "Lingotek"
(→Lingotek) |
(→Types of projects created) |
||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | '''Note''': ''Lingotek'' and ''Lingoport'' are not the same company. Lingotek is a TMS provider. |
||
| − | To choose Lingotek as the vendor, uncomment the '''<code>l10n.vendor=lingotek</code>''' in the '''<code>config_l10n_vendor.properties</code>''' file. |
||
| + | |||
| + | When Lingotek is selected as the L10n ventor, the '''<code>config_l10n_vendor.properties</code>''' 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: |
The information that is needed to upload the files to be translated as well as retrieve translated files is: |
||
| Line 38: | Line 40: | ||
... |
... |
||
</pre> |
</pre> |
||
| + | |||
| + | === 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: |
||
| + | |||
| + | https://lingotek.atlassian.net/wiki/spaces/PDOC/pages/29403785/Supported+File+Types |
||
| + | |||
| + | === Lingotek IP addresses === |
||
| + | Lingotek needs network access to Lingoport Jenkins in order for the callbacks to reach the system. Lingotek has a set of IP addresses which needs to be allowed, for example via a Security Group in AWS. The list of IP addresses is provided below and may be updated from time to time. |
||
| + | |||
| + | https://lingotek.atlassian.net/wiki/spaces/PDOC/pages/1987837987/Whitelisting+for+outbound+Lingotek+services |
||
| + | |||
| + | As of ''June 2021'', those addresses are: |
||
| + | |||
| + | * use1a: 54.145.247.135 |
||
| + | * use1b: 54.81.151.136 |
||
| + | * use1c: 54.237.10.242 |
||
| + | * use1d: 52.6.43.156 |
||
| + | |||
| + | === Types of projects created === |
||
| + | On the Lingotek side, each prep kit zip file will be used to create a unique Lingotek project. The default is that there will be one Lingotek project per prep kit per locale. Configuration can occur if there is a need to create one Lingotek per prep kit for all locales. See [[Zip_Files_For_Prep_and_Import | Prep/Import Zip Files]] for more information. |
||
Latest revision as of 16:55, 11 May 2022
Note: Lingotek and Lingoport are not the same company. Lingotek is a TMS provider.
When Lingotek is selected as the L10n ventor, the config_l10n_vendor.properties 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
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}
Contents
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 config_lingotek_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 ...
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:
https://lingotek.atlassian.net/wiki/spaces/PDOC/pages/29403785/Supported+File+Types
Lingotek IP addresses
Lingotek needs network access to Lingoport Jenkins in order for the callbacks to reach the system. Lingotek has a set of IP addresses which needs to be allowed, for example via a Security Group in AWS. The list of IP addresses is provided below and may be updated from time to time.
https://lingotek.atlassian.net/wiki/spaces/PDOC/pages/1987837987/Whitelisting+for+outbound+Lingotek+services
As of June 2021, those addresses are:
- use1a: 54.145.247.135
- use1b: 54.81.151.136
- use1c: 54.237.10.242
- use1d: 52.6.43.156
Types of projects created
On the Lingotek side, each prep kit zip file will be used to create a unique Lingotek project. The default is that there will be one Lingotek project per prep kit per locale. Configuration can occur if there is a need to create one Lingotek per prep kit for all locales. See Prep/Import Zip Files for more information.
