Selected Customers

Buy Now

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 372 released

5/22/2018

The new build comes with many new features. [...]

.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. [...]

Delphi Berlin, Android, Project Merge...

5/6/2016

Build 360 [...]

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 Source Code Localization

Source code localization is very simple in Sisulizer because it is visual and safe. The basic idea of source code localization it to parse the source, extract strings from it and create localized copy of the source code where the original strings are replaced with the translated ones. The structure of the localized file is identical to the original file. Only the strings are different.

For example if we have the following C++ source code:

void TForm1::FormCreate(TObject *Sender)
{
  Caption = "Hello"; // Form caption
  Label1->Caption = "How are you?";
}

Sisulizer extracts two strings: "Hello" and "How are you?". When building the Finnish files Sisulizer creates the following source code:

void TForm1::FormCreate(TObject *Sender)
{
  Caption = "Moi"; // Form caption
  Label1->Caption = "Mitä kuuluu?";
}

When building the Japanese files Sisulizer creates the following source code:

void TForm1::FormCreate(TObject *Sender)
{
  Caption = "こんにちは"; // Form caption
  Label1->Caption = "お元気ですか";
}

As you can see only the string have been replaced. Everything else (e.g. code and comments) are left unchanged.

Whenever you change the original source code you have to create the localized source code files again. Just open the Sisulizer project file and choose Project | Build All. You can also use Sisulizer's command line tool, SlMake to build the localized files.

Source code localization is supposed to be used only with the platform that do not use resource files. Such platforms are J2ME applications and embedded system applications. Source code parser is also used together with other parsers such as XML and HTML to localize scripts that are embedded into these files.

Tagging

By default Sisulizer extracts all strings from the source code. You can exclude one or more strings by using tagging. You can also use tagging to make Sisulizer to extract only those strings that you mark.

Context

When you localize a source code file you can choose between two context methods.

Context method specifies how context value of formed. Possible values are:

Value Description
Item index Item index is the string context. Each item (code or string) has an index value that is a counting integer values starting from 0.
Compared to String value method this method creates own row for each instance of the same string letting you to translate them in a different way.
This is the default value.
String value String value is the string context.
If the source code contains same string twice of more then all instances share the single row and they all are translated in the same way.

Both methods can be used with any file. The difference is how duplicates strings are handled. Item index creates as many rows as there are duplicate strings. String value method always only one row for each string.

Samples

Sisulizer's Source directory contain source code samples.