LocalyzerQA
Contents
Introduction
Linguistic Review Made Easy
Lingoport Localyzer facilitates the process of translating resource file (properties, resx, json, etc.). LocalyzerQA is focused on the Linguistic Review process of a running application with translations. A Linguistic Reviewer may be a application specialist who is native in a language, an in-country in-company person, a member of a localization team, a member of a translation team.
Without LocalyzerQA, the linguist review process tends to be cumbersome. For example, Linguistic Reviewers may navigate the application based on an email sent by the dev team, then when finding an issue screen shot the page, highlight the text to be corrected, open a defect in a bug tracking system, assign it to a manager who will then have to find which team/dev/repository that may belong to, have a developer (who is busy with feature development) figure out where the error is located for a string in a language they most likely don't speak and may not even read (think Chinese or Japanese for an English speaker), send the file with a correction via email to a language service provider; The language service provider team then needs to handle that retranslation, start a workflow, assign that correction, return the correction, send the correction some time later back to the dev team (which may be busy with some other tasks), figure from the email where to push the file back, and finally have a correction in the repo. This tends to take days.
With LocalyzerQA, this process takes minutes and does not involve developers.
Localyzer Trackback locale
Localyzer creates trackback files for a configured locales, by default 'ia' or Interlingua. (The reason for this default locale is that most browsers support interlingua and interlingua is not an actual market locale for typical application. The trackback files contain a key and the original source text. The key allows the system to identify the resource in a repository, branch, resource files on-boarded in Localyzer.
For example, if, for a UI label, the original messages.properties files contains
welcome.title=Welcome
a typical translated file, say French, would have the translated messages_fr.properties file with
welcome.title=Bienvenue
and the trackback file messages_ia.properties would have
welcome.title=143.9278 Welcome
The UI label would display:
- Welcome when the locale is set to English,
- Bienvenue when the locale is set to French,
- 143.9278 Welcome when the locale is set to Interlingua
Post Editing
A manager will set up a review for an application with a set of directives for all target locales. A linguist following the directions and will switch back and forth between their target locale (say French) and the trackback locale (say Interlingua). If the target locale needs post editing, the trackback key will be used to fill in the post edit key field.
