Selected Customers

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

4/27/2017

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

Sisulizer 4 Build 366

3/1/2017

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

10 Years Sisulizer

8/5/2016

Celebrate and save Big. [...]

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. [...]

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

 

Skip the typical software localization beginner's traps

Character Sets

Using a different language often means you must consider another character set. Especially if English is your first language, you might think that you need only 128 characters. However, many languages use special characters:

  • French accents, like in à, é, î, and ç,
  • Spanish punctuation, like the reverse question mark ¿,
  • Umlauts, like ß, ä, ö and ü in Germany or Finland,
  • Other umlauts, like æ and å used in Denmark, Norway or Sweden.

The list is endless.

So how would you feel if you couldn't use characters from your own native alphabet? What if your name is Henry, and you couldn't write your name, because a Russian software developer would not support the letter H as his/her language does not use that letter? Would you write enry instead? Or would you directly uninstall the application?

What you need to do

Use Unicode string handling in your application, whenever possible. This allows you to support all languages and character sets. The Unicode Windows API can help you accomplish this.

If your development environment supports only ANSI character sets, you should ensure that you do not restrict your input to the first 128 characters. For Delphi, and classic VB there are third-party unicode components available. DotNet developers already have unicode.

How does Sisulizer support you

Sisulizer itself is a unicode application. You exchange data with your translator without the hazzle of conversions. Sisulizer does the job for you. Period.

You can localize both, ANSI and Unicode applications using Sisulizer. No need to change the tool. Sisulizer does it all.

Sisulizer comes with integrated support of the following third-party unicode tools: LMD ElPack and TMS Unicode Component Pack for Delphi; Hexagora UNICODE components for Visual Basic.

Software localization traps