The language page is where a user manages multiple languages for the installation. While Windows Installer does not support multiple languages in a single installation,
the use of transforms can provide a seamless localized installation experience.
It is howerver recommended that a separate installation be created for each language so as to minimize the
download time and simplify distribution.
There are several languages already available with Install Time's™ themes. Select any of the available languages and import them into your project to produce a localized installation.
Language options include:
• Build: True indicates that the localized install will be build when compile is selected
• Code page: Code page for the output MSI. Windows Installer does not support Unicode code pages.
• Language Code:Language code is used to set the Template Summary value in the Windows Installer package
• Name: name of the language edition being built.
• Output File: If it desired to have the localized install build into a different folder, select that folder here. If this is blank, the localized install will be built in the same directory as the default language install
NOTE: the language page can be used to create multiple outputs using the same language. For instance if installation branding was directed to different customers you might have a single install made for company A and company B but are unique in their installation experience. perhaps the title would say "This widget was created for Ford Motor Company" and the second one might say "This widget was created for General Motors". while the underlying installation is the same, the user experience is more attractive to the individual customer.
Select add to create a new localized installation copy. Select the "build" checkbox to include this build automatically when compiling.
Removes the selected localized copy from the project.
Select Import to add the translated strings to the project.
Select Export to create a resx file that can be translated into a the language of choice and imported for inclusion into any project.
Export options include:
• File Name - The name of the resx file that will be created.
• Export only strings that require translation - Translation managment is handled internally so that when the default language is changed the localized langage is marked as requiring translation. selecting this option will ensure that you do not incur undo translation costs and only send the translator what you require them to translate.
• Export File names and other non-Interface strings - at times you may want to either dispaly items in custom actions or change the file name to a localized instance. While this is not typical select this option to have these strings translated.