Selected Customers
Specials run until 4/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. [...]
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
Project Wizard - Visual C++ binary file
Use this sheet to specify the Visual C++ binary file options.
Output files
Specifies what kind of output files Sisulizer creates and what kind of file name it uses when creating those files. You can check one or more output file types.
| Output file type | Description |
|---|---|
| Localized files | If checked Sisulizer creates a localized file for each language in the project. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates de\MySample.exe and ja\MySample.exe. These files are equal to the original file except resource data has been localized. |
| Multilingual file | If checked Sisulizer creates one multilingual file containing all the languages of the project. For example if the original file is MySample.exe, Sisulizer creates all\MySample.exe that contains resources in each language of the project. |
| Resource DLLs | If checked Sisulizer creates localized resource DLL files. They are resource-only DLLs that contains the same resource data as the original file but the resource data has been localized to the target language. Delphi and C++Builder (VCL) Use VCL's resource files and Sisulizer VCL functions to enable run-time language switch. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates Sample.DE and Sample.JA resource DLL files. Visual C++ (MFC) Use MFC's resource files to enable initial language choose. For example if the original file is MySample.exe and the project contains German and Japanese, Sisulizer creates SampleDE.dll and SampleJA.dll resource DLL files. |
| Embedded resource DLLs | If checked Sisulizer creates an output files that contains all the resource DLL files embedded into the original file. Such an EXE can support several language in one file and the user can even change the language of the application on run time. The output directory for the embedded file is "emb". |
Options
Specifies the localization 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. |
Resource id file name
Specifies a .h file that contains the symbolic names of the resource id. If you specify this Sisulizer uses these symbolic names instead of the resource ids that are integers. Let's have an example. We have two files: resources.rc that contains the resources and resources.h that contains names and ids. resources.h contains the following line:
#define IDS_ABOUTBOX 101
It give IDS_ABOUTBOX symbolic name and integer id 101. resources.rc contains the following lines:
STRINGTABLE BEGIN IDS_ABOUTBOX "&About Converter..." END
When the resource compiler compiles the above resource it gives the string id. The id is an integer number 101. This is stored to the resource data of EXE file with the actually string. When Sisulizer scans the resource data it gives the string id that is 101. Unfortunately this id does not tell much about the string and its context. If you give the resource id file Sisulizer uses the symbolic name of the id (IDS_ABOUTBOX ) as context. This gives more information to the translator than plain number of 101 would give.
If you set the resource id file name Sisulizer uses symbolic names instead of integer values on every possible id. This also makes it possible to import translations from localized .rc files.