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


Visual Report Localization

Sisulizer can localize reports. In order to do that it localizes the report template data and the database that the report uses. Together this produces multilingual reports feature where the same report can be produced in several languages.

Report Template Localization

Report tools use report templates. They define the report layout and bind data to the report. Report tools combine report template with the actual data from database to produce reports. The first step of report localization is to localize the template data. The data can be either embedded to the report component on the user interface form or it can be a separate file. If it is embedded Sisulizer will automatically localize the report template when localizing the form where the report component exist. If you use external report file you have to add the report file to your Sisulizer project. On build process Sisulizer will create localized report files.

Database Localization

Most reports contains data that need to be localized. For example if we create a product report the report might contains "How to use" field that describes how to use the product. This data contains text that needs to be localized. in order to do that you have to localize the database itself. This is called database localization. Sisulizer support several different ways to localize database data. We recommend to use row localization because then you don't have to modify your SQL queries that much. It is enough that you add WHERE part to your query.

Let's have an example. You have Country table that contains data that you use in your report. When the table contains only one language (e.g. English) your SQL query is simple.


Let's suppose that we localize the your English database to German and Japanese using row localization method. Our database contains each row in English, German and Japanese. When we create English report we only use English rows and this is why we have to add WHERE part to the SQL statement.

SELECT * FROM Country WHERE Language='en'

In a similar way we can select German data for German report.

SELECT * FROM Country WHERE Language='de'

Sisulizer contains several sample applications that generate localized reports. See the table below to see sample location for your reporting tool.

Supported Report Formats

Sisulizer supports the following report tools:

Tool Platform Description Sample
Ace Reporter VCL Sisulizer localizes report data embedded to the form. <sldir>\VCL\DelphiWin\Report\Ace
QuickReport VCL Sisulizer localizes report data embedded to the form. <sldir>\VCL\DelphiWin\Report\QuickReport
ReportBuilder VCL Sisulizer localizes both report data embedded to the form and ReportBuilder report files (.rtm). <sldir>\VCL\DelphiWin\Report\ReportBuilder

If your reporting tool is not included in the above list you have two choices. If the reporting tool uses components to define report templates just map your report components to Sisulizer report components. If you reporting tool uses standalone report files contact Sisulizer.