Selected Customers
Specials run until 4/30/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. [...]
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
Visual C++ Binary Source | Resource Options
Use this sheet to specify the resource options.
Dialogs
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. |
Versions
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 |
General
Sets the version options. Possible values are:
| Value | Description |
|---|---|
| Application uses MFC library | Check this if the application uses Microsoft Foundation library (MFC). |
| Single string table | In Windows resource files strings are stored into string tables. There can be many string tables in a single EXE-file. By default a separate tree node for each string tables will be created. You can however to choose to combine every string rows into a single string node by checking Single string table Some tools combine string into a single string table. In that case you can also choose the same option. After that importing from existing EXE-file can be properly done. |