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


Database Source | Settings

Use this sheet to specify how to maintain project during the scan process and how to update the localized databases during the build process.

Replace project translations with existing translations in database

Specifies the existing translation will be replaced with the values in the database when scanning the database. Possible options are:

Value Description
Never update existing translations Does not bring any translation from the database to the project.
Update only project empty translations Bring translations from the database to the project only if the current value in the project is empty.
Always update existing translations Bring translations from the database to the project. Overwrite the existing value if it differs from the value in the database.

Set the value to the second or third value if you have manually modified the localized values in the database and you want to get the modified values from the database to the project.

This option is not enabled if either database cloning is used or segmentation is turned on.

When building incomplete database rows

Specifies how incomplete row should be handled during the build process. Possible options are:

Value Description
Use original string Use the original value in the field.
Use empty string Write the empty string to the field.
Skip row Skip the row and does not write anything.

This option is not enabled if database cloning used.


Specifies other options.

Check Database is case sensitive if your database used case sensitive collation. Uncheck this is the databases uses case insensitive collation.

Check Use Oracle language codes if your database is Oracle and you wan to use Oracle language codes instead of ISO language codes.

Value of the first block number specifies the number of the first blcok if the strings is devided into several rows.

Language id case

Specifies the language if format. Possible values are:

Value Description
Standard Language part is lower case. Country part is upper case. For example en-US and de-DE.
Lower Both lanugage and country parts are lower case. For example en-us and de-de.
Upper Both lanugage and country parts are upper case. For example EN-US and DE-DE.

Read more about database localization.