Advanced Installer has the ability to build MSI packages in various languages.

Selecting additional build languages

Check the check-box button next to the desired language in the tree. For each language a separate MSI package will be built with the code page set to the default ANSI code page of that language.

TipMac OS X has a native support for multi language bundles so the resulted package will contain the translations for all languages.

NoteThe languages must be specified independently for each build. You can select the desired build in the toolbar builds combo. This option is enabled only if several build are defined.

The language in which the project was created in the Start Page is set as default. This language must be used by at least one build. Any build must have at least one language. The languages are grouped by their relation.

NoteEach language increases the package size with about 40 - 50 Kilobytes (depending on the strings it contains).

Creating a single multi-language package

You can choose to create a package that contains all the build languages by selecting the “Create separate packages and a multi-language package” option. This package will be created in the "\all" sub-folder of the folder where the project is build. If you need only the multi-language package you can speed up the build process by selecting the “Create only a multi-language package” option.

When the package is installed the language will be selected according to the regional settings on the target computer. The interface language of the tools that Advanced Installer uses (Setup, Java Launcher and Updater) is selected according to the Windows operating system's language.

Filtering visible build languages

By default, only selected languages and languages with translations are showed. You can choose to only see the selected languages or all the possible languages (that is the ones without translation as well).

Warning!If you select a language without translations build in, Advanced Installer will try to get the translation strings from the closest related language. This may be or may not be what you want. The Neutral language (ASCII US English) is used as the parent of all languages and generic fall back.

Translations

When translating a package in another language, Advanced Installer will look for the corresponding strings in one of the specified translation dictionaries. You can add more dictionaries to the project in the Translations section.

If you select at least one additional build language (other than the default project language), two abilities will become available:

  • Specifying which parts of the project will be translated in the Localization Options Dialog.
  • Generating a dictionary containing just the strings that need to be translated into the build languages. Only the project parts selected for translation in the Localization Options Dialog will be included in the generated dictionary.

Topics