Difference between revisions of "InContext Translation Installation"

From Lingoport Wiki
Jump to: navigation, search
(Installation)
Line 14: Line 14:
 
* [[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.
 
* [[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 Integration with TMSs=
  +
* [[Trados_Integration | SDL Trados Studio]] - SDL Trados Studio InContext Plugin

Revision as of 18:50, 30 September 2019

Overview

Lingoport incontext translation.png

The InContext Translation process:

  1. Base and target resource files are instrumented by LRM and pushed to the code repository.
  2. The instrumented resource files are deployed in a test build of the web application.
  3. 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).
  4. 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 Instrumentation - The first thing to do is verify that you are using an LRM version and license for InContext Translation.
  • InContext Server - InContext Server manages the resources identified by InContext Capture.
  • InContext Capture - InContext Capture uses a Chrome extension to identify application resources and send the text and context to the InContext Server.

InContext Integration with TMSs