Update to Version 3

Sisulizer version 3 is a paid update recommended for all Sisulizer customers.

Still using Sisulizer 1.x or Sisulizer 2008/2010?

Time to update to version 3 now and profit from all new features in version 3.

Specials run until May, 20 2012

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

Social Networks

Please click this facebook button if you want to share this page with friends

Share

(english) (german)


Please click this Google +1

button to give Sisulizer a positive vote in Googles new voting system.

Thank you very much.

Selected Customers

Software Localization News

Version 3 Build 331 released

4/23/2012

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

Top News: Version 3

11/9/2011

Sisulizer version 3 out now. [more]

Tips & Tricks

9/30/2011

You are looking for tips and tricks around Sisulizer? [more]

Delphi Tage

9/8/2011

Delphi Tage 2011 in Cologne are sold out! [more]

Download Build 321

8/12/2011

Please us a download manager for your download. [more]

Import Wizard - Delphi

Use this sheet to specify optional files need to properly import Delphi binary file.

Project file name

Specifies a Delphi project file (.dpr). Use this if you have unit names having _ in their file names and those units use resource strings having also _ in their names. Otherwise Sisulizer can not determine the exact resource string context. For example if My_File.pas has the following resource string

resourcestring
  SMy_Sample_String = 'This is a sample';

It is highly recommend to specify project file. However Sisulizer can localize VCL applications without project files.

DRC file name

Specifies a DRC file that contains tables of all string constants declared by the resourcestring keywords. If you do no specify a DRC file then you have to select what context method is used with resource strings. Possible values are:

Context method Description
String value Sisulizer uses string values as context values. This is safe even if you modify and recompile your application. However if the application has the same text in two ore more resource strings this method brings only one row to the project file. So all instances of the same text will share the same row and you can no longer translate them in a different way.
Resource id Sisulizer uses resource ids as context values. This is potentially dangerous because it is very likely that Delphi compiler will change the resource strings ids next time you compile your project. This will cause lost of translations or switching of existing translations. Both are very hard to fix.

Because both alternative context methods have their limitation and dangers it is very much recommended to specify a DRC file. To create a .drc file choose Project | Options | Linking from Delphi and select Detailed in the Map file selection. In Delphi XE2 or later you can also turn DRC files on by checking Output resource string .drc file check box.