Selected Customers

Specials run until 8/10/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


Windows Binary Source | Header files

Specifies the header file

Header Files

Specifies .h files that contains the symbolic names of the resource id. If you specify file(s) Sisulizer uses the symbolic names of the file instead of the resource ids that are integers. Let's have an example. We have two files: resources.rc that contains the resources and resources.h that contains names and ids. resources.h contains the following line:

#define IDS_ABOUTBOX 101

It give IDS_ABOUTBOX symbolic name and integer id 101. resources.rc contains the following lines:

  IDS_ABOUTBOX "&About Converter..."

When the resource compiler compiles the above resource it gives the string id. The id is an integer number 101. This is stored to the resource data of EXE file with the actually string. When Sisulizer scans the resource data it gives the string id that is 101. Unfortunately this id does not tell much about the string and its context. If you give the resource id file Sisulizer uses the symbolic name of the id (IDS_ABOUTBOX ) as context. This gives more information to the translator than plain number of 101 would give.

If you add a resource id file or files Sisulizer uses symbolic names instead of integer values on every possible id. This also makes it possible to import translations from localized .rc files. Without header files you can import translations only from localized binary files.

Click Add to add a new file. Click Edit to edit the selected file. Click remove to remove the selected file. Click Clear to remove all files.

Resource Files

By default Visual Studio uses IDS_xxx as resource ids. If this is true in your case you can leave this filed empty. However if you use some other id naming convention you have to specify the original resource files (.rc) too. This way Sisulizer can map the integer id to the correct symbolic name.

Click Add to add a new file. Click Edit to edit the selected file. Click remove to remove the selected file. Click Clear to remove all files.