Three simple steps to localize
C#, VB.NET, Delphi, FireMonkey, C/C++, Android, VB, Java, XML, Databases, HTML, HTMLHelp, ...
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
(english)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]
.NET Assembly Source | VCL
This sheet is visible if the assebly file has been created using Delphi and VCL.NET.
Options
Specifies how VCL forms are localized. Possible options are:
| Value | Description |
|---|---|
| Set BiDiMode property | If checked Sisulizer changes the BiDiMode property when creating Middle Eastern forms. If the original value is bdLeftToRight, Sisulizer changes this to bdRightToLeft. This is applied only if ParentBiDiMode property of the same component is False. |
| Mirror forms | If checked Sisulizer mirrors the form and its sub components when creating a Middle Eastern form. Uncheck this if you call TForm.FlipChildren method before showing the form. This is because FlipChildren automatically mirrors the form. |
| Scan only forms from RcData | If checked only form data is scanned from RcData resources. |
| Separate lines | If checked each line of a Lines.Strings (e.g. TMemo.Lines) property is handled as a separate item. If unchecked the whole content of the List property is handled as a single item. |
Form scaling
Specifies how the localized forms are scaled. VCL has a build-in form scaling. It works like this: When VCL loads a form it checks if the runtime height of the font is different to the design time height of the form. If it is VCL scales the components on the form. Unfortunately it does not scale the width and height of the form if the BorderStyle property is set to bsDialog. As a result some of the components may be cut off. To fix this Sisulizer has a form scaling option. Possible values are:
| Value | Description |
|---|---|
| Disable scaling | If checked Sisulizer sets the TForm.Scaled property to False. This disables the build-in form scaling of VCL. |
| Scale forms | If checked Sisulizer scales the width and height of the form. This scaling is done properly for every form no matter what are the property settings. Unfortunately the build-in VCL scaling is always based runtime fonts of the OS where the application is running. When Sisulizer does the scaling on the developers computer this might be different than the actual runtime scaling. |
| Ignore | If checked Sisulizer does not change the Scaled, Width or Height properties. |
Read more about .NET localization.