#552 VIAddVersionKey causes problems with localized installers

[Anonymous]

The default language is supposed to be the first language file loaded, and that is the case, except when using VIAddVersionKey.

For example, if I have a French installer and add anywhere in the script the following:

VIAddVersionKey /LANG=1033 "FileVersion" "1.0.0.0"
VIProductVersion "1.0.0.0"

.. then the installer thinks it should have English (1033) langstrings and throws a bunch of warnings. Shouldn't it be possible to add English binary resources without a langstring table using the instructions above?

The problem can be reproduced using the MultiLanguage.nsi MUI example script. Simply comment out the !insertmacro for MUI_LANGUAGE_ENGLISH and then add the above VI instructions to the bottom of the script and compile to see the list of warnings.

My e-mail address is amayo (at) divxcorp [dotcom].

[Nobody/Anonymous]

Logged In: NO

Additionally, English will become the default language, i.e. VIAddVersionKey acts as if it were loading the language file.

Typo in my original summary: MUI_LANGUAGE_ENGLISH should be MUI_LANGUAGE "English"

[Amir Szekely]

Logged In: YES
user_id=584402
Originator: NO

Thanks, fixed.