XLIFF Settings

Use this dialog to configure XLIFF settings.

Fonts

Specified the default localized fonts to be used in XLIFF files.

Each script has the default font to be used in the localized items. This list contains the default fonts.

Edit

To modify a font data select the script that you want to modify and press Edit.

Import

You can import font data from a font file by pressing the Import button and browsing the font file.

Export

You can export the font data to a font file by pressing the Export button.

Components

Components sheet contains the component mapping list. Sisulizer uses its own visual components to render visual components, forms and dialogs. In order to properly draw the components Sisulizer needs to know the type of the component (i.e. label or button or check box). Component mapping performs this. It is used with platforms using components such as .NET, Delphi, C++Builder and Visual Basic. The purpose of the mapping is to give Sisulizer information about components that applications use.

By default Sisulizer contains mappings for all the standard component of the platform plus the most common 3rd party components. Sisulizer can localize any other component as well even if has not been mapped. However if the component is unmapped Sisulizer can not show it visually correct on the form editor but it shows the component and a pink box having "Click to map" text.

To map the component click the Click to map text and choose the component type. Mapping is not mandatory but it makes Sisulizer to show visual items better.

Each row in the component mappings list contains a mapping of one component. The mapping contains the following properties:

Class name

The class name specifies the class name of the component. For example the standard label component is TLabel in VCL and System.Windows.Forms.Text in .NET.

Component

Sisulizer component type. Sisulizer contain a collection of visual component type. Select the type that is best match to the component type. For example if the component class name contains a label component (TMyLabel) the best choice would be Label.

Status

Status column tells the status of the mapping. The possible values are:

Properties

By default Sisulizer extracts all string-typed properties and the properties that needs to be extract to get the visual information. Such kind of properties are for example left, top, width, height, color, font, input method and reading order. In most cases this is just enough to properly localize a component. However in some cases the component could contain a non-string-typed property that needs to be localized as well.

Editing mappings

Press Add to add a new mapping. Press Remove to delete the selected mapping. Press Edit to edit the selected mapping.

Press Import to import mappings from a mappings file. Press Export to export current mappings to a mappings file.

Press Restore to restore the default properties to the selected mapping. Press Restore All to restore the default mappings values.

For example the component might contains Mirrored property that controls the layout of the component. When localizing to a bi-directional language such as Arabic or Hebrew this property should be set True. In order to localize the property you need to get the property value to the project grid first. To do that add the property name to the property list as an included property. Next time you scan a project containing source file that uses such a component the Mirrored property will be scanned.

Some components contain string properties that should not be localized. For example most database components contain table name, SQL statements or connection strings. You can disable scanning of these properties by adding them to the properties list as an excluded property.