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
Some compilers can compile the same project for two or more platforms. Platforms are for different CPU or for different operating system. For example Visual C++ can compile projects for 32-bit and 64-bit Windows. Delphi can compile VCL applications for 32-bit and 64-bit Windows. Delphi can compile FireMonkey application even more platform such as OSX and iOS. The common things for platform files are they each platform file for same project contains the same resource items. Only the code part of the platform files differ. When dealing with multiple platform files one choice would be to add each platform file into Sisulizer project. However this approach is not good because it causes every resource and strings to appear multiple times. By adding only one file into the project and then configuring that file to have one or more platform files is a much better solution. First is brings each item only once to the project and secondly the same settings are used for each platform files.
Create a Sisulizer project that contains a WIN32 EXE. Once the project is created add the additional files as platform files. Right click the EXE file in the project three and choose Properties. Then choose Platform files sheet and click Add button to add files. Add the 64-bit output file of the same project. If you have more than two output targets then add each platform file.
Now you have added two platforms files, 64-bit Windows file and 32-bit Mac file. The main file of the source is specified in the File sheet and it is 32-bit Windows file. All three files contains the same sources and are localized in the same way.
The following table contains the development tools supported by Sisulizer that can create multiple target files:
Development tool | Description |
---|---|
Visual C++ | 32-bit and 64-bit Windows. |
Visual Studio using .NET | Several .NET assembly formats: 32-bit, 64-bit, platform independent. |
Delphi XE2 and C++Builder XE2 or later using VCL | 32-bit and 64-bit Windows. |
Delphi XE2 and C++Builder XE2 or later using FireMonkey | 32-bit and 64-bit Windows, 32-bit OSX and iOS. |