Difference between revisions of "Localyzer Resource File Comments"

From Lingoport Wiki
Jump to: navigation, search
(Created page with " = Localyzer Comments Overview = Localyzer uses a set of comments, either in the repository files for retranslation requests, or to resource files when sending them for transl...")
 
Line 21: Line 21:
   
 
Example of a Context tag, here for a <code>.properties</code> file:
 
Example of a Context tag, here for a <code>.properties</code> file:
  +
<!--LRM_INCONTEXT https://fs-incontext.lingoport.io/incontext-server/lookup?token=4h23984Rh5JLWhn79tS12UJauH71XV7J9R&key=3015_41-->
  +
<data name="DELIVERED" xml:space="preserve"><value>Delivered</value></data>
  +
  +
The key/value pair here is <code> <data name="DELIVERED" xml:space="preserve"><value>Delivered</value></data> </code>

Revision as of 19:26, 30 June 2021

Localyzer Comments Overview

Localyzer uses a set of comments, either in the repository files for retranslation requests, or to resource files when sending them for translation. The three types of comments are:

  • A Localyzer Project tag at the top of the file
  • A Localyzer Context tag above a key value pair
  • A Localyzer Retranslation tag above a key value pair

Localyzer Project Tag

A project tag is created as a comment and added when sending a file for translation. It indicates if the file is a full file or a delta, the Localyzer project, the target locale, and the kit number. This tag must not be modified when returning the translated file. The translation validation process uses the tag for some of its internal checks.

Example of the project tag, here in a .json file:

   "_LRM_PKTAG636": "RawClipped_5_97 - CHANGES-ONLY"
  • _LRM_PKTAG636: Indicates an Localyzer tag.
  • RawClipped: The name of the Localyzer project.
  • 5: the kit version, here the 5th time files for the RawClipped project are sent to translation
  • 97: the internal language identifier, here Japanese/Japan

Localyzer Context Tag

When Localyzer is configured to work with InContext Translation, the system creates a tag as a comment above each resource key/value pair when sending the file to translation. The tag includes a URL pointing to a context held by the Lingoport Context server.

Example of a Context tag, here for a .properties file:

   <value>Delivered</value>

The key/value pair here is <value>Delivered</value>