This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Base OS language Vs Language Pack issues
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
Feb 28, 2011
09:35 AM
Base OS language Vs Language Pack issues
I have a multi language installer, which I want to detect the 'UserLanguage' and install the necessary language specific components. The problem I am finding is that InstallShield can only detect the base OS language, not the language pack the user is using. So base OS = English with a French language pack installed results in the installer thinking it is English.
Well for a full UI install, I simply show the language selection dialog at the start, it isn't ideal, it defaults to English, but the user can then select French.
However, for a silent install this is no good - but then there is no UI right? I just need to condition out the components after making an API call to get the UserLanguage, this involves catching 16 different Language codes just for French, 18 for English, 22 for Spanish, 1-5 for various other languages. 14 languages in total, done and I thought I was rocking.
So I silently install this on an English OS with a French language pack and sure the right (French) files are installed, but the shortcuts are in English and additionally when you uninstall from the ARP there are a couple of dialogs that pop up which again are in English. I should add a note about the shortcuts, in that they are seperated from the files to allow the user to choose whether to install the shortcuts on a UI install, but they are in fact from language neutral components anyway.
Any ideas how to set the installer language to the language pack rather than the OS language. My understanding is that the language selection is made from the Setup.exe wrapper before you can run any embedded CA making an API call to get the language code. So is the only solution to run a bootstrapper app that makes the API call and then calls the setup with the /L
Well for a full UI install, I simply show the language selection dialog at the start, it isn't ideal, it defaults to English, but the user can then select French.
However, for a silent install this is no good - but then there is no UI right? I just need to condition out the components after making an API call to get the UserLanguage, this involves catching 16 different Language codes just for French, 18 for English, 22 for Spanish, 1-5 for various other languages. 14 languages in total, done and I thought I was rocking.
So I silently install this on an English OS with a French language pack and sure the right (French) files are installed, but the shortcuts are in English and additionally when you uninstall from the ARP there are a couple of dialogs that pop up which again are in English. I should add a note about the shortcuts, in that they are seperated from the files to allow the user to choose whether to install the shortcuts on a UI install, but they are in fact from language neutral components anyway.
Any ideas how to set the installer language to the language pack rather than the OS language. My understanding is that the language selection is made from the Setup.exe wrapper before you can run any embedded CA making an API call to get the language code. So is the only solution to run a bootstrapper app that makes the API call and then calls the setup with the /L
parameter?
(1) Reply
Mar 01, 2011
12:30 AM
Nick Umanski wrote:
So is the only solution to run a bootstrapper app that makes the API call and then calls the setup with the /Lparameter?
I think so. As far as I'm aware,language detection function is not customizable. And sometimes this function doesn't work fine....