LRM Import Checks
Contents
- 1 LRM Translation Checks
- 1.1 LRM Translation Duplicate Key Check
- 1.2 LRM Translation Empty Key Check
- 1.3 LRM Translation Encoding Check
- 1.4 LRM Translation File Already Processed Check
- 1.5 LRM Translation File Too Big Check
- 1.6 LRM Translation ICU Argument Mismatch Check
- 1.7 LRM Translation ICU MessageFormat Check
- 1.8 LRM Translation Missed Translation Check
- 1.9 LRM Translation Missing File Check
- 1.10 LRM Translation Missing Key Check
- 1.11 LRM Translation Missing or Invalid Tag Check
- 1.12 LRM Translation No Text Check
- 1.13 LRM Translation Parameter Mismatch Check
- 1.14 LRM Translation Source Location Not Found Check
- 1.15 LRM Translation Unknown Error Check
- 1.16 LRM Translation Unknown File/Line Format Check
- 1.17 LRM Translation Non-Writable File Check
LRM Translation 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
- 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. In addition, if the ICU MessageFormat contains parameters, then the parameters must match. See Parameter Mismatch Check
LRM Translation ICU MessageFormat 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.
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. 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.
LRM Translation Source Location Not Found Check
- The source location cannot be found and this file cannot be imported to its source location
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
