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


Binary Settings

Use this dialog to configure binary settings. Binary settings are used with binary file localization and binary resource localization.


Use this sheet to configure binary format. Sisulizer can localize and import data from various binary based files. In order to properly scan the binary file you need to specify the format. It is done by defining fields. It is possible to specify the definition case by case but if you need to constantly work with certain file type you can define the format and give it a name. Finally you can attach the definition to a file extension.

The combo box on the upper side of the dialog contains the configured definition. Select the definition you want to edit. Click + button to add a new. Click - to remove the selected one. Click notepad image to rename the selected definition.

Definition is used when

Specifies if definition is used when localizing files or when importing files.

Header and Record

These sheets contain the header and record definitions. Header is an optional block in the beginning of the file. The file contains only on header. Record is a mandatory definition and it specifies a record. The file contains one or more records after the header. Header and record contain fields where each field contains one single data such as integer value or string.

Click Add to add a new field. Click Remove to remove the selected field. Click Edit to edit the selected field. Click Move Up to move selected field one step up in the list. Click Move Down to move selected field one steop down in the list.


Specifies the common options of the definition.

Byte order (endianess) specifies in which order data containing multiple bytes is written. Possible values are:

Value Description
Little-endian The least significant byte value is stored at the memory location with the lowest address, the previous byte value in significance is stored at the following memory location and so on.

The most significant byte value is at the lowest address.

String encoding and string length specify what is the default string encoding. When you add a string field into header or record you can either specify a generic string field or encoding and length depend string field. The difference is that generic string always uses the default string encoding. Specific string fields use hard coded string encoding. If you binary file encodes all string values in the same way it is better to use generig strings. If the file contains two or more different string encodings you have to use specific strings or you can use generic string for the most common field and specific string for other fields.

Possible encoding methods are:

Value Description

UTF-8 strings are used.


UTF-16 strings are used.

Windows code page Strings are encoded with Windows (ANSI) code pages.
ISO code page Strings are encoded with ISO code pages.
Mac code page Strings are encoded with Mac code pages.
OEM code page Strings are encoded with OEM (DOS) code pages.
EBCDIC code page Strings are encoded with EBCDIC code pages.
Other code page Strings are encoded with other code pages.

Possible length methods are:

Value Description
Null terminared A null characters is written following the last string character.
Preceding length byte

The length of the string in characters is written in the preceding byte of the the first character. Maximum string length is 255 characters.

Preceding length word

The length of the string in characters is written in the preceding word of the the first character. Maximum string length is 65535 characters.

Fixed length

The length of the string is fixed. Some files using fixed string length contain the actual length in the header. If this is the case add a string length or string size field into the header definition. If header does not contain the string length specify the size value.

File extensions edit contains the file extensions that use the defined binary format. If you give more that one extension separate them with semicolon (;).


Enter any text that describes the definition.


Shows a sample binary data of a file using the current definition. The file contains three records.


Click Test button to select a file and o run parsing on that fie using the current definition. Click Import button to import definition from a definition file. Click Export to export definition to a definition file. Click Sample to show a same sample as in the sample sheet but in a floating dialog.