Component Mapping

Sisulizer is a 100% Windows application. Even it can localize several other platforms (including XML, HTML, .NET, Java, etc.) it never requires any runtime code such as .NET common language runtime or Java virtual machine. This choice was made to make it sure that every single translator can use Sisulizer without installing dozens of runtimes or 3rd party libraries into his or her computer before starting the translation task. In fact Sisulizer application file, Sisulizer.exe is a single file that runs without any installation or registry settings and requires no DLL or ActiveX.

To support several visual platforms without platform's runtime code Sisulizer uses its own component to show user interface elements such as labels, edit fields, buttons, check boxes, etc. Sisulizer has over 100 build in component types covering all kind of components from basic labels to complex grids. When drawing component on the visual editor Sisulizer needs to know the type of the component. Component mappings is for this. It is a collection of mappings where each mapping maps the original component to Sisulizer's own component. For example .NET's label System.Windows.Forms.Label, VCL's label TLabel, and Visual Basic's Label are all mapped to Sisulizer's Label component. Every platform such as .NET, VCL, Visual Basic, etc. has its own mappings collections. By default Sisulizer's mappings collections contain all the standard components of the platform (e.g. VCL components or .NET components) and the most popular 3rd party components. You can add new items to the mappings collection by choosing Tools | Platforms | <platform> and selecting Components sheet. This contains global mappings collection. A project releated mapings collaction can be edited by choosing Project | Components.

If you use a component that is not present in the mappings collection you use an unmapped component. In that case Sisulizer tries to automatically map it based on keywords. For example every component that has word Label in its type name is most likely a label and it is mapped to label. You can add new items to the keyword list by choosing Tools | Platforms | <platform> and selecting Keywords sheet. If the automatic mapping goes wrong you can always correct it by using the mappings dialog. If Sisulizer can not automatically map a component it remain unmapped and it is drawn as a light pink box in the visual editor. An unmapped component also contains "Click to map component" text. You can map it by simple clicking it and the Map Component dialog appears. It lets you choose the right component mappings.

To make mapping easier the Log will contains an entry for each unmapped component type. Select a line and Sisulizer selects an instance of the component. Click the component to map it.

Once you have mapped a component Sisulizer remembers the mapping and you do not have to map the same component again in this project or in new projects.

Important

Even if the component is unmapped or the mapped component does not look 100% right Sisulizer still finds all strings belonging to it and makes it possible to fully localize the component.

3rd Party Components

Sisulizer contains most 3rd party components pre mapped so you do not have to map them. However if you use some rare or new 3rd party component you have to map them. You can also contact Sisulizer's support to ask us to pre map the component.

We also have third party components support program where most component vendors have already joined. If the vendor of the component that you use is not already joined please contact them and ask them to join.