Selected Customers

Buy Now

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 372 released

5/22/2018

The new build comes with many new features. [...]

.NET Support updated

6/14/2018

New in May 2018: [...]

Sisulizer 4 Build 366

3/1/2017

Build 366 - support for Visual Studio 2017 [...]

10 Years Sisulizer

8/5/2016

Celebrate and save Big. [...]

Delphi Berlin, Android, Project Merge...

5/6/2016

Build 360 [...]

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

 

Default Translation Memory Options

When starting Sisulizer first time the default translation memory will be created. Some properties of the translation memory can not be changed after creatoin of translation memory. This is why Sisulizer asks user the creation settings. Generally it is recommended to accept the default values.

Create options

Specifies the translation memory creation options. These options can not be changed after the translation memory has been created.

Value Description
Keep case If checked the translation memory is case sensitive. This means that all data is stored as it is. When translating the translation memory first tries exact case match. If no string is found it ignores the case.
If not checked the translation memory is case insensitive. This means that all data is stored in lower case. When translating data the engine reformats the string case to match the original string.
Is is recommended to leave this check box checked.
Remove white spaces If checked the translation memory removes leading and trailing white spaces from the string before storing them. It is recommended to leave this check box checked. Sisulizer can automatically add leading and trailing spaces to the translations if the original string contains them.
This feature is not supported in some databases and with those database it is not possible to change this value.
Remove special characters If checked the translation memory removes the special characters from the string before storing them. Special characters are:
& Hotkey character used in Windows user interfaces.
For example &File.
_ Hotkey character used in WPF user interfaces.
For example _File.
: Semicolon is used in user interface to show that something is following.
For example Color:
... Three or two periods are used in menu items to show that item opens a user interface element such as dialog.
For example Options...
| Vertical line is used in some menu items to separate menu caption and menu hint.
For example Options|
It is recommended to leave this check box checked. Uncheck this only if you want the translation memory remember the exact location of the hotkey positions and special characters.

It is recommended to leave all above check boxes checked.

Maximum string length

Specifies the maximum string length in bytes that translation memory can store. The length is in bytes but strings are stored as UTF-8 strings. This makes the actual string length in bytes longer than in characters. The length is much longer if string contains non-European characters. Most database engines have a length limitation of a indexed string. If you enter larger value than the maximum value allowed by the database engine Sisulizer will use the maximum value.