About InContext Translation - Revision history

Olibouban at 20:57, 26 April 2022

2022-04-26T20:57:18Z

← Older revision		Revision as of 20:57, 26 April 2022
Line 26:		Line 26:
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. Localyzer then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. Localyzer then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#Decorated\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.		* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#Decorated\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.

			= License =
			[[InContext Translation License]]

Olibouban at 20:25, 23 February 2021

2021-02-23T20:25:46Z

← Older revision		Revision as of 20:25, 23 February 2021
Line 21:		Line 21:
	For an on-boarded repository, the happy path looks like:		For an on-boarded repository, the happy path looks like:
	* The repositories contain base resource files created by developers and files translated by the LSP (localization service provider).		* The repositories contain base resource files created by developers and files translated by the LSP (localization service provider).
	* ~~LRM~~ analyzes the resource files and '''instruments''' both base and target files.		* Localyzer analyzes the resource files and '''instruments''' both base and target files.
	* ~~LRM~~ pushes the '''instrumented''' files to the repository		* Localyzer pushes the '''instrumented''' files to the repository
	* An instrumented build gets deployed		* An instrumented build gets deployed
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. ~~LRM~~ then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. Localyzer then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#Decorated\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.		* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#Decorated\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.

Rdaly: /* System Overview */

2019-05-02T16:20:41Z

System Overview

← Older revision		Revision as of 16:20, 2 May 2019
Line 25:		Line 25:
	* An instrumented build gets deployed		* An instrumented build gets deployed
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#~~Decoration~~\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.		* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#Decorated\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.

Rdaly: /* System Overview */

2019-05-02T16:19:44Z

System Overview

← Older revision		Revision as of 16:19, 2 May 2019
Line 25:		Line 25:
	* An instrumented build gets deployed		* An instrumented build gets deployed
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL, a ~~'''~~decoration~~'''~~, pointing back to a Lingoport '''InContext Server''' that stores the context.		* When files are sent to translation, each segment may have a context and a URL, a [[Terms_and_Definitions#Decoration\|decoration]], pointing back to a Lingoport '''InContext Server''' that stores the context.

Olibouban: /* System Overview */

2019-04-26T19:48:47Z

System Overview

← Older revision		Revision as of 19:48, 26 April 2019
Line 25:		Line 25:
	* An instrumented build gets deployed		* An instrumented build gets deployed
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL, a decoration, pointing back to a Lingoport '''InContext Server''' that stores the context.		* When files are sent to translation, each segment may have a context and a URL, a '''decoration''', pointing back to a Lingoport '''InContext Server''' that stores the context.

Rdaly: /* System Overview */

2019-04-25T20:03:41Z

System Overview

← Older revision		Revision as of 20:03, 25 April 2019
Line 25:		Line 25:
	* An instrumented build gets deployed		* An instrumented build gets deployed
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL pointing back to a Lingoport '''InContext Server''' that stores the context.		* When files are sent to translation, each segment may have a context and a URL, a decoration, pointing back to a Lingoport '''InContext Server''' that stores the context.

Olibouban at 19:11, 5 April 2019

2019-04-05T19:11:13Z

← Older revision		Revision as of 19:11, 5 April 2019
Line 1:		Line 1:
	InContext Translation is a Lingoport product ~~to be used by translators that~~ passes the context of a Web application along with the resource to be translated. Translation Management Systems (TMSs) can then show the context within the translation workbench, either via a note, a comment, a clickable link, or a view from within their computer aided translation (CAT) tools.		Translators use InContext Translation, a Lingoport product which passes the context of a Web application along with the resource to be translated. Translation Management Systems (TMSs) can then show the context within the translation workbench, either via a note, a comment, a clickable link, or a view from within their computer aided translation (CAT) tools.

	[[File:InContextTranslation.jpg\|700px]]		[[File:InContextTranslation.jpg\|700px]]

Rdaly at 19:16, 3 April 2019

2019-04-03T19:16:39Z

← Older revision		Revision as of 19:16, 3 April 2019
Line 6:		Line 6:

	= Goals =		= Goals =
	* The Lingoport InContext Translation allows for a better-quality translation earlier with possibly reduced need for downstream Linguistic QA. Lingoport is not a translation company or a TMS (Translation Management System) vendor. The aim of InContext Translation is to provide the TMS with the ability to associate segments with context.		* The Lingoport InContext Translation product allows for a better-quality translation earlier with possibly reduced need for downstream Linguistic QA. Lingoport is not a translation company or a TMS (Translation Management System) vendor. The aim of InContext Translation is to provide the TMS with the ability to associate segments with context during the translation process.

	= Benefits =		= Benefits =
	* The translation team uses the TMS, tools, products, and processes of their choice		* The translation team uses the TMS, tools, products, and processes of their choice.
	* Agile: short translation bursts come from different projects and applications: Context really helps translation		* Agile: short translation bursts come from different projects and applications: Context really helps translation.
	* The translation context can be invoked by a simple URL		* The translation context can be invoked by a simple URL .
	* No software developer involvement		* No software developer involvement.
	* Non-intrusive		* Non-intrusive

Rdaly: /* System Overview */

2019-03-29T18:37:55Z

System Overview

← Older revision		Revision as of 18:37, 29 March 2019
Line 25:		Line 25:
	* An instrumented build gets deployed		* An instrumented build gets deployed
	* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.		* With each navigation to a new page on the '''instrumented''' deployment, the '''InContext Capture''' Chrome extension saves the context back to the Lingoport VM. LRM then sends the association between the context and each of the base resources to the TMS.
	* When files are sent to translation, each segment may have a context and a URL pointing back to a Lingoport '''InContext Server'''		* When files are sent to translation, each segment may have a context and a URL pointing back to a Lingoport '''InContext Server''' that stores the context.

Rdaly at 18:19, 29 March 2019

2019-03-29T18:19:15Z

← Older revision		Revision as of 18:19, 29 March 2019
Line 1:		Line 1:
	InContext Translation is a Lingoport product that passes the context of a Web application along with the resource to be translated. Translation Management Systems (TMSs) can then show the context within the translation workbench, either via a note, a comment, a clickable link, or a view from within their computer aided translation (CAT) tools.		InContext Translation is a Lingoport product to be used by translators that passes the context of a Web application along with the resource to be translated. Translation Management Systems (TMSs) can then show the context within the translation workbench, either via a note, a comment, a clickable link, or a view from within their computer aided translation (CAT) tools.

	[[File:InContextTranslation.jpg\|700px]]		[[File:InContextTranslation.jpg\|700px]]