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:
Besides running the checks for one segment in the focus view you have to run all checks using the following button:
You can use the icon button with the eye symbol to ignore an error.
You have also the possibility to generally ignore specific checks. You can do so by navigating to your project settings page, in the "EDITOR, TM/MT, ORDERING" tab and clicking the "Issues to ignore" section in the "Cat settings" card.
As this check is very performance intensive you will have to trigger this check manually.
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.
As this check is rather performance intensive you will have to trigger this check manually. This check will only work if you uploaded a glossary file in your settings page.
The translation contains a term that was set as forbidden in the glossary provided for this project.
The segment appears to match a glossary entry in the source language, but no allowed term was used in the translation in the target language.
This check will compare source and target translations for containing same i18n syntax features (depending on set i18n format).
The translation contains a different number of i18n syntax used, eg. interpolation, nesting, ....
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.
There was a change to the source content. The translation might be outdated, wrong – time to check if the provided translation is still valid.
In the source language is a defined max length for this sentence and the provided translation is too long.
This issue exists if there is a key eg.
key.nestedthat 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.
The key is in form
key.10001which 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