Selected Customers

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


Visual XML Localization

XML localization is very simple in Sisulizer because it is visual and safe. You just select what tags you want to localize. Sisulizer extracts the visual XML data and adds the translated tags to the project. When creating localized file Sisulizer creates an identical copy of the original XML file except it contains the selected tags in the target language.

Use the Tags sheet of XML Source Dialog to select what tags you want to translate and how to translate them. The following paragraphs describe more about your choices to configure how to interpret and localize certain kinds of XML elements.

Embedded tags

In some case several XML tags should be translated as a single entiry. For example you might have text data that contains formatting tags. The following tag contains a plain text:

<text>Finland is the most northern country in the world</text>

If you want to underline the the word most you might store the data in the following way:

<text>Finland is the <u>most northern</u> country in the world</text>

This will break the sentance in three different parts: "Finland is the ", "most" and " country in the world". To translate them separately is impossible or at least very hard. A better choice is to treat the how stuff as a single translation unit.

If you select an XML tag that has sub tags Sisulizer automatically combines the tag into single element and adds that to the project.

Source code

Sometims XML contains source code. For example there might be script code emebedded inside an XML tag. In such case Sisulizer can use its source code parser to extract only strings from the code. Transalating only strings of the source code is much easier and safer that translating the whole source code. Sisulizer can detect if an XML element contains source code. If the detection result is not right or it fails you can set the source code type by right clicking the node in the Tags sheet and choosing the source code type from the popup menu.

<sl>\XML\code.xml contains a sample XML file that contains embedded source code.

Images and binary data

Just like source code your XML files might contain image or binary data. Sisulizer can read both hexadecimal encoded and base-64 encoded image/binary data. Right click the node and select the right type.

<sl>\XML\vehicles.xml contains a sample XML file that contains image data.


There are two kinds of special attributes: context and localize attributes. You can use context attribute to give content to elements. You can use localize attribute to control element by element what to localize.


Sisulizer's XML directory contains XML samples.