Localizability Testing

Before you pay for translation, check that the application can be localized: all user-visible text comes from resources, longer text fits, and the application displays characters of other languages.

Pseudo-translate the application

Choose Project > Translate Using > Pseudo Translate.
Select how to change the text: replace characters with similar characters of other alphabets, add characters before and after each string, and expand the text by a percentage. The preview in the dialog shows the result.
Create the localized files and run the application with Project > Run Localized Application.

Text that is still in the original language is not in the resources Lingobit Localizer translates. Text that is cut off or overlaps other controls needs more space. Broken or missing characters mean the application or its fonts do not support them. See Pseudo Translate.

Pseudo-translations get the Auto status. Delete them before the real translation with Delete Translations in the shortcut menu of the Navigation pane, or pseudo-translate a separate test language.

Try a machine translation

A machine translation into the target languages shows how real text of these languages looks in your dialogs and forms. See Machine translation.

If the application crashes

A translation can break the application, for example when a format string loses a placeholder. Run Validate & Fix first. If the crash remains, Crash Finder finds the translation that causes it.