Selected Customers

Specials run until 8/10/2021

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


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



Tutorials updated [...]

.NET Support updated


New in May 2018: [...]

Sisulizer 4 Build 366


Build 366 - support for Visual Studio 2017 [...]

10 Years Sisulizer


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


Language Codes and Translation Fallback

Language code is a unique code that identifies a language in Sisulizer. The three kinds of language codes:

Code Description
Neutral language This is the most common language code. It specifies a language such as English or German.
Country depend language This code specifies the language and the region (e.g. country) where the language is spoken. For example English (United States) or German (Germany). Using a country depend language code makes it possible to differentiate two or more different regions where the same language is spoken. For example American English and British English or Standard German and Swiss German. In both cases the language is same but different regions uses different words and/or spelling.
Language variant Sometimes it is necessary to differentiate language based on some other way but country. For example the are might be profession based slang of a language. For example Engineering English or Medical English. In these cases a language can have a variant or variants. Also a country depend language can have variants.

Each language has a unique language code. It is a combination of language, country, variant and script ids. The format is:


Value Description
language Specifies the ISO-639 language code.
country Specifies a ISO-3166 country code. This is optional.
variant Any string that describes the variant. This is optional.
script Specifies the script that the language uses. Normally this is omitted but if the language does not use the default script of the language then the script part must be included. Languages such as Azeri, Chinese, Serbo-Croatian and Uzbek can be written using two different scripts. In these cases there exits two code that have the same language code but but different script.

The following table contains language code examples:

Example Description
en English
en-US English (United States)
en--ENG Engineering variant of English
en-US-ENG Engineering variant of English (United States)
zh Simplified Chinese
zh.tra Traditional Chinese
ja Japanese Japanese written in Latin characters (e.g. Romaji)

Custom languages, countries and variants

You can add custom items to Sisulizer's language list. A custom item is either a custom language, custom country or custom variant. By default Sisulizer contains all the languages, countries and variants of the Windows version that you are using plus all the languages, countries and variants of the that Windows version that was most recent when your Sisulizer build was compiled.

Original language

Original language is the language that is used in the original file. For example if an American software company writes a software they usually use American English in user interfaces and help files. Similarly a German company uses German. It is essential that Sisulizer know the original language. This is why Project Wizard asks that information.

Target languages

A Sisulizer project contains one of more target languages. These are languages that the user adds to the project and purpose is to translate the original file(s) into those languages.

Default language

One of the target languages or the original language is the default language. Its purpose is to determine what language is used in the build process when there are no translation given. By default the default language is original language. This means that Sisulizer uses the original value in the case there is no translation value in the project. You can set the default language to be any target language in the project. This is useful in the case that original language is a language that is not well known in the world. For example if you original language is Finnish and you localize to English, German, French and Japanese it is useful to set the default language to English. In that case when ever there is no German, French or Japanese translation Sisulizer is using English translation instead of original Finnish value. It is much more likely that the end user of the application in Germany know English than Finnish.

Translation fallback

Finally we have defined all the element to describe the translation fallback process that Sisulizer used when building localized files. Your Sisulizer project can contain several language columns that that in actually are the same language but represent language's different variations. The most common situation is American English and British English combination. The most of the words and strings are the same in both languages but there are situations where the spelling of American English differs from British English. How can you handle this in Sisulizer?

The best was is to include a neutral English (e.g. en) and use this column as a American English column. Then include also English (United Kingdom) column for British English. Translate all rows in the American English but only those rows in British English where the spelling differs from the American English. When Sisulizer creates localized files for British English it first uses translation from the British English column. If there are not translation then Sisulizer uses the translation in the American English column. If there is no translation then Sisulizer uses the translation in the column of default language. Finally if no translation is found Sisulizer uses the original value.

Exact match -> Partial match -> Default language -> Original language

Let's have an example. We have an Finnish software where the original language is Finnish. We localize this software to American English, British English, German, Swiss German and Japanese.

Language Description
Original language Finnish
Target languages English
English (United Kingdom)
English - Engineering
Swiss German
Default language English

We have the following rows in the Sisulizer project.

Original English English (United Kingdom) English - Engineering German Swiss German Japanese
Väri Color Colour   Farbe  
Yksi One   1 Eins    
Kaksi Two   2 Zwei    
Kolme Three   3 Drei Drüü

When Sisulizer builds the localized files it uses the following values:

Original English English (United Kingdom) English - Engineering German Swiss German Japanese
Väri Color Colour Color Farbe Farbe
Yksi One One 1 Eins Eins One
Kaksi Two Two 2 Zwei Zwei Two
Kolme Three Three 3 Drei Drüü

Values written in bold typeface are got through translation fallback procedure.