FAQ

The translation looks right in Lingobit Localizer, but the localized application shows wrong characters.

The application probably does not use Unicode. See Running a non-Unicode application.

Lingobit Localizer does not show Chinese, Japanese, or Korean characters.

Install a font for the language in Windows.

How do I include localization in our build process?

Use the command line, for example localizer.com MyApp.loc -scan -lang:all -validate -create -save. It is available in Professional and higher.

Our application is already translated. Do we have to translate it again?

No. Import the translations from the localized files you ship. See Migrating from other tools.

We have translations in a text or CSV file. How do we use them?

Import the file into translation memory with Project > Translation Memory > Import Matching Translations and translate the project with Project > Translate Using > Translation Memory.

How do we work with a CAT tool?

Prepare a translation task as an XLIFF or CSV file and import the result with Import Translation Results. Translation memory can be exchanged as TMX. See About translation tasks.

Do translators need our source code or our application?

No. Translators get a translator project or a delivery bundle prepared with Prepare Translation Task and work in Translator Edition, which is included with every Localizer license. See Working with translators.

We localized an MFC application, but some strings are still in English.

If the application links MFC dynamically, some texts come from the MFC resource DLLs; Visual Studio includes them for several languages. Standard Windows dialogs and messages come from Windows and follow the language of Windows.

I cannot move controls in the dialog editor.

Use the commands in Designer > Move and Designer > Align.

What about applications on .NET 1.x–3.5?

Localizer 10 supports .NET Framework 4.8 and .NET 5–10. For applications on .NET 1.x–3.5, use Localizer 9.