locize will help to keep your translations free of issues and inconsistencies by performing checks. On this page, you will find a list of possible issues and how to solve them.
The global view will only show that there is a warning/error on a specific key for details you will have to follow the link into the focus view and check the right-hand column:
You can use the icon button with the eye symbol to ignore an error.
Generally ignoring checks
You have also the possibility to generally ignore specific checks.
You can do so by going to your project settings page in the Control Center view and selecting the "SET ISSUES TO IGNORE" menu item in the extensions card.
Check translation memory consistency
As this check is very performance intensive you will have to trigger this check manually.
issue 220 - not consistent with the translation memory
This issue tells you that we found another translation inside the translation memory that was translated differently. You got the option to change the translation to be consistent or to ignore this issue as you prefer having this inconsistency.
Check exists in the source language
issue 301 - is not found in the source language
The key was only imported into a target language. It is recommended to add the content in the source language, too.
This may also result in having your translation statistics not to show the expected percentage of translated segments.
Check if the translation is up to date
issue 302 - the content in the source language changed after translating to this target language
There was a change to the source content. The translation might be outdated, wrong – time to check if the provided translation is still valid.
If the translation is still valid, you can confirm it in the focus view:
Do not forget to click the SAVE button, after having clicked CONFIRM.
Check max characters length
issue 310 - is longer than the defined max characters
In the source language is a defined max length for this sentence and the provided translation is too long.
issue 420 - gets nested into another string
This issue exists if there is a key eg. key.nested that would be nested into another key key. The result in a JSON export would then be:
So you would lose one of the keys in your export. To solve this issue rename one of the keys.
Check array size
issue 430 - check for array issue
The key is in form key.10001 which leads to exporting as an array (eg. in the JSON format). Having such a key would result in the creation of an array with the given number. This check asserts array sizes stay in a limited size (below 100).
You can avoid the conversion of the content to an array by providing a key that has a non-numeric end like key.aString.