InContext Translation Installation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=Overview= | |||
[[File:Lingoport_incontext_translation.png|650px]] | |||
The InContext Translation process: | |||
#Base and target resource files are instrumented by LRM and pushed to the code repository. | |||
#The instrumented resource files are deployed in a test build of the web application. | |||
#Using a Chrome browser extension, InContext Capture, the resource files and their context are captured and stored at the InContext Server (which may reside on the Lingoport Server). | |||
#LRM sends the resource files with their context to the TMS. | |||
=Installation= | |||
InContext Translation is made up of three components that must be installed: | InContext Translation is made up of three components that must be installed: | ||
* [[LRM Instrumentation | InContext LRM Intrumentation]] - The first thing to do is verify that you are using an LRM version and license for InContext Translation. | * [[LRM Instrumentation | InContext LRM Intrumentation]] - The first thing to do is verify that you are using an LRM version and license for InContext Translation. | ||
* [[InContext_Capture_Installation|InContext Capture]] - InContext Capture uses a Chrome extension to identify application resources and send the text and context to the InContext Server. | * [[InContext_Capture_Installation|InContext Capture]] - InContext Capture uses a Chrome extension to identify application resources and send the text and context to the InContext Server. | ||
* [[InContext_Server_Installation|InContext Server]] - InContext Server manages the resources identified by InContext Capture. | * [[InContext_Server_Installation|InContext Server]] - InContext Server manages the resources identified by InContext Capture. | ||
Revision as of 20:37, 3 April 2019
Overview
The InContext Translation process:
- Base and target resource files are instrumented by LRM and pushed to the code repository.
- The instrumented resource files are deployed in a test build of the web application.
- Using a Chrome browser extension, InContext Capture, the resource files and their context are captured and stored at the InContext Server (which may reside on the Lingoport Server).
- LRM sends the resource files with their context to the TMS.
Installation
InContext Translation is made up of three components that must be installed:
- InContext LRM Intrumentation - The first thing to do is verify that you are using an LRM version and license for InContext Translation.
- InContext Capture - InContext Capture uses a Chrome extension to identify application resources and send the text and context to the InContext Server.
- InContext Server - InContext Server manages the resources identified by InContext Capture.