Selected Customers

Specials run until 10/31/2018

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

9/9/2018

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

.NET Support updated

6/14/2018

New in May 2018: [...]

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

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

 

FireMonkey Localization

FireMonkey is a new cross platform component library for Delphi. It has lots of similarities to VCL but is designed to supports several targets including WIN32, WIN64, OSX and iOS. Localization of a FireMonkey application is similar to localization of a VCL application. You add the original WIN32 application (.exe) or library (.dll) file into a Sisulizer project. Sisulizer scans the resources of the file and finally creates localized files or localzied resource files.

The biggest different between VCL and FireMoney localization is that compared to VCL you can have multiple target files. FireMonkey can have several target files: WIN32, WIN64, OSX, etc. When you create a project you only have to add one target file into Sisulizer project. Most often this is 32-bit Windows target but it can also be 64-bit Windows target. All other targets are added as platform files. Platform file is a file that Sisulizer handles like the main file (e.g the one you have added in to the project). Using this approach we eliminates the same resource items appearing multiple times. Starting from Delphi XE2 also VCL can have two target files. One for WIN32 and another for WIN64.

TLang

Delphi does not have a good localization support for FireMonkey. The platform itself is very much localization ready but Delphi IDE does not have any way to create the resource files for your application. Instead FireMonkey contains TLang component that provides very rudimentary localizartion support. It requires that you add TLang component on every form and manully maintain the translations of each forms. This is very time using and frustrating. You should not use TLang and you don't have to use it if you use Sisulizer. If you already have a project using TLang you don't loose any translation you have allready done. Just create a new Sisulizer project containing your application. Sisulizer automatically imports translations from each TLang component. Once imported you can safely remove TLang components. You won't need them any more.

Samples

Sisulizer's FireMonkey\Converter directory contains a sample that shows how to localize a FireMonkey application with multiple targets.