|
|
||
MSI Factory
This dialog lets you add a pre-made existing language to the project, or to define a new language based on an existing one.
A list of pre-made languages that are available for use in your project. The availability of the language is dependent on the UI set that you are using in your project. Language translations are based on the available screens in a given UI set. If a language that you want is not found here, you can create a new language translation by selecting an existing one and then editing its properties below. This will ensure that you have a template to work from when making your new language translation.
When you select a language from this list it will automatically populate the values in the fields below for you. Normally you only need to change the values if you are creating a new language based on another existing one.
The short name of the language. This value is arbitrary and has no meaning in terms of the installer database that is created. It is merely a label that helps you identify the language throughout the project.
The language identifier of the language that you are adding to the project. This value will set the language identifier for the installer database package. See the More Information links below for more details about language identifiers. Note that you can use the same language identifier for more than one language in your project if you want to use one or the other in different circumstances.
The ANSI codepage to use for strings in your installer database. Usually it is best to leave it as "0" (zero) so that it is set to be a neutral code page.
The full path and filename of the local language file (in XML format) to import the messages from. Note that this will be filled in by default if you select a pre-existing language. Even if you are creating a new language you should specify an existing language file so that the default message IDs can be created for you. When you click OK to add the language, it does a one-time import of the messages currently in the language file. The messages are then stored with your project and are not re-imported every time you build or open the project.
MSDN Online: Code Page Handling (Windows Installer)
MSDN Online: Creating a Database with a Neutral Code Page
MSDN Online: Language Identifier Constants and Strings
MSDN Online: Language Identifiers
MSDN Online: Locales and Languages
MSDN Online: Setting the Code Page of a Database
Learn More: Indigo Rose Software - MSI Factory - Buy Now - Contact Us