L10n Vendors and Integration - Revision history

Rdaly: /* InContext Token */

2022-08-26T19:02:34Z

InContext Token

← Older revision		Revision as of 19:02, 26 August 2022
Line 98:		Line 98:

	===== InContext Token =====		===== InContext Token =====
	The Incontext Token value must match one of the ~~Tokens~~ configured on the Settings page of the InContext Server. Together with the InContext Server URL, the token is used to display the content to the translator for InContext Translation. This authorization token will be supplied by your InContext Server administrator.		The Incontext Token value must match one of the tokens configured on the Settings page of the InContext Server. Together with the InContext Server URL, the token is used to display the content to the translator for InContext Translation. This authorization token will be supplied by your InContext Server administrator.

	===== InContext Unique Tag =====		===== InContext Unique Tag =====

Rdaly: /* What are L10n Vendors? */

2022-08-25T22:36:16Z

What are L10n Vendors?

← Older revision		Revision as of 22:36, 25 August 2022
Line 1:		Line 1:
	=What are L10n Vendors?=		=What are L10n Vendors?=

	Localyzer packages the resources files and send them to localization service providers and translation management systems to translate the files. There are many ways to send the files and they can be done a number of different ways that depend on a different factors including the translation management system.		Localyzer packages the resources files and send them to localization service providers (LSP) and translation management systems (TMS) to translate the files. There are many ways to send the files and they can be done a number of different ways that depend on different factors including the translation management system.

	=Supported L10n Vendors=		=Supported L10n Vendors=

Llawson: /* WorldServer Vendor */

2022-05-11T17:10:40Z

WorldServer Vendor

← Older revision		Revision as of 17:10, 11 May 2022
Line 201:		Line 201:

	The default location of the config_l10n_vendor.properties file is at the group level in <code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config</code>.		The default location of the config_l10n_vendor.properties file is at the group level in <code>/var/lib/jenkins/Lingoport_Data/L10nStreamlining/<group-name>/config</code>.

			==== Configuration Details ====
			See [[WorldServer\|advanced WorldServer vendor info]] for more WorldServer configuration details.

	=== Machine Translation Vendors ===		=== Machine Translation Vendors ===

Llawson: /* Translation Lingotek Vendor Integration */

2022-05-11T17:09:25Z

Translation Lingotek Vendor Integration

← Older revision		Revision as of 17:09, 11 May 2022
Line 185:		Line 185:
	* The Jenkins URL will be something like: '''https://<IP address>/jenkins'''. Probably of the current system.		* The Jenkins URL will be something like: '''https://<IP address>/jenkins'''. Probably of the current system.

	==== ~~Translation Lingotek Vendor Integration~~ ====		==== Configuration Details ====
	See [[Lingotek\|advanced Lingotek vendor info]] for more Lingotek configuration details.		See [[Lingotek\|advanced Lingotek vendor info]] for more Lingotek configuration details.

Llawson: /* Lingotek Vendor */

2022-05-11T17:07:33Z

Lingotek Vendor

← Older revision		Revision as of 17:07, 11 May 2022
Line 184:		Line 184:
	* Set the Lingotek credentials. If these are unknown, contact Lingotek or ''support@lingoport.com''.		* Set the Lingotek credentials. If these are unknown, contact Lingotek or ''support@lingoport.com''.
	* The Jenkins URL will be something like: '''https://<IP address>/jenkins'''. Probably of the current system.		* The Jenkins URL will be something like: '''https://<IP address>/jenkins'''. Probably of the current system.
	* See [[Lingotek\|advanced Lingotek vendor info]] for more Lingotek configuration details.
			==== Translation Lingotek Vendor Integration ====
			See [[Lingotek\|advanced Lingotek vendor info]] for more Lingotek configuration details.

	=== WorldServer Vendor ===		=== WorldServer Vendor ===

Llawson: /* Local Vendor */

2022-05-11T17:06:52Z

Local Vendor

← Older revision		Revision as of 17:06, 11 May 2022
Line 163:		Line 163:
	* [[XTM]] and [[Memsource]] use the local vendor for their configurations. Continuing to these links gives more information.		* [[XTM]] and [[Memsource]] use the local vendor for their configurations. Continuing to these links gives more information.

			==== Translation Local Vendor Integration ====
	See [[Local_Vendor\|advanced Local vendor info]] for more vendor details.		See [[Local_Vendor\|advanced Local vendor info]] for more vendor details.

Llawson: /* Example of the Zip File Structure */

2022-05-11T17:06:00Z

Example of the Zip File Structure

← Older revision		Revision as of 17:06, 11 May 2022
Line 173:		Line 173:
	* Often FTP uses port 22 and SSH. Change this if the configuration differs.		* Often FTP uses port 22 and SSH. Change this if the configuration differs.

	==== ~~Example of the Zip File Structure~~ ====		==== Translation FTP Vendor Integration ====
	See [[Zip_Files_For_Prep_and_Import \| Prep/Import Zip Files]] for more information.		See [[Zip_Files_For_Prep_and_Import \| Prep/Import Zip Files]] for more information.

Llawson: /* Translation FTP Vendor Integration */

2022-05-11T17:05:05Z

Translation FTP Vendor Integration

← Older revision		Revision as of 17:05, 11 May 2022
Line 241:		Line 241:

	A possible issue may be the port number: port 22 is typically used for FTP/SSH; port 21 is typically used for vanilla FTP. Change the port number in '''config_l10n_vendor.properties''' and test again.		A possible issue may be the port number: port 22 is typically used for FTP/SSH; port 21 is typically used for vanilla FTP. Change the port number in '''config_l10n_vendor.properties''' and test again.

	~~= Translation FTP Vendor Integration=~~
	~~Lingoport pushes zip files to the configured FTP outbound endpoint and consumes zip files sent on the incoming endpoint. The structure of the zip file is defined below:~~

	~~The files sent back and forth over FTP have the following characteristics:~~

	* The data files to be translated or returned from translation are sent in a '''zip file'''.
	* The '''zip file''' is named according to this convention: '''<code><group-name>.<project-name>.<kit-version>.<locale>.zip</code>'''. For example, a zip file could be named '''<code>Queens.Champions.1.fr_fr.zip</code>''': The group-name is Queens, the project-name is Champions, the kit version is 1, and the target locale is fr_FR.
	* The zip file consists of '''one top level directory''', <code><group-name>.<project-name>.<kit-version>.<locale></code>, with all the files to be translated under it.
	* There is '''one zip file per target locale'''. You may target 10 locales for translation for project "Champions" under group "Queens". You then would have 10 zip files to send over FTP.
	* A zip file may contain '''more than one file and more than one file type'''.
	* Each file to be translated has a comment at the top of the file which needs to be kept when returning the file from translation vendor.
	* The '''translated files''' will be named the same as the original files (so they could be _en.properties even if the content is for French)

	~~Two FTP endpoints are necessary: a ''''to translation'''' end point and a ''''from translation'''' endpoint.~~

	= How do I setup a proxy for a project's FTP server? =		= How do I setup a proxy for a project's FTP server? =

Llawson: /* FTP Vendor */

2022-05-11T17:04:44Z

FTP Vendor

← Older revision		Revision as of 17:04, 11 May 2022
Line 173:		Line 173:
	* Often FTP uses port 22 and SSH. Change this if the configuration differs.		* Often FTP uses port 22 and SSH. Change this if the configuration differs.

			==== Example of the Zip File Structure ====
			See [[Zip_Files_For_Prep_and_Import \| Prep/Import Zip Files]] for more information.

	=== Lingotek Vendor ===		=== Lingotek Vendor ===

Llawson: /* Example of the Zip File Structure */

2022-05-11T17:04:12Z

Example of the Zip File Structure

← Older revision		Revision as of 17:04, 11 May 2022
Line 254:		Line 254:

	Two FTP endpoints are necessary: a ''''to translation'''' end point and a ''''from translation'''' endpoint.		Two FTP endpoints are necessary: a ''''to translation'''' end point and a ''''from translation'''' endpoint.

	~~=== Example of the Zip File Structure ===~~
	~~See [[Zip_Files_For_Prep_and_Import \| Prep/Import Zip Files]] for more information.~~

	= How do I setup a proxy for a project's FTP server? =		= How do I setup a proxy for a project's FTP server? =