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


Qt Settings

Use this dialog to configure Qt settings.


Each script has the default font to be used in the localized items. This list contains the default fonts.


To modify a font data select the script that you want to modify and press Edit.


You can import font data from a font file by pressing the Import button and browsing the font file.


You can export the font data to a font file by pressing the Export button.


Components sheet contains the component mapping list. Sisulizer uses its own visual components to render visual components, forms and dialogs. In order to properly draw the components Sisulizer needs to know the type of the component (i.e. label or button or check box). Component mapping performs this. It is used with platforms using components such as .NET, Delphi, C++Builder and Visual Basic. The purpose of the mapping is to give Sisulizer information about components that applications use.

By default Sisulizer contains mappings for all the standard component of the platform plus the most common 3rd party components. Sisulizer can localize any other component as well even if has not been mapped. However if the component is unmapped Sisulizer can not show it visually correct on the form editor but it shows the component and a pink box having "Click to map" text.

To map the component click the Click to map text and choose the component type. Mapping is not mandatory but it makes Sisulizer to show visual items better.

Each row in the component mappings list contains a mapping of one component. The mapping contains the following properties:

Class name

The class name specifies the class name of the component. For example the standard label component is TLabel in VCL and System.Windows.Forms.Text in .NET.


Sisulizer component type. Sisulizer contain a collection of visual component type. Select the type that is best match to the component type. For example if the component class name contains a label component (TMyLabel) the best choice would be Label.


Status column tells the status of the mapping. The possible values are:

Value Description
Auto Component has been automatically mapped based on the name of the component class.
Overload The user has changed component mapping values from the default values.
Custom Component mapping is a custom mapping added by the user.


By default Sisulizer extracts all string-typed properties and the properties that needs to be extract to get the visual information. Such kind of properties are for example left, top, width, height, color, font, input method and reading order. In most cases this is just enough to properly localize a component. However in some cases the component could contain a non-string-typed property that needs to be localized as well.

Editing mappings

Press Add to add a new mapping. Press Remove to delete the selected mapping. Press Edit to edit the selected mapping.

Press Import to import mappings from a mappings file. Press Export to export current mappings to a mappings file.

Press Restore to restore the default properties to the selected mapping. Press Restore All to restore the default mappings values.

For example the component might contains Mirrored property that controls the layout of the component. When localizing to a bi-directional language such as Arabic or Hebrew this property should be set True. In order to localize the property you need to get the property value to the project grid first. To do that add the property name to the property list as an included property. Next time you scan a project containing source file that uses such a component the Mirrored property will be scanned.

Some components contain string properties that should not be localized. For example most database components contain table name, SQL statements or connection strings. You can disable scanning of these properties by adding them to the properties list as an excluded property.


Keywords sheet contains the keyword list. Keywords are used in component mapping. By default Sisulizer contains mapping list that contains the most common 3rd party components. However if you use some other component library you have to map these components. To make this easy Sisulizer contains automatic component mapping feature that makes it possible to automatically detect the component type from the component class name. Sisulizer uses keywords to perform the automatic mapping. The mapping algorithm uses the keyword list. When Sisulizer finds an unmapped component it check if any keyword in the keyword list equals the tail of the component class name. If a match is found Sisulizer maps the component to the component type specified in the keyword list. Sisulizer searches keywords in the order they appear in this list.

Tail of the class name

The name is case insensitive.


The Sisulizer component where the component class having the above tail is mapped.


Status column tells the status of the keyword. The possible values are:

Value Description
Overload The user has changed keyword value from the default value.
Custom Keyword is a custom keyword added by the user.

Editing mappings

Press Add to add a new keyword. Press Remove to delete the selected keyword. Press Edit to edit the selected keyword.

Press Import to import keyword from a keyword file. Press Export to export current keywords to a keyword file.


Properties sheet contains property list. The purpose of the list is to either include or exclude localization of certain properties no matter what is the component where they belong to.

Property name

The name of the property.


The localization mode. Possible values are:

Value Description
Include Property is localized
Exclude Property is not localized


Status column tells the status of the property. Possible values are:

Value Description
Overload The user has changed property value from the default value
Custom Property is a custom property added by the user.

Editing mappings

Click Add to add a new property. Click Remove to delete the selected property. Click Edit to edit the selected property.

Click Import to import properties from a property file. Click Export to export current properties to a property file.


In order to compile the localized resources Sisulizer needs to know the location of the tools used by Qt.

Lupdate executable

Set the full path name of Qt's lupdate commmand line tool.

Example: C:\Qt.4.3\bin\lupdate.exe

Lrelease executable

Set the full path name of Qt's lrelease commmand line tool.

Example: C:\Qt.4.3\bin\lrelease.exe

By pressing the Default button Sisulizer tries to detect the location of the files.