Difference between revisions of "Localyzer Checks"
(→LRM Detections) |
m (Olibouban moved page LRM Checks to Localyzer Checks) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Introduction = |
= Introduction = |
||
| − | When |
+ | When Localyzer issues are displayed on Command Center, they are displayed with short descriptor. For example: |
| − | [[File: |
+ | [[File:Localyzer Issues.png|750px]] |
| − | |||
| − | To see the context of the issue, select the '''<code>></code>''' in the box. The file will open at the point of the issue: |
||
| − | |||
| − | [[File: IssueInCode.jpg |750px]] |
||
= Localyzer Detections = |
= Localyzer Detections = |
||
Latest revision as of 19:45, 12 March 2026
Introduction
When Localyzer issues are displayed on Command Center, they are displayed with short descriptor. For example:
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
