Difference between revisions of "LocalyzerQA"

From Lingoport Wiki
Jump to: navigation, search
(Handling Errors)
(Introduction)
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
   
 
== Introduction ==
 
== Introduction ==
  +
=== 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
  +
<code>welcome.title=Welcome</code>
  +
  +
a typical translated file, say French, would have the translated messages_fr.properties file with
  +
<code>welcome.title=Bienvenue</code>
  +
  +
and the trackback file messages_ia.properties would have
  +
<code>welcome.title=143.9278 Welcome</code>
  +
  +
The UI label would display:
  +
* <b>Welcome</b> when the locale is set to ''English'',
  +
* <b>Bienvenue</b> when the locale is set to ''French'',
  +
* <b>143.9278 Welcome</b> 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.
   
 
== Handling Errors ==
 
== Handling Errors ==
Line 7: Line 26:
 
* [[LocalyzerQAInvalidLocale]]
 
* [[LocalyzerQAInvalidLocale]]
 
* [[LocalyzerQAInvalidKey]]
 
* [[LocalyzerQAInvalidKey]]
  +
* [[LocalyzerQAEncodingError]]
  +
* [[LocalyzerQANotFoundParameter]]
  +
* [[LocalyzerQAUnknowError]]
  +
* [[LocalyzerQANotFound]]
  +
* [[LocalyzerQAIcuMsgformatError]]
  +
* [[LocalyzerQAUnknowFormatError]]
  +
* [[LocalyzerQAFileTooBig]]
  +
* [[LocalyzerQANonWritableFile]]

Revision as of 15:55, 9 December 2020

Introduction

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.

Handling Errors