Update to Version 3

Sisulizer version 3 is a paid update recommended for all Sisulizer customers.

Still using Sisulizer 1.x or Sisulizer 2008/2010?

Time to update to version 3 now and profit from all new features in version 3.

Specials run until May, 20 2012

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

Social Networks

Please click this facebook button if you want to share this page with friends

Share

(english) (german)


Please click this Google +1

button to give Sisulizer a positive vote in Googles new voting system.

Thank you very much.

Selected Customers

Software Localization News

Version 3 Build 331 released

23.4.2012

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

Top News: Version 3

9.11.2011

Sisulizer version 3 out now. [more]

Tips & Tricks

30.9.2011

You are looking for tips and tricks around Sisulizer? [more]

Delphi Tage

8.9.2011

Delphi Tage 2011 in Cologne are sold out! [more]

Download Build 321

12.8.2011

Please us a download manager for your download. [more]

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.