Difference between revisions of "About InContext Translation"
(→Goals) |
|||
| 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. TMS's can then show the context within the translation workbench, either via a note, a comment, a clickable link, or a view from within their CAT tools. |
||
| + | |||
= 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 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. |
||
= Benefits = |
= Benefits = |
||
| + | * 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 t9n |
||
| + | * The translation context can be invoked by a simple URL |
||
| + | * No software developer involvement |
||
| + | * Non-intrusive |
||
= System Overview = |
= System Overview = |
||
| Line 12: | Line 18: | ||
* The repositories contain base resource files created by developers and files translated by LSP. |
* The repositories contain base resource files created by developers and files translated by LSP. |
||
* LRM analyzes resource files and instrument both base and target files |
* LRM analyzes resource files and instrument both base and target files |
||
| − | * LRM pushes the instrumented files to the repository |
+ | * LRM 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, InContext Capture chrome extension saves the context back to the Lingoport VM and sends the association between the context and each of the base resources |
+ | * With each navigation to a new page on the '''instrumented''' deployment, '''InContext Capture''' chrome extension saves the context back to the Lingoport VM and sends the association between the context and each of the base resources |
| − | * When files are sent to translation, each segment may have a context, a URL, pointing back to a Lingoport |
+ | * When files are sent to translation, each segment may have a context, a URL, pointing back to a Lingoport '''InContext Server''' |
Revision as of 20:26, 19 March 2019
InContext Translation is a Lingoport product that passes the context of a Web application along with the resource to be translated. TMS's can then show the context within the translation workbench, either via a note, a comment, a clickable link, or a view from within their CAT tools.
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.
Benefits
- 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 t9n
- The translation context can be invoked by a simple URL
- No software developer involvement
- Non-intrusive
System Overview
For an on-boarded repository, the happy path looks like:
- The repositories contain base resource files created by developers and files translated by LSP.
- LRM analyzes resource files and instrument both base and target files
- LRM pushes the instrumented files to the repository
- An instrumented build gets deployed
- With each navigation to a new page on the instrumented deployment, InContext Capture chrome extension saves the context back to the Lingoport VM and sends the association between the context and each of the base resources
- When files are sent to translation, each segment may have a context, a URL, pointing back to a Lingoport InContext Server
