"that install a resource under the same name and target location. If a resource must be duplicated in multiple components, change its name or target location in each component."
As I understand, the very consequence for creating a localized installer is that for a given set of localized code files (.exe, .dll, ...), which share the same name and target (but with different language identifiers) always multiple .msi packages (or one .msi and multiple transforms) must be created for every language to be included.
Owning InstallShield Professional Edition (and not the Premier Edition, which is capable of creating multiple localized transforms), I want to ask, if Community members would endorse localizing a single .msi file (where the user selects the language to install in the GUI) by
* authoring different components with equal file names and equal target, but different language codes for each file, in one .msi file (thus breaking component rules)
* and setting the ProductLanguage Property to the language selected by the user or (in case of repair/modify) to the language already installed,
so that files will be installed correctly (see "File Versioning Rules" - it states that the product language is used, when file versions are equal. I suppose the doc is referring to the corresponding property, but also in the stream file info of the final file and in the project setup of the uncompiled project (I don't know where this will be used) language identifiers are present and configurable).
I understand that the ProductLanguage Property will not reflect any more the language of the GUI (which can have side-effects concerning GUI, see MSI docs for ProductLanguage Property, which I could tolerate) but the installation should be carried out correctly.
Edited by Pizzero, 20 June 2008 - 14:06.