Selected Customers

Specials run until 9/20/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


Invalid Script Validation

This validation checks if a string contains characters that do not belong to the language of the string. Sometimes when you enter translations you might enter characters that do not belong the script of the target language. This might cause that the computer where the end user runs the applications of views the document can not show the characters. Some examples:

Simplified and traditional Chinese mixed

When translating Chinese translators might enter Simplified Chinese when Traditional Chinese is needed or other way around.

Ansi applications

If your application is an Ansi application it is very important that translations only use script of the language. Ansi applications can not generally show mixed script text and it is very likely that some of the text that does not belong to the default script of the language is not shown correctly. In Unicode application you can mix scripts but event there on most cases translations using two or more scripts are mistakes and not by purpose.

This validation can be applied both to original and translated strings.