Selected Customers

10 Years of Sisulizer

10 Years of Sisulizer


Time to celebrate 10 years of software localization made easy.

"Over the past 10 years, we’ve seen 15 Delphi, 9 .NET, 5 Windows, a bunch of Java, Database, Android and other platform releases.

Each of them came with new challenges and opportunities for developers doing software localization. Sisulizer’s goal was and is to hide the nasty details and make localization as easy as possible so that you, our loyal customers, can localize software on the newest platforms first.

For 10 years, you’ve helped Sisulizer become the optimal software localization experience. Thank you! Your valuable and continuous feedback has motivated and empowered us to stay ahead of the competition.

And now, back to work. New platform releases on the horizon are waiting to be supported. Time to localize and open up to new markets!"

--- Your proud Sisulizer Team

Buy Now

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 363 released

7/26/2016

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

Delphi Berlin, Android, Project Merge...

5/6/2016

Build 360 [...]

Delphi 10, VS 2015, .NET 4.6

10/14/2015

Up-to-date for the future. [...]

Windows 10, Delphi XE8

4/28/2015

Ready for the future. [...]

Welcome 2015, Welcome VS 2015

1/16/2015

Improved .NET support and more. [...]

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

 

How to avoid Mojibake

Working with Code Pages in Windows

Background Info: Use virtual machines for different code pages

Use virtual machines for different code pages

The following information describes how you can learn how to change the system code page. This is simple; however, Windows asks you to reboot your machine every time. This is time-consuming and might interrupt your work.

A solution to this is to use a virtual machine, such as Virtual PC or VMWare. Set up multiple virtual PCs with different code pages for the languages you want to support and test without rebooting. While the market even offers free editions all you need is some free space on your hard drive to follow this practical hint.

Applications designed on Win32, depending on the development language or IDE, use either UNICODE or ANSI. ANSI applications, like programs designed with Delphi and C++ Builder, use code page encoded strings and a non-Unicode version of WIN32 API. Why do you have to know this information?

There are several different code pages. English and most other Western languages use code page 1252. Japanese uses 932, Russian uses 1251, and so forth. To render an ANSI string correctly, the application must have the right system code page. This page is the default code page of the system. In Windows ME, 98, and 95 you cannot change the system code page.

However, in Windows 8, 7, Vista, XP, 2008, 2005, 2003, 2000, and NT, you can change the system code page.

How do I know if the system code page is not right?

Usually, you will see the problem when trying to run your application. If strings in the menu items and components do not show correctly and display gibberish, the system code page is not right. This effect is called Mojibake.

The following screenshot shows a Japanese application that is run on a computer where the Japanese system code page is active.

Dialog with Japanese chars

Everything is fine here.

Dialog with scrambled chars

However, if the same application is running on a computer that has the Western code page, the application appears like this. As you can see, hopefully without the help of your Japanese colleagues, the strings are mojibake ("character changing" = gibberish).