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
- :
- Code Page issue in the Project Name
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
Apr 22, 2009
10:01 AM
Code Page issue in the Project Name
I've got a InstallScript MSI project whose project name is "Project360°". Note that the name includes the degree sign. For the ten languages we currently support, there is no problem. But now were are looking to support Chinese. The Chinese Windows Code Page does not include the degree sign, so when the user runs the installer, they get an error that says “Error reading setup initialization file.” I assume this is because the project name appears in the setup.ini file.
What can I do to work around this? I've looked for a way to run the installer in Unicode, but that doesn't seem to be an option for InstallScriptMSI projects.
Is there a way to put a condition on the Project Name so that it could have the degree sign if it is supported and omit it if it is not?
What can I do to work around this? I've looked for a way to run the installer in Unicode, but that doesn't seem to be an option for InstallScriptMSI projects.
Is there a way to put a condition on the Project Name so that it could have the degree sign if it is supported and omit it if it is not?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 22, 2009
10:32 AM
Is the degree sign included in the name of your .msi file? If so, try removing that, for instance by using the MSI Package File Name field on the Product Configuration (Releases view). As an aside, note that you cannot change the name of your MSI file during a minor upgrade.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Apr 22, 2009
11:04 AM
The isssue isn't the name of the msi file. The issue seems to be that in the setup.ini file, there is an entry that says:
Product=Project360°
Product=Project360°