Selected Customers

Specials run until 12/20/2019

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

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

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

 

System code page and CHM compilation

HTML Help compiler is rather old product. It does not support Unicode even it allows that topic files use UTF-8 encoding. TOC and index files are not Unicode. When HTML Help compiler compiles topic, TOC and index files into CHM it assumes that the system code page is same as the code page of the target CHM. This might not be the case if you have a Western OS but are localizing CHM into Asian languages such as Japanese. In such case the binary index of the CHM get invalid and when CHM is viewed the index data shows up as mojibake.

Mojibake index

when the correct one should be

Correct index

To avoid this Sisulizer by default does not create binary index when creating localized CHM file that would require different code page. Not having a binary index does not prevent the user to use index, it just makes index little bit slower. If you want to turn off this default and force Sisulizer to always use the binary index (if the original CHM uses binary index) you have to uncheck Use compatible index check box from the Options sheet of the HTML Help source dialog.