Selected Customers

Specials run until 9/30/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


Android Localization

Android is a mobile operating system from Google. Each Android application can contain several resources such as user interface, strings, images, animation and XML. Sisulizer can localize all Android resource types including HTML, XML and text files stored as raw resources.

Android application are deployed as APK files. An APK file contains compiled code and compiled resources. When you use binary localization you don't need source codes at all and you don't have to recompile anything. Sisulizer reads the orignal application file (.apk), extracts resources from the file, and finally creates localized application file(s). Each output file contains resources in one language or one output file contains resources in all languages that you support. A localized single language application is similar to the original application but the original resource data has been replaced with the translated ones. A localized multi language application contains the unchanged original resources plus set of localized resources. It is up to you which file you create and deploy. A single language application files are smaller because they contain resources in one language only. A multi language application files are easier to deploy because you can deploy the same file to every market area.

Sisulizer supports two different methods to localize Android applications. The methods are:

Application file localization

When using the application file localization user selects an application file (.apk) to be localized. Sisulizer scans all the resource data from the application including string, layout and image data. On the build process Sisulizer creates the localized application files containing localized resources.

Values file localization

When using the values file localization user selects a values file (.xml) to be localized. On the build process Sisulizer creates the localized values files. You have to add the localized folders into your Android project and recompile your project.

Signing applications

All Android applications must be signed. If an application is not signed Android OS will not install it. In order to sing an application you need to have a key. You can do your key yourself. There is no need to get it from a certified key provided. There are two kind of keys in Android. One is the debug key. This is a temporal key that works only on emulator. You can not deploy applications signed with debug key. The password of the debug key is always the same so there is no need to store password or ask password them. If you use Eclipse it automatically debug signs application before installing in to the emulator. Sisulizer can also sign the application package files it creates. Use the Signing sheet of the source dialog to configure sign settings. Read more about signing from Android documentation


Sisulizer's Android\Converter directory contains a sample that shows how to localize an Android application.