Custom Launch Condition for multi language packages - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

rho
Posts: 69
Joined: Tue May 12, 2009 1:22 pm

Custom Launch Condition for multi language packages

Hi,

we try to build an installer which supports english and german (one multi lingual package).
I added localized prereqs for german and english, and set the "Support only the following languages" to the english or german codes.

1. I found out, that I have to set EVERY sub language for english or german, too. Otherwise this package would not show up on a system configured with system locale "English (Ireland)". (That's lots of clicks with 12 prereqs.)

2. As there are prereq packages which are language independent, I have to set these packages to german and english language codes. (Even more clicks) Otherwise the language independent ones would show up, while the german/english packages would not be shown on a system configured to system locale = italian.

3. Running this installer on a "system locale = italian" - system, the bootstrapper is skipped and the main installation starts right away. This is useless, as all the prereqs are missing.
So I tried to add a custom launch condition on the Custom Launch Condition tab. It would look like this:

Code: Select all

SystemLanguageId = 1033 or SystemLanguageId = 2057 or SystemLanguageId = 3081 or SystemLanguageId = 4105 or SystemLanguageId = 5129 or SystemLanguageId = 6153 or SystemLanguageId = 7177 or SystemLanguageId = 8201 or SystemLanguageId = 9225 or SystemLanguageId = 10249 or SystemLanguageId = 11273 or SystemLanguageId = 12297 or SystemLanguageId = 13321 or SystemLanguageId = 1031 or SystemLanguageId = 2055 or SystemLanguageId = 3079 or SystemLanguageId = 4103 or SystemLanguageId = 5127
This is much too long for the condition field. :) I could set it in xml code, but I think this is a bad idea.

My question is: How can I get around this language problem?
German users should get a german installation, English users should get an english installation (+ the same for all other languages)
Or would you suggest to build two independant packages?

If I could set the prereq language like this:
german package -> "install if german"
english package -> "install if not german"
I could ensure that all prereqs would be installed.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Custom Launch Condition for multi language packages

Hi,
1. I found out, that I have to set EVERY sub language for english or german, too.
Please note that there aren't any sub-languages for a language. We show them this way because they are related and it's easier to select similar languages. From the Windows OS point of view "English (United States)" and "English (Ireland)" are two different languages. This is why the "Regional and Language Options" Control Panel applet shows all languages in a list.
If I could set the prereq language like this:
german package -> "install if german"
english package -> "install if not german"
I could ensure that all prereqs would be installed.
Since your package has language dependent prerequisites, the best approach would be to use separate installers: one for German and one for any other language. Using a single installer would be too complicated because there are many limitations (in Windows OS, Windows Installer and Advanced Installer) which need to be avoided.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”