Selected Customers
Specials run until 2/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.
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. [...]
.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
HTML Help Source | Options
Use this sheet configure how help file is localized.
HTML Options
Specifies how HTML data is localized. Possible values are:
| Value | Description |
|---|---|
| Scan images | If checked Sisulizer scans images of the HTML files making it possible to replace them in the localized files. |
| Scan scripts | If checked Sisulizer localizes client side scripts such as JavaScript and VBScript codes. |
| Update image sizes | If checked Sisulizer updates the image size attributes to match the localized image (if any) when writing the localized HTML files. |
| Update sizes in image styles |
If checked Sisulizer updates the image size values in style attributes to match the localized image (if any) when writing the localized HTML files. For example the size of the original image is 200x100 and the translated image is 210x110. style="width:200px; height:100px;"-> style="width:220px; height:110px;" |
| Keep format | If checked the text preserves spaces and line breaks. Otherwise all extra spaces and all line breaks will be removed on scanned rows. |
| Keep format in code tags | If checked the text enclosed in the code element preserves spaces and line breaks. Otherwise all extra spaces and all line breaks will be removed on scanned rows. |
HTML Help Options
Specifies HTML Help options and what other HTML Help items in addition of HTML data is localized. Possible values are:
| Value | Description |
|---|---|
| Scan contents | If checked Sisulizer localizes contents data (.hhc file). |
| Scan index | If checked Sisulizer localizes index data (.hhk file). |
| Scan browse sequence | If checked Sisulizer localizes browse sequence data (.brs file). Some help authoring tools can add browse sequence elements into CHM file. |
| Scan script | If checked Sisulizer localizes script files (e.g .js file). |
| Create localized CHM file | If checked Sisulizer creates localized CHM file. If unchecked Sisulizer creates localized HTML files. The user has to use HTML Help Compiler to compile localized HTML files into localized CHM file. |
| Group items | If checked contents, index, browse sequence, and browser nodes are grouped in Items folder in the project tree. If unchecked above nodes are placed in the root node of the source. |
| Use compatible language id whenever possible | If checked Sisulizer uses compatible language id when creating localized CHM file. This means that if the target language is not English but uses Western code page 1252 such as German or French, Sisulizer sets the language id of the CHM to English (United States), |
| Use compatible index | If checked and original CHM file uses binary index then Sisulizer creates binary index to localized CHM files only if the code page of the target CHM and the current system match.If code pages do not match then the localized CHM file does not use binary index. This option is because HTML Help compiler can not create correct index data if there is no code page match. Learn more about this. |
| Include images in the Files section | If checked Sisulizer add images files in the Files section of the project file (.hhp) of the localized CHM file. Check this if the localized CHM files do not include all images files. |