Windows desktop localization · Lingobit Localizer 10
Localize the build, not the source code.
Lingobit Localizer works on compiled Win32, WinForms, and WPF applications. Use your translators or machine translation, check the result in the real UI, and translate only what changed in the next release.
Switching tools? Bring your translations
- Windows desktop application
- Works offline
- Perpetual license
Five steps from your build to a localized release.
Start from the EXE and DLL files you already ship.
Lingobit reads resources from the compiled application and writes localized files back. Pick your platform to see how it works.
Windows desktop
Other platforms
- Delphi / C++Builder .exe .dll .dfm
- Java .properties .jar
- Qt .ts .ui
- Python .po
- Apple .xib .strings .plist
- Android values XML
- XAML
Web, help, and data
- HTML, ASP, PHP
- XML
- HTML Help .chm
- Help & Manual
- Databases
- INI, SQL, plain text
- Customizable parsers
Exchange formats
- XLIFF 1.2
- TMX translation memory
- TBX terminology
- CSV and text
- Lingobit translator project
Editions
- StandardVisual translation, translation reuse, validation, and the translator workflow.
- ProfessionalAdds translation memory, machine translation, pseudo-translation, and command-line automation.
- EnterpriseAdds terminology, Crash Finder, and help, database, and folder localization.
- Enterprise Multi-UserEnterprise for multiple users in one organization.
Switch to Lingobit without translating everything again.
Lingobit imports existing translations straight from your localized EXE, DLL, and resource files — no old project needed. Switching costs a project setup, not a retranslation.
New in Localizer 10
See what's new in Localizer 10-
.NET and WPF, reworked
- .NET Framework 4.8 and .NET 5–10
- .NET version and bitness detected automatically
- 64-bit resource processing and form editor
-
Form editor
- Full and Safe modes for WinForms forms
- A failing assembly no longer closes Localizer
- Controls stay in place on scaled forms
-
Machine translation
- Now with DeepL, Google Translate, and Azure Translator
- Batch translation of the whole project
- Rebuilt Translation Hints panel
-
Translation memory and terminology
- Import only what matches the project, even partly
- Microsoft terminology, downloaded automatically
- TMX, XLIFF, and CSV in one import wizard
-
Output panel
- One panel for scans, imports, and validation
- For most operations, details show what exactly changed
- Go to the element and fix it from the results
-
Interface and command line
- New theme, start page, and menus
- Translation editor: element types, translated position and size
- Extended command line, with validation for the build
Try Lingobit Localizer on your own build.
Create a project from your compiled files, machine-translate it, and run the localized version in your own environment.
Need a more specific workflow?
- Source preparation and ExtractorMove hardcoded strings into resources before translation starts.
- RC, RES, and C++ source cleanupPrepare native Windows resource and source files for translation.
- Multilingual LibraryOptional: let MFC applications switch language at runtime.