LRM Source Translation Checks: Difference between revisions

From Lingoport Wiki
Jump to navigation Jump to search
← Older edit
No edit summary
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
LRM checks against the translated files in the local repository.
LRM checks against the '''translated files''' in the local repository. It also compares each translated file against its corresponding base resource file.


===LRM Translation Duplicate Key Check===
See [[LRM_Checks|''Localyzer Checks'']] for additional checks.
* This translated file already contains this key
===NON_BASE_DATE_FORMAT_VALUE LRM Source Translation Date Format Check===
===LRM Translation Empty Key Check===
* The text associated with this key may be a date format, as per the Java date format possibilities: See https://docs.oracle.com/javase/8/docs/api/java/text/SimpleDateFormat.html
* a key/value pair is missing the key portion in the translated file to be imported, making the text irretrievable by the application.
 
'''LRM Translation Encoding Check'''
===NON_BASE_DNT_MISMATCH LRM Source Translation DNT Key Check===
* This translated file has an incorrect encoding or, if an xml file, the prolog may be missing
* A segment (string value) in the translated file has a translation when the string is marked DNT. Strings marked as DNT must not be translated.
'''LRM Translation File Already Processed Check'''
===NONBASE_DUPLICATE_KEY LRM Source Translation Duplicate Key Check===
* This file has already been processed for this kit
* The identifier/key already exists in this translated file in the source directory
'''LRM Translation File Too Big Check'''
===NONBASE_EMPTY_VALUE LRM Source Translation Empty Key in Translated File Check===
* This translated file exceeds the maximum size supported by the Lingoport Resource Manager
* a key/value pair is missing the key portion in the translated file in the source, making the text irretrievable by the application.
'''LRM Translation ICU Argument Mismatch Check'''
===NONBASE_ENCODING LRM Source Translation Encoding Check===
* The translation does not contain the same ICU arguments as the base resource. Check the plural and/or select arguments. See http://userguide.icu-project.org/formatparse/messages for formatting examples.
* This file's encoding is incorrect in the translated file in the source directory or, if an xml file, the prolog may be missing
'''LRM Translation ICU MessageFormat Check'''
===NONBASE_FILE_TOO_BIG LRM Source Translation File Too Big Check===
* The structure of the message is incorrect potentially due to the locale of the file. See http://userguide.icu-project.org/formatparse/messages for formatting examples. See http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for locale plural rules. In addition, if the ICU MessageFormat contains parameters, then the parameters must match. See below for information about the ''Parameter Mismatch Check''
* This translated resource file exceeds the maximum size supported by the Lingoport Resource Manager
'''LRM Translation Missed Translation Check'''
===NONBASE_HTML_VALUE LRM Source Translation HTML Check===
* The translation is missing for this text
* There is HTML in the text associated with this key
'''LRM Translation Missing File Check'''
===NONBASE_ICU_MSGFORMAT_AND_TEXT LRM Source Translation ICU Argument Mismatch Check===
* The translated file is missing from the kit to import
* The translation does not contain the same ICU arguments as the base resource. Check the plural and/or select arguments. See https://unicode-org.github.io/icu/userguide/format_parse/messages for formatting examples. In addition, if the ICU MessageFormat contains parameters, then the parameters must match. See [[LRM_Import_Checks#LRM_Translation_Parameter_Mismatch_Check|Parameter Mismatch Check]]
'''LRM Translation Missing Key Check'''
 
* The identifier/key is missing in the translated file.
===NONBASE_ICU_MISMATCH LRM Source Translation ICU MessageFormat Check===
'''LRM Translation Missing or Invalid Tag Check'''
* The structure of the message is incorrect potentially due to the locale of the file. See https://unicode-org.github.io/icu/userguide/format_parse/messages for formatting examples. See http://cldr.unicode.org/index/cldr-spec/plural-rules for locale plural rules
* LRM cannot process a translated file if the LRM Tag is corrupted (see top of file)
===NONBASE_MISSED_TRANSLATION LRM Source Translation Missed Translation Check===
'''LRM Translation No Text Check'''
* This text is not translated in the source directory
* This resource key/identifier is missing in the translated text
===NONBASE_MISSING_FILE LRM Source Translation Missing File Check===
'''LRM Translation Parameter Mismatch Check'''
* This translated file is missing and the LRM project configuration calls for this locale
* The import kit's file parameters do not match the prep kit's source file parameters. Possible reasons:
===NONBASE_MISSING_KEY LRM Source Translation Missing Key Check===
**Translator translated the parameter. For example, if the base resource file has {car} defined as a parameter but the translated French file has {voiture} then a parameter mismatch error will occur. The translator will need to fix this issue by not translating the parameter.
* The identifier/key is missing in the translated file in source
**Issue with single ticks surrounding a parameter with curly brackets.
===NONBASE_MISSED_TRANSLATION LRM Source Translation No Text Check===
***''''{0}'''' - if there are single ticks surrounding the curly brackets then this means that the curly brackets do '''not''' represent a parameter. The single tick is used as a special character indicating that the curly bracket is a displayable character. So, if the base resource file has '''{0}''' and the imported file has ''"{0}"'' then a parameter mismatch will occur because '''{0}''' is '''not''' a parameter while ''"{0}"'' is a parameter.
* The text is missing from the translated file in source
'''LRM Translation Source Location Not Found Check'''
===NONBASE_PARAM_MISMATCH LRM Source Translation Parameter Mismatch Check===
* The source location cannot be found and this file cannot be imported to its source location
* The translated resource parameters do not match the base resource parameters. See [[LRM_Import_Checks#LRM_Translation_Parameter_Mismatch_Check|Pararmeter Mismatch Check]] for more information.
'''LRM Translation Unknown Error Check'''
 
* There is an error in the import kit file and LRM cannot identify its source
===NONBASE_RETRANSLATE_TEXT LRM Source Translation Retranslate Check===
'''LRM Translation Unknown File/Line Format Check'''
* This text needs to be retranslated for the translated resource file.
===NONBASE_UNKNOWN_ERROR LRM Source Translation Unknown Error Check===
* There is an error in the translated source file and LRM cannot identify its source
===NONBASE_UNKNOWN_FILE_FORMAT LRM Source Translation Unknown File/Line Format Check===
* Unknown format for file/line or empty file (no key/values found) - The translated file/line could not be parsed
* Unknown format for file/line or empty file (no key/values found) - The translated file/line could not be parsed
'''LRM Translation Non-Writable File Check'''
* LRM cannot import the file to the source directory

Latest revision as of 19:21, 3 April 2026

LRM checks against the translated files in the local repository. It also compares each translated file against its corresponding base resource file.

See Localyzer Checks for additional checks.

NON_BASE_DATE_FORMAT_VALUE LRM Source Translation Date Format Check

NON_BASE_DNT_MISMATCH LRM Source Translation DNT Key Check

  • A segment (string value) in the translated file has a translation when the string is marked DNT. Strings marked as DNT must not be translated.

NONBASE_DUPLICATE_KEY LRM Source Translation Duplicate Key Check

  • The identifier/key already exists in this translated file in the source directory

NONBASE_EMPTY_VALUE LRM Source Translation Empty Key in Translated File Check

  • a key/value pair is missing the key portion in the translated file in the source, making the text irretrievable by the application.

NONBASE_ENCODING LRM Source Translation Encoding Check

  • This file's encoding is incorrect in the translated file in the source directory or, if an xml file, the prolog may be missing

NONBASE_FILE_TOO_BIG LRM Source Translation File Too Big Check

  • This translated resource file exceeds the maximum size supported by the Lingoport Resource Manager

NONBASE_HTML_VALUE LRM Source Translation HTML Check

  • There is HTML in the text associated with this key

NONBASE_ICU_MSGFORMAT_AND_TEXT LRM Source Translation ICU Argument Mismatch Check

NONBASE_ICU_MISMATCH LRM Source Translation ICU MessageFormat Check

NONBASE_MISSED_TRANSLATION LRM Source Translation Missed Translation Check

  • This text is not translated in the source directory

NONBASE_MISSING_FILE LRM Source Translation Missing File Check

  • This translated file is missing and the LRM project configuration calls for this locale

NONBASE_MISSING_KEY LRM Source Translation Missing Key Check

  • The identifier/key is missing in the translated file in source

NONBASE_MISSED_TRANSLATION LRM Source Translation No Text Check

  • The text is missing from the translated file in source

NONBASE_PARAM_MISMATCH LRM Source Translation Parameter Mismatch Check

  • The translated resource parameters do not match the base resource parameters. See Pararmeter Mismatch Check for more information.

NONBASE_RETRANSLATE_TEXT LRM Source Translation Retranslate Check

  • This text needs to be retranslated for the translated resource file.

NONBASE_UNKNOWN_ERROR LRM Source Translation Unknown Error Check

  • There is an error in the translated source file and LRM cannot identify its source

NONBASE_UNKNOWN_FILE_FORMAT LRM Source Translation Unknown File/Line Format Check

  • Unknown format for file/line or empty file (no key/values found) - The translated file/line could not be parsed
Retrieved from "https://wiki.lingoport.com/index.php?title=LRM_Source_Translation_Checks&oldid=99874"