LRM Source Translation Checks

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

• 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

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

• 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 Parameter Mismatch Check

NONBASE_ICU_MISMATCH LRM Source Translation ICU MessageFormat 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

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