Sisulizer alternative
A Sisulizer alternative that keeps your translations.
Sisulizer is no longer developed. Lingobit Localizer 10 localizes the same kind of software, compiled Windows applications in Delphi, C++Builder, MFC, WinForms, and WPF, and takes the translations from the localized files you shipped with Sisulizer.
- Approach
- Localize the compiled files, without source code
- Your translations
- Imported from the localized files you shipped
- Delphi
- Forms in the DFM preview, resource modules such as
MyApp.DEU - .NET
- .NET Framework 4.8 and .NET 5–10
The way you worked with Sisulizer still works.
Add the files you ship, translate them with the forms in front of you, send work to translators, and build a localized version for each language. No source code, no rebuild for each language.
Same approach
- Localization of EXE, DLL, and BPL files and .NET assemblies, outside the source-code cycle
- Translation in the visual editor: dialogs, WinForms forms, Delphi and C++Builder forms
- A localized EXE for each language, resource-only DLLs, or .NET satellite assemblies
Same release routine
- Scan for Changes on each new build: only new and changed strings need translation
- Translators work in Translator Edition, included with every Localizer license
- Command-line builds with Professional and higher
Sisulizer and Lingobit Localizer 10 compared.
Sisulizer as it was last released; Lingobit as it ships today.
| Topic | Sisulizer | Lingobit Localizer 10 |
|---|---|---|
| Development | No longer developed; the website has been offline since 2021 | Localizer 10.0, released in 2026; updates and support with Annual Maintenance |
| Licenses | No longer sold | Perpetual licenses in Standard, Professional, Enterprise, and Enterprise Multi-User. Pricing |
| Approach | Localization of compiled files | Localization of compiled files |
| Output | Localized files, multilingual files, resource DLLs, .NET satellite assemblies | A localized EXE for each language, resource-only DLLs and Delphi resource modules, .NET satellite assemblies |
| Delphi and C++Builder | Written in Delphi; VCL units for changing the language at runtime | Forms and resource strings in EXE, DLL, and BPL files; DFM preview; resource modules that Delphi loads by itself. No runtime units |
| WinForms and WPF | WinForms, WPF, and Silverlight, for the .NET versions of its last release | WinForms form editor and WPF (BAML) on .NET Framework 4.8 and .NET 5–10 |
| Win32 and MFC | Localized files and MFC resource DLLs | Dialogs, menus, and string tables; MFC loads resource DLLs such as MyAppDEU.dll by itself |
| Your existing translations | In the .slp project and the localized files it built | Imported from the localized files, with positions and sizes from the same version. .slp projects are not opened |
Where Lingobit differs from Sisulizer.
Lingobit is a localization tool for Windows desktop software in general, not a tool written around the VCL. For most Delphi applications that use standard forms and resource strings, that makes no difference. Check the points below before you switch.
Covered
- Forms, resource strings, and their properties in the EXE, DLL, and BPL files you ship
- Custom VCL controls mapped to preview controls in the VCL form editor settings
- A localized EXE per language, or resource modules such as
MyApp.DEUnext to the unchanged EXE - Unicode and non-Unicode Delphi applications, with a warning when characters do not fit the code page
Check first
- Your application changes the language at runtime with Sisulizer's units: test it with resource modules made by Lingobit
- Only the
.slpproject is left, no localized files: build them once in Sisulizer, or see the other paths - Text that is assembled at runtime and is not in the files
Your Sisulizer translations come with you.
Add the release you shipped and import the translations from its localized files: every string gets its translation item by item, with positions and sizes. Then Scan for Changes brings in your current build. You do not need Sisulizer running.
Sisulizer alternative FAQ
Can Lingobit open Sisulizer .slp projects?
No. Lingobit takes the translations from the localized files your Sisulizer project produced: localized EXE and DLL files, resource DLLs, .NET satellite assemblies, and translated .resx files. See Move from Sisulizer.
Is Lingobit a native VCL tool like Sisulizer?
No. Lingobit is written for Windows desktop software in general. For Delphi and C++Builder it translates forms and resource strings in the EXE, DLL, and BPL files, shows forms in the DFM preview, and writes a localized EXE or resource modules such as MyApp.DEU that Delphi loads by itself. It does not include runtime units for switching the language.
Which applications can I localize with Lingobit?
Compiled Win32 and MFC applications, Delphi and C++Builder applications, WinForms and WPF applications on .NET Framework 4.8 and .NET 5–10, .NET resource files, and the further formats on the Supported formats page.
Can I try it on my own files first?
Yes. The free trial runs for 90 days. Add the release you shipped, import its translations, and see what comes over. See Download.
Bring a Sisulizer release and see what comes over.
Your original files and their localized versions are enough. Import, scan your current build, and review what changed.