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: Support for non-English characters in install path
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
Jan 03, 2017
12:39 AM
Support for non-English characters in install path
Hi,
We need to support installation of our product into directories with unicode characters in the path ( non-English multi-byte). We are using IS 2013 and the installation summary shows '?????' as the install path and the installation fails when it tries to access the install path.
I read that the unicode support has been added since IS 2015. I am trying the IS 2016 trial version but the problem persists.
How do I enable the non-english character support in my Installer?
Thanks
Shobha
We need to support installation of our product into directories with unicode characters in the path ( non-English multi-byte). We are using IS 2013 and the installation summary shows '?????' as the install path and the installation fails when it tries to access the install path.
I read that the unicode support has been added since IS 2015. I am trying the IS 2016 trial version but the problem persists.
How do I enable the non-english character support in my Installer?
Thanks
Shobha
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 04, 2017
10:21 AM
I'm not sure how to do it in InstallShield. In WiX (Windows Installer XML from Microsoft) you can set the code page in the element.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unicode-characters-in-MSI-setup-package-td710445.html
Must be a way to do that in InstallShield, too.
Maybe this is part of the answer?
http://helpnet.installshield.com/installshield22helplib/helplibrary/CodePageReqs.htm
Chad