Selected Customers

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


Flash Localization

Adobe Flash 8 and later has a feature that can store the strings in a separate XML file. Actually these file are XLIFF files but because Flash can not properly import translated data from an XLIFF file, you have to use XML localization. Flash localization process is following:

  1. Add the languages that you want to support. Flash creates a language file under a language specific sub directory. If you original Flash file is Sample.fla, Flash will create <langcode>\Sample_<langcode>.xml file for each language. For example en\Sample_en.xml contains the English strings.
  2. Add all strings of your Flash document to a string panel. This makes Flash to put the strings to the language file(s).
  3. Use Sisulizer to localize the main language file. This is the language file of that language that you use to edit the Flash document.
  4. The build process if Sisulizer creates the localize XML files. For example if you added en\Sample_en.xml to the Sisulizer project the output files would be en\<langcode>\Sample_en.xml
  5. You have to choices to import the localized language files to Flash. The first is to use the String panel and import each localized language file to the project. Another is to copy the localized files to their localziation. For example copy the Finnish file en\fi\Sample_en.xml to fi\Sample_fi.xml. Next time you start Flash it uses the updated strings.