Selected Customers

Specials run until 11/20/2019

Offers are for commercial and industrial customers only.
All prices are net.

Not sure which edition is the right one? Visit our Edition Comparison

Sisulizer version 4 is a paid update recommended for all Sisulizer customers.

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.

Version 4 Build 374 released

11/30/2018

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

Tutorials

3/5/2019

Tutorials updated [...]

.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. [...]

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

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

Use this sheet configure how TMX file is localized.

Specifies if the localized TMX file(s) contains multiple tuv elements or just one tuv element in each tu element. Possible values are:

Value	Description
Add localized tuv elements	The localized TMX file contains the original tuv and localized tuv(s).
Change original tuv elements	The localized TMX file contains only the original tuv where seg element and language attribute have been changed to match the target language.

Specifies how context value is generated. Possible values are:

Value	Description
String value	Context is the string value of the original tuv.
tuid value	Context is the value of tuid attribute of tu element. If there is no tuid attribute or its value is empty then string value is used.

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

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