Update to Version 3

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

Update to Sisulizer 3

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 5/20/2013

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

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

 

Selected Customers

Software Localization News

Version 3 Build 339 released

4/24/2013

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

Update Alert

9/25/2012

Android app for Sisulizer customers available. [...]

Windows 8, Delphi XE3

9/3/2012

Ready for the future. [...]

Delphi Tage

8/13/2012

Delphi Tage 2012 in Heidelberg. [...]

Top News: Version 3

11/9/2011

Sisulizer version 3 out now. [...]

The German and French Online-Help pages have been created with the help of machine translation. In doubt please read the English original.

JSON Source | File

Use this sheet to specify a file to be localized and the location and naming of the localized files that Sisulizer creates.

File name

Type the file name, or press the "..." button to browse to a file. The file must be an JSON file (e.g. C:\Samples\Sample.json).

Output directory

Specifies the directory where Sisulizer creates localized files. By default the output directory is usually the same directory where the original source file is located. You can change this by pressing ... and browsing another directory.

Output files

Specifies what kind of output files Sisulizer creates and what kind of file name it uses when creating those files. Combo box is used to specify the name of the output file. You can select a pattern from the combo box list or you can type your own pattern. Each pattern can contain file and language parameters.

File parameters are:

Parameter Description
<file> Variable is replaced with the original file name with extension.
C:\MyFiles\Sample.exe -> Sample.exe
<dir>

Variable is replaced with the relative directory to the source file including the last backslash.
If the source file is
C:\MyFiles\*.html
and if the file to be processed is
C:\MyFiles\SubFiles\Sample.html
variable is replaced with
SubFiles\
If the file locates in the same directory as the source directory this parameter is ignored.
<body> Variable is replaced with the original file name without extension.
C:\MyFiles\Sample.exe -> Sample
<name>

Variable is replaced with the fixed name of the file or original file extension without period (if the file does not have a fixed name).
C:\MyFiles\Sample.exe -> MyName
Fixed name is a name determined by the original platform and it can not be fixed (e.g. .NET specifies assembly name in the project file and that name must be used in order to enable satellite assembly file).
<ext> Variable is replaced with the original file extension without period.
C:\MyFiles\Sample.exe -> exe

If pattern does not contains <dir> parameter Sisulizer automatically adds it into the beginning of pattern before processing it.

Language parameters are:

Parameter Description
<sl> Sisulizer's locale code is used.
For example "en" is for English, "en-US" is fo English (United States), and "zh.tra" is for Traditional Chinese. The default Chinese script is the Simplified Chinese. This is why the language code of Traditional Chinese is "zh.tra".
<iso> ISO locale code is used. It is combination of language and country. The syntax is
la[_co[_variant]]
where
la ISO-639 language code
co ISO-3166 country code
variant ISO variant code
For example "en" is for English, "en_US" is fo English (United States), and "zh_TW" is for Traditional Chinese. ISO language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.
<net> NET culture code is used. It is combination of language and country. The syntax is
la[-co[-script]]
where
la .NET language code.
co .NET country code
script .NET script code
For example "en" is for English, "en-US" is fo English (United States), and "zh-TW" is for Traditional Chinese. .NET language code does not have any way to code a country neutral Traditional Chinese. That is why Chinese (Taiwan) is used.
<win> Windows locale code is used. It contains two or three upper case characters.
For example "EN" is for English, "ENU" is for English (United Stated), and "CHT" is for Traditional Chinese.
<mfc> MFC locale code is used. It contains three upper case characters.
For example "ENE" is for English, "ENG" is for English (United Kingdom), and "CHT" is for Traditional Chinese.
<nls> Windows locale id is used. It is a integer number containing the primary and sub language ids.
<hex> As above but four digit hex value is used instead decimal value.

For example if the original file is C:\MyFiles\Sample.xml and the pattern is <body>_<iso>.<ext> the German (Austria) file will be C:\MyFiles\Sample_de_AT.xml.

For example if the original file is C:\MyFiles\Sample.xml and the pattern is <sl>\<file> the Chinese (Taiwan) file will be C:\MyFiles\zh.tra\Sample.xml.