Difference between revisions of "InContext Translation Release notes"

From Lingoport Wiki
Jump to: navigation, search
(Lingoport InContext Translation 1.0 Release Notes - April 2019)
Line 3: Line 3:
 
</p>
 
</p>
 
<p>
 
<p>
  +
InContext Translation is a new add-on to LRM. Its aim is to support TMS/CAT tools with a viewable context for translators for strings in resource files, such as properties and resx files.
  +
InContext Translation uses three components:
  +
* LRM: For InContext Translation, LRM instrument files that are then pushed to the associated repository and deployed to a server dedicated to InContext Translation: The application running in Chrome will be the basis for to capture the context of the application. LRM also sends resource files with decorations, i.e. comments that point back to a URL for the context of each key/value pair in a resource file.
   
* '''Introducing Lingoport InContext Translation''': The aim of InContext Translation is to provide the translator with a view of the application where the string is located.
+
* '''InContext Translation Capture''': A Google Chrome extension which can automatically capture strings displayed when navigating to the instrumented application (see above) and their associated context and send them to the InContext Server.
   
* '''InContext Translation Capture''': A Google Chrome extension which can automatically capture strings and their associated context and send them to the InContext Server.
+
* '''Introducing Lingoport InContext Translation''': The aim of InContext Translation is to provide the translator with a view of the application where the string is located. It receives the context from the Chrome Capture extension and serves the context from the TMS/CAT tools.

Revision as of 17:06, 23 April 2019

Lingoport InContext Translation 1.0 Release Notes - April 2019

This release provides the following new features:

InContext Translation is a new add-on to LRM. Its aim is to support TMS/CAT tools with a viewable context for translators for strings in resource files, such as properties and resx files. InContext Translation uses three components:

  • LRM: For InContext Translation, LRM instrument files that are then pushed to the associated repository and deployed to a server dedicated to InContext Translation: The application running in Chrome will be the basis for to capture the context of the application. LRM also sends resource files with decorations, i.e. comments that point back to a URL for the context of each key/value pair in a resource file.
  • InContext Translation Capture: A Google Chrome extension which can automatically capture strings displayed when navigating to the instrumented application (see above) and their associated context and send them to the InContext Server.
  • Introducing Lingoport InContext Translation: The aim of InContext Translation is to provide the translator with a view of the application where the string is located. It receives the context from the Chrome Capture extension and serves the context from the TMS/CAT tools.