LRM Import Checks

From Lingoport Wiki
Revision as of 21:07, 29 April 2022 by Llawson (talk | contribs) (LRM Translation Parameter Mismatch Check)
Jump to: navigation, search

LRM Translation Checks

These checks occur during the import process. The import file is checked for errors and then compared against its corresponding base resource file.

See Localyzer Checks for additional checks.

LRM Translation Duplicate Key Check

  • This translated file already contains this key

LRM Translation Empty Key Check

  • 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

  • This translated file has an incorrect encoding or, if an xml file, the prolog may be missing

LRM Translation File Already Processed Check

  • This file has already been processed for this kit

LRM Translation File Too Big Check

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

LRM Translation ICU Argument Mismatch Check

LRM Translation ICU MessageFormat Check

LRM Translation Missed Translation Check

  • The translation is missing for this text

LRM Translation Missing File Check

  • The translated file is missing from the kit to import

LRM Translation Missing Key Check

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

LRM Translation Missing or Invalid Tag Check

  • LRM cannot process a translated file if the LRM Tag is corrupted (see top of file)

LRM Translation No Text Check

  • This resource key/identifier is missing in the translated text

LRM Translation Parameter Mismatch Check

  • The import kit's file parameters do not match the prep kit's source file parameters. The parameter regex pattern is defined in the project. Possible reasons:
    • 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.
    • Issue with single ticks surrounding a parameter with curly brackets.
      • '{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. Parameter mismatch will also occur if the opposite occurs (base resource file has "{0}" and the imported file has '{0}')
    • Number of parameters must match. For example, if the base resource file has 2 {0} parameters then the file that is to be imported must have 2 {0} parameters.

LRM Translation Source Location Not Found Check

  • The source location cannot be found and this file cannot be imported to its source location. This occurs when the repository structure has changed after the kit was prepped and the location for the imported file no longer exists. In addition, if the translated file in the local repository no longer exists and the import file is for changes only, then this error will occur.

LRM Translation Unknown Error Check

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

LRM 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

LRM Translation Non-Writable File Check

  • LRM cannot import the file to the source directory