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 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 is resources_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

@@ Line 9: / Line 9: @@
 [[File: IssueInCode.jpg |750px]]
-= LRM Detections =
+= Localyzer Detections =
-LRM detections are split into three categories:
+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 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.