InContext Translation Release notes

For supported versions, please see: Lingoport_Suite_Installation#Supported_Versions

InContext Server 2.0.7 ( June 2025

• Now serving files [8926, 8922, 8923, 8924] captured from
  • the Google Chrome extension for Webapp
  • the Figma context
  • the screenshot association

InContext Server 1.2.0 - June 2022

• Upgraded Tomcat version to 8.5.78
• Updated from MySQL connector to MariaDB connector

InContext Server 1.0.0 - May 2019

This release introduces Web application context support for TMS/CAT tools.

InContext Translation is a new add-on to Localyzer. 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:

• Localyzer: For InContext Translation, Localyzer instrument files that are then pushed to the associated repository and must be 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. Localyzer 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. TMS/CAT tools can then parse the comments for each key/value pair and display the context of each application segment to translate.

• 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.

• Lingoport InContext Server: The InContext Server receives the context from the Chrome Capture extension and serves the context from the TMS/CAT tools as sent as decoration in resource files by Localyzer.