Radialix 2 helps the user to check localization for errors to find common errors that may appear after editing resources.

The program can check translation for errors automatically as you edit values, before creating localized files. You can also start translation check manually. To check selected resources for errors, press <Ctrl + F9>, or use the command from the context menu.

The listing of found errors is displayed in the error panel. A double click on the error message takes the user to the resource error. Some errors can be fixed automatically by using the Fix Error(s) option in the context menu of this panel.

The translation check settings are stored in the properties of a project and edited in the Project Properties dialog.

The program supports the following options to check localization for errors:

• Ignore error if it appears in source resources – the option to ignore recurring errors. The option does not work for some checks.
• Do not check items with status Deleted – this option disables the check of deleted items.
• Inconsistent printf specifiers – the list of printf parameters in a translated string does not match the list of parameters in a source string.
• Inconsistent FormatMessage specifiers – the list of the FormatMessage parameters in a translated string does not match the list of these parameters in a source string.
• Invalid symbol(s) – a translated string contains a symbol, which is missing in the codepage of a target language.
• Missing symbol(s) – required symbol is missing.
• Empty target string, but source is not empty
• Source is empty, but target is not empty
• Inconsistent Tabulators – inconsistent number of tabulators in translated and source strings.
• Inconsistent spaces in the beginning or in the end of string.
• Spell checking errors – a word is entered incorrectly, or missing in the spell-checker dictionary
• Text too long – length of text exceeds the specified maximal length. The maximal length of a string is defined in the Object Inspector.
• Missing AccelKey in target string
• No AccelKey in source string, but target string has
• Invalid AccelKey – invalid key combination.
• Duplication of AccelKey in menu.
• Duplication of AccelKey in dialog/form
• Text doesn’t fit in control – text does not fit in a control. The check of text length is simplified. Sometimes such errors are not detected, or detected by mistake.
• Control overlaps – controls overlap each other.
• Control is out of parent control.
• Invalid accelerator – incorrect indication or invalid combination of keys in an accelerator indication.
• Duplication of accelerator.
• Invalid image – these images are missing, or have an invalid format.
• Size of target image is not equal the size of source one.
• Inconsistent image formats.
• Before creating targets – check all translated resources before generating localized files.
• When item changed – check the resource after editing, auto-translation, import, insertion from the clipboard, etc.
• After project loading – check the project after loading.

TM files have their own settings to check translation for errors. They can be edited from the menu of the Tools button in the TM editor panel.