Difference between revisions of "InContext Translation Installation"

From Lingoport Wiki
Jump to: navigation, search
(InContext Integration with TMSs)
 
(5 intermediate revisions by 2 users not shown)
Line 4: Line 4:
   
 
The InContext Translation process:
 
The InContext Translation process:
#Base and target resource files are instrumented by LRM and pushed to the code repository.
+
#Base and target resource files are instrumented by Localyzer and pushed to the code repository.
 
#The instrumented resource files are deployed in a test build of the web application.
 
#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).
 
#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.
+
#Localyzer sends the resource files with their context to the TMS.
   
 
=Installation=
 
=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 Instrumentation]] - The first thing to do is verify that you are using an LRM version and license for InContext Translation.
+
* [[Localyzer Instrumentation | InContext Localyzer Instrumentation]] - The first thing to do is verify that you are using an Localyzer version and license for InContext Translation.
 
* [[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=
 
=InContext Integration with TMSs=
  +
* [[Lingoport_InContext_Plugin_for_Trados_Studio | Lingoport InContext Plugin for Trados Studio]]
* [[Trados_Integration | SDL Trados Studio]] - Lingoport InContext Plugin
 

Latest revision as of 20:31, 23 February 2021

Overview

Lingoport incontext translation.png

The InContext Translation process:

  1. Base and target resource files are instrumented by Localyzer 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. Localyzer sends the resource files with their context to the TMS.

Installation

InContext Translation is made up of three components that must be installed:

  • InContext Localyzer Instrumentation - The first thing to do is verify that you are using an Localyzer 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