Difference between revisions of "InContext Translation Installation"
| Line 1: | Line 1: | ||
| + | InContext Translation is made up of three Components: |
||
| − | = Goals = |
||
| + | * LRM Instrumentation |
||
| − | * 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 vendor. The aim of In Context Translation is to provide TMS with the ability to associate segments with context. |
||
| + | * InContext Server |
||
| + | * InContext Capture |
||
| − | = Benefits = |
||
| − | * |
||
| − | |||
| − | = System Overview = |
||
| − | |||
| − | [[File:Lingoport_incontext_translation.png|650px]] |
||
| − | |||
| − | 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 Context Server |
||
[[InContext_Capture_Installation]] |
[[InContext_Capture_Installation]] |
||
Revision as of 17:33, 20 February 2019
InContext Translation is made up of three Components:
- LRM Instrumentation
- InContext Server
- InContext Capture
