Selected Customers

Specials run until 10/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.

Update to Sisulizer 4

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

 

Custom Windows Resources

Custom Windows resource are resource data that do not use any predefined Windows resource type but use named a resource type. For example:

Ski IMAGEDATA "Ski.jpg"

The above line for a .rc file adds IMAGEDATA typed custom resource with "Ski" name. The resource data is read from Ski.jpg file. Whenever you have a custom resource Sisulizer tries to detect its format. Sisulizer can handle custom resources as following formats:

Format Description Can Sisulizer detect the format
Image JPEG, PNG, GIF, BMP, ICO and CUR images Yes
Text Text file Yes if text file contains either UTF-8 header or UTF-16 byte order mark (BOM). If you file uses Ansi encoding Sisulizer can not detect the format but you have to specify the format manually.
XML XML file Yes
HTML HTML file Yes if the resource contains whole HTML page and not part of it.
Binary Any data. Sisulizer does not interpret the data but lets the translator to assign translated binary data file. When Sisulizer build the localized file it uses data from the give translated binary data file. No

Specifying the format manually

If Sisulizer can not detect the data format of custom resource you can specify the format manually. Right click the resource item node on the project three and choose Properties. Uncheck Automatic check box and set the format in the Format combo box.