Selected Customers

Specials run until 10/31/2021

Offers are for commercial and industrial customers only.
All prices are net.

Complete Price Sheet.

Not sure which edition is the right one? Visit our Edition Comparison

Update to Version 4

Sisulizer version 4 is a paid update recommended for all Sisulizer customers.

Update to Sisulizer 4

Still using Sisulizer 3 or Sisulizer 1.x/2008/2010?

Time to update to version 4 now and profit from all new features in version 4.

Software Localization News

Version 4 Build 374 released


The new build comes with many new features. [...]



Tutorials updated [...]

.NET Support updated


New in May 2018: [...]

Sisulizer 4 Build 366


Build 366 - support for Visual Studio 2017 [...]

10 Years Sisulizer


Celebrate and save Big. [...]

Our customers use Sisulizer...

to reach international customers with software in their language

to localize their in-house software in the international subsidiaries

to build multilingual custom software for their clients' enterprises

as Localization Service Providers because it is the localization tool of their customers

to localize software at Government Agencies

To teach software localization at Universities

for software localization on Electronic Devices

To translate software for Biomedical Hardware

to localize software in the Mining Industry

to create multilingual software for Mechanical Engineering


Skip the typical software localization beginner's traps


Your first consideration is most likely the language. At the very least, you must think about how to translate all strings in the application user interface. Usually, these are strings for menu entries, dialog boxes, message boxes, the status bar, and error messages.

If you want to send all strings to a translator, you must consistently separate strings from source code. Don't hard-code strings! If you did, convert these strings to string resources. Start this process now. Don't wait until you are under pressure to meet a deadline.

All major development languages for Windows support resource files. You have no excuse! You can easily read strings from resources, such as in classic Visual Basic with LoadResString or LoadStr in a VCL application.

What you need to do

Store all strings in Windows standard resource files; or, if you develop with Microsoft .Net, use ResX. In .Net applications make sure you set the localizable property to True!

How does Sisulizer support you

Sisulizer supports localization of resource files. It is perfect in binary localization of executables (.exe, .dll, .ocx) with embedded resources, or linked resource DLLs, .Net ResX files, and assemblies.

And the clue: You localize in a WYSIWYG environment. Your translator sees the dialogs, and menus he is translating, visually and in context! This speeds up translation process by reducing the questions that otherwise would arise; and maximizes localization quality!

Software localization traps