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
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
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
Use this sheet to specify the RC file options.
Specifies the localization options.
Sets the dialog options. Possible values are:
Value | Description |
---|---|
Scan owner draw text | Check this if you want to scan texts of owner draw controls. |
Scan spin control | Check this if you want to scan texts of spin controls. |
Scan visible property | Check this if you want Sisulizer to scan the Visible property of dialog elements. This makes it possible to hide some elements in the localized dialogs. |
Use charsets on dialogs | If checked the code page of localized language is used drawing the dialog and its elements. Otherwise the default code page is used. |
Sets the version options. Possible values are:
Value | Description |
---|---|
Update file version field | Updates the FILEVERSION ?,?,?,? field in VERSIONINFO resource |
Update product version field | Updates the PRODUCTVERSION ?,?,?,? field in VERSIONINFO resource |
Update language id | Updates language fields to match the localized language in VERSIONINFO resource |
Update code page | Updates code page fields to match the localized language in VERSIONINFO resource |
Update charset | Updates charset fields to match the localized language in VERSIONINFO resource |
Sets the version options. Possible values are:
Value | Description |
---|---|
Application uses MFC library | Check this if the application uses Microsoft Foundation library (MFC). |
Build excluded resources | Check this if you do not want Sisulizer to write excluded resources to the localized RC-files. |
Build relative paths to files | Check this if you want all external files be relative to the original file(s). For example 147 BITMAP "Images\BMP147.BMP" will become 147 BITMAP "..\Images\BMP147.BMP" Checking this you can use the images on original RC-file. You don't need to copy them to the localized directories. |
Scan #&include directives | Check this if you want to scan file name after #include
directive (e.g. "#include "file_name""). Only the file name is
scanned and a string row created for the file name. The content of file is not scanned. This can be
used when there is need to use a localized include files. |
Update language fields to match the target language | Check this if you want Sisulizer to update LANGUAGE and #pragma code_page part in the localized RC-files it creates LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US #pragma code_page(1252) |
Update by primary language only | If you have different sublangauges in resources, you can check this option in order to force to update all languages fields of different sublanguages in the localized file. Otherwise only the main sublanguages field are updated. |
Create images | If a image (e.g. BITMAP) has been translated it will be written to the localized directory if this has been checked. |
Use caption in menu context | Check this options if you want that the caption of popup menu is used instead of index. By default Sisulizer uses an index for menu objects without ID (Popup menus for example). This causes on problem when inserting a new popup menu between olds. |