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
- :
- Re: Multilingual or Unicode (Premier or Pro)
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 04, 2009
03:15 PM
Multilingual or Unicode (Premier or Pro)
We are evaluating InstallShield 2010 Professional. My requirement is to develop separate installations of our software product for English, Chinese, Japanese and Russian. I do not need to support all of these languages in a single project.
Using Pro, I have been able to export localizable strings (using the English language which is the only selectable option), convert the text file to Chinese, then re-import the text file. This appears to work. (I understand I will have to create individual projects for each of the languages.)
Is this a valid approach? Will my Chinese customers get the expected results when they install my project, even though the underlying language (code page) is English?
If the answer is No, then why is Unicode support available to the Pro edition?
Thanks,
Joe
Using Pro, I have been able to export localizable strings (using the English language which is the only selectable option), convert the text file to Chinese, then re-import the text file. This appears to work. (I understand I will have to create individual projects for each of the languages.)
Is this a valid approach? Will my Chinese customers get the expected results when they install my project, even though the underlying language (code page) is English?
If the answer is No, then why is Unicode support available to the Pro edition?
Thanks,
Joe
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Sep 08, 2009
03:12 PM
What you describe sounds like it should work, but we do not explicitly test it, and you'll be stuck with that manual import step each time you switch languages. By contrast, Unicode support is intended to display strings that mix code pages (e.g. to allow a Russian product name in an English installation), and support installing files (and shortcuts and more) with names that either individually or collectively don't fit on a single code page. The latter uses in particular (files, etc.) were considered central for both the Professional and Premier editions.