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


Delphi Source | Project

Use this sheet configure how forms are localized.

Resource string tags

Check Scan source code to find resource string comments check box to make Sisulizer to scan the source code. Checking this will slow down the scanning speed so check it only if your source code contains resource string tags. You need to have source code available and you have to specify project file name in order to enable resource string tags.

Resource string tag is used to pass resource string comments and properties to the project. The syntax is


where tag is a tag string (e.g. slz), mc is the maximum length of the translation in characters, mp is the maximum length of the translation is pixels, and expression is the combined string expression.

The following line has an resource string tag that contains a comment ("A message that is shown when the application starts"):

SMsg = 'Hello world'; //slz A message that is shown when the application starts

The following line has an resource string tag that contains a comment ("Clicking this button opens on-line help") and sets the maximum length to 300 pixels:

SMsg = 'Click Help to get more information'; //slz MaxPixels=300 Clicking this button opens on-line help

Project file name

Specifies a Delphi project file (.dpr). Use this if you have unit names having _ in their file names and those units use resource strings having also _ in their names. Otherwise Sisulizer can not determine the exact resource string context. For example if My_File.pas has the following resource string

  SMy_Sample_String = 'This is a sample';

It is highly recommend to specify project file. However Sisulizer can localize VCL applications without project files.

DRC file name

Specifies a DRC file that contains tables of all string constants declared by the resourcestring keywords.

If you add a platform file such as 64-bit EXE or DLL make sure that the same directory contains the DRC file of the 64-bit EXE or DLL. For example if your 64-bit file is C:\Sample\Debug\Win64\Project1.exe there must be also C:\Sample\Debug\Win64\Project1.drc. Make sure that Delphi compiler creates the DRC file.

DRC file name of &OSX (required if OSX platform file exists)

If yo add a OSX platform file then you must also specify the DRC file of the OSX file. Learn more about Mac localization.

Context method of string resources

If you do no specify a DRC file then you have to select what context method is used with resource strings. Possible values are:

Context method Description
String value Sisulizer uses string values as context values. This is safe even if you modify and recompile your application. However if the application has the same text in two ore more resource strings this method brings only one row to the project file. So all instances of the same text will share the same row and you can no longer translate them in a different way.
Resource id Sisulizer uses resource ids as context values. This is potentially dangerous because it is very likely that Delphi compiler will change the resource strings ids next time you compile your project. This will cause lost of translations or switching of existing translations. Both are very hard to fix.

Because both alternative context methods have their limitation and dangers it is very much recommended to specify a DRC file. To create a .drc file choose Project | Options | Linking from Delphi and select Detailed in the Map file selection. In Delphi XE2 or later you can also turn DRC files on by checking Output resource string .drc file check box.