• Command-line Tool
• Database Localization
• Delphi and C++Builder
• .NET
• Multilizer Components
  • IvResDLLDictionary
• Pseudo Translations
• Reports & Statistics
• Visual Studio .NET
• Visual Studio 4-6
• XML Files
• Concordance search
• Translation
• Obsolete documents

Multilizer components

Multilizer components are intended for Delphi/C++Builder developers that want to localize their software and make it truly multilingual. The components introduce a unique Dictionary-Translator Architecture for software localization.

Please see also the document describing how to migrate from earlier Multilizer versions to the current version.

Background

Multilizer components have been developed since 1995/96 until 2002/03 (Multilizer ("Innoview Multilanguage") versions 1.0-5.1). In version 6 components were not updated, because Multilizer's binary localization method was mature enough with it's accompanying localization API.

Binary localization was much easier and had less impact on source code.

However, feedback from developers has proven that there are situations where binary localization is far from satisfactory. That's the reason that components are re-introduced in 2006 and maintained to this very day.The latest version of the components now supports Delphi and C++Builder 2010.

Dictionary-Translator Architecture

Multilizer components localize the software by using the unique dictionary-translator architecture; translator components automatically translate forms on run-time using translations provided by the dictionary component.

Multilizer Localization Components include a complete set of components needed to localize any Delphi or C++Builder software. Based on the functionality, components are grouped in following 3 categories:

Dictionary components provide Translator components with translations. Multilizer Localization Components include several dictionary components each of them having different sources for translation:

• IvResDLLDictionary Just specify the ResDLLPath property to resourcedlls and the dictionary can use their translations. (Read more)
• IvBinaryDictionary This dictionary uses the Multilizer Dictionary File (.mld file).
• IvUserDictionary This dictionary allows user-specified source for translations.
• IvTestDictionary Use this component to test how a localized software would look like.

Translator components translate the user interface just before the form becomes visible. User can specify which properties are translated and which not.

Module components take care of translating complex properties and non-vcl-forms that can't be translated with translator components. For example common-dialogs are translated by IvDialogModule. Developers can inherit their own modules for translating just anything in the application.