About InContext QA: Difference between revisions

From Lingoport Wiki
Jump to navigation Jump to search
Rdaly (talk | contribs)
Rdaly (talk | contribs)
Line 8: Line 8:


= Benefits =
= Benefits =
*Strings to review in context: live Web app
* Strings to review are in context. They are on a live Web app so reviewers can see strings in the context they are presented.
* No software developer involvement
* There is no software developer involvement, freeing up developers from the localization process
* Easy, direct interaction from reviewer
* Easy, direct interaction from reviewer to localization group.
* Automatic updates
* Automatic updates
* Light, minimal learning curve
* Light, minimal learning curve for reviewers.
* Non-intrusive
* Non-intrusive, no changes to the code and web apps can be deployed while being reviewed.


= System Overview =
= System Overview =

Revision as of 16:58, 29 June 2018

High Level Goals

The Lingoport InContext QA goals are:

  • Facilitate the translation review process of internationalized applications
  • Provide a simple way to review and edit translations of an application’s string resources in Chrome

The following is not a goal of Lingoport InContext QA:

  • Lingoport InContext QA does not replace how translation is done: It is not a translation management system (TMS) and not pretending to be one.

Benefits

  • Strings to review are in context. They are on a live Web app so reviewers can see strings in the context they are presented.
  • There is no software developer involvement, freeing up developers from the localization process
  • Easy, direct interaction from reviewer to localization group.
  • Automatic updates
  • Light, minimal learning curve for reviewers.
  • Non-intrusive, no changes to the code and web apps can be deployed while being reviewed.

System Overview

For an on-boarded repository, the happy path looks like:

  • Resource files are analyzed by Lingoport Resource Manager (LRM) and displayed in the Dashboard
  • Resource files which need to be translated are sent to the Translation Group
  • Translated resource files are received by LRM and pushed to the repo
  • Translated resource files are instrumented
  • The application with instrumented resource files are deployed to a Linguistic QA server
  • The reviewers navigate to the deployed instrumented application
  • The reviewers submit suggestions which are captured by LRM
  • LRM handles the retranslation requests and deals with the book keeping, the automation, the metrics, etc.