Difference between revisions of "LocalyzerQANotFound"

From Lingoport Wiki
Jump to: navigation, search
(Created page with "== Error #4: Not Found == == Possible Corrective Action == == List of Errors ==")
 
(Possible Corrective Action)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Error #4: Not Found ==
 
== Error #4: Not Found ==
  +
This error occurs when the translation to correct is not found based on the key for that locale. For example, if the text in French is "Viens" in the resource file but the ''Current'' entry from LocalyzerQA is "Vient", the Not Found error will occur.
   
 
== Possible Corrective Action ==
 
== Possible Corrective Action ==
  +
To re-use some of the input, click in the PostEdit on the error, then click on the '''Send to Task''' link. That will move that entry in the Review list.
  +
  +
* Verify the spelling of the current text.
  +
* Make sure the key is indeed the correct one for the text and not for another string.
  +
* More rarely, the resource file may contain some characters which show up in the application but are encoded differently. For example, a non-breaking space in UTF-8 in the resource file (302 240) may show up in the application like any other space.
   
 
== List of Errors ==
 
== List of Errors ==
  +
* [[LocalyzerQA#Handling_Errors|LocalyzerQA Error List]]

Latest revision as of 18:10, 15 March 2021

Error #4: Not Found

This error occurs when the translation to correct is not found based on the key for that locale. For example, if the text in French is "Viens" in the resource file but the Current entry from LocalyzerQA is "Vient", the Not Found error will occur.

Possible Corrective Action

To re-use some of the input, click in the PostEdit on the error, then click on the Send to Task link. That will move that entry in the Review list.

  • Verify the spelling of the current text.
  • Make sure the key is indeed the correct one for the text and not for another string.
  • More rarely, the resource file may contain some characters which show up in the application but are encoded differently. For example, a non-breaking space in UTF-8 in the resource file (302 240) may show up in the application like any other space.

List of Errors