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


VCL Source | VCL Options

Use this sheet to configure how forms are localized.


Specifies how VCL forms are localized. Possible options are:

Value Description
Set BiDiMode property If checked Sisulizer changes the BiDiMode property when creating Middle Eastern forms. If the original value is bdLeftToRight, Sisulizer changes this to bdRightToLeft. This is applied only if ParentBiDiMode property of the same component is False.
Mirror forms If checked Sisulizer mirrors the form and its sub components when creating a Middle Eastern form. Uncheck this if you call TForm.FlipChildren method before showing the form. This is because FlipChildren automatically mirrors the form.
Scan only forms from RcData If checked only form data is scanned from RcData resources.
Scan inherited forms hierarchically If checked inherited forms are show as sub nodes of the parent node in the project tree.
Separate lines If checked each line of a Lines.Strings (e.g. TMemo.Lines) property is handled as a separate item. If unchecked the whole content of the List property is handled as a single item.
Use index in list items If checked items of strings list (e.g. TMemo.Lines) will use index context instead of value index.
For example we have three items in a list box: One, Two and Three. If this check box is unchecked (default) each value will have following context values: ListBox1.Items.Strings.One, ListBox1.Items.Strings.Two and ListBox1.Items.Strings.Three. If this check box is checked the context values will be ListBox1.Items.Strings[0], ListBox1.Items.Strings[1] and ListBox1.Items.Strings[2].
Vietnamese support If checked and if Sisulizer will set Font.Charset property on localized forms, Vietnamese 163 is used.

Form scaling

Specifies how the localized forms are scaled. VCL has a build-in form scaling. It works like this: When VCL loads a form it checks if the runtime height of the font is different to the design time height of the form. If it is VCL scales the components on the form. Unfortunately it does not scale the width and height of the form if the BorderStyle property is set to bsDialog. As a result some of the components may be cut off. To fix this Sisulizer has a form scaling option. Possible values are:

Value Description
Disable scaling If checked Sisulizer sets the TForm.Scaled property to False. This disables the build-in form scaling of VCL.
Scale forms If checked Sisulizer scales the width and height of the form. This scaling is done properly for every form no matter what are the property settings. Unfortunately the build-in VCL scaling is always based runtime fonts of the OS where the application is running. When Sisulizer does the scaling on the developers computer this might be different than the actual runtime scaling.
Ignore If checked Sisulizer does not change the Scaled, Width or Height properties.

Widestring (Unicode) usage

Specifies if Ansi strings are converted to Unicode strings when creating localized forms. Possible values are:

Value Description
Automatic Ansi strings are written as Unicode strings if the original application was compiled with Unicode enabled VCL (Delphi 6 or later, C++Builder 6 or later) and it contains at least one Unicode string in its form(s).
No Ansi strings are never converted to Unicode but are written as Ansi strings.
Yes Ansi strings are written always as Unicode strings. Use this if you use Unicode enabled VCL (Delphi 2009 or later, C++Builder 2009 or later) or Unicode enabled components such as TNT or ElPack.


Specifies the framework that is used. Possible values are:

Value Description
Detect Detect the framework.
FireMonkey FireMonkey.

Read more about strings in VCL.