Difference between revisions of "LRM Checks"
(→LRM Detections) |
(→LRM Detections) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 9: | Line 9: | ||
[[File: IssueInCode.jpg |750px]] |
[[File: IssueInCode.jpg |750px]] |
||
| − | = |
+ | = Localyzer Detections = |
| − | + | Localyzer detections are split into three categories: |
|
#'''Source Base Checks''' - applied to base resource files in the source. The base resource file is generally the English file, so these issues will be on these files. See [[LRM_Source_Base_Checks|Source Base Checks]] for more information. |
#'''Source Base Checks''' - applied to base resource files in the source. The base resource file is generally the English file, so these issues will be on these files. See [[LRM_Source_Base_Checks|Source Base Checks]] for more information. |
||
#'''Source Translation Checks''' - applied to translation resource files in the source. These are the files that have been translated and returned. For example, if the base file is <code>resources_en_US.json</code>, the translated file, for French, now in the source code is <code>resources_fr_FR.json</code>. See [[LRM_Source_Translation_Checks|Source Translation Base Checks]] for more information. |
#'''Source Translation Checks''' - applied to translation resource files in the source. These are the files that have been translated and returned. For example, if the base file is <code>resources_en_US.json</code>, the translated file, for French, now in the source code is <code>resources_fr_FR.json</code>. See [[LRM_Source_Translation_Checks|Source Translation Base Checks]] for more information. |
||
#'''Translation Checks''' - applied to returned translation files. These are the files that are coming back from translation and there are some problems created during translation that is causing an issue. See [[LRM_Import_Checks#LRM_Translation_Checks|Import Checks]] |
#'''Translation Checks''' - applied to returned translation files. These are the files that are coming back from translation and there are some problems created during translation that is causing an issue. See [[LRM_Import_Checks#LRM_Translation_Checks|Import Checks]] |
||
| − | |||
| − | |||
| − | == Source Translation Checks == |
||
| − | Checks against translation resource files in the source. |
||
| − | |||
| − | '''LRM Source Translation Date Format Check''' |
||
| − | * The text associated with this key may be a date format |
||
| − | '''LRM Source Translation Duplicate Key Check''' |
||
| − | * The identifier/key already exists in this translated file in the source directory |
||
| − | '''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. |
||
| − | '''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 |
||
| − | '''LRM Source Translation File Too Big Check''' |
||
| − | * This translated resource file exceeds the maximum size supported by the Lingoport Resource Manager |
||
| − | '''LRM Source Translation HTML Check''' |
||
| − | * There is HTML in the text associated with this key |
||
| − | '''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. |
||
| − | '''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 |
||
| − | '''LRM Source Translation Missed Translation Check''' |
||
| − | * This text is not translated in the source directory |
||
| − | '''LRM Source Translation Missing File Check''' |
||
| − | * This translated file is missing and the LRM project configuration calls for this locale |
||
| − | '''LRM Source Translation Missing Key Check''' |
||
| − | * The identifier/key is missing in the translated file in source |
||
| − | '''LRM Source Translation No Text Check''' |
||
| − | * The text is missing from the translated file in source |
||
| − | '''LRM Source Translation Parameter Mismatch Check''' |
||
| − | * The translated resource parameters do not match the base resource parameters |
||
| − | '''LRM Source Translation Retranslate Check''' |
||
| − | * This text needs to be retranslated for the translated resource file. |
||
| − | '''LRM Source Translation Unknown Error Check''' |
||
| − | * There is an error in the translated source file and LRM cannot identify its source |
||
| − | '''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 |
||
Latest revision as of 21:10, 29 April 2022
Introduction
When LRM issues are displayed on the Dashboard, they are displayed with short descriptor. For example:
To see the context of the issue, select the > in the box. The file will open at the point of the issue:
Localyzer Detections
Localyzer detections are split into three categories:
- Source Base Checks - applied to base resource files in the source. The base resource file is generally the English file, so these issues will be on these files. See Source Base Checks for more information.
- Source Translation Checks - applied to translation resource files in the source. These are the files that have been translated and returned. For example, if the base file is
resources_en_US.json, the translated file, for French, now in the source code isresources_fr_FR.json. See Source Translation Base Checks for more information. - Translation Checks - applied to returned translation files. These are the files that are coming back from translation and there are some problems created during translation that is causing an issue. See Import Checks
