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
- :
- Filenames with Japanese characters are corrupted during build or install (basic MSI)
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
‎Dec 17, 2013
01:07 PM
Filenames with Japanese characters are corrupted during build or install (basic MSI)
I have an installer which includes a number of files with Japanese translated names (hence Japanese characters). I'm running 2013 Premier which is supposed to support Japanese among other languages for installation. However, upon installation on a Japanese Windows VM (Win 7 x64 or Win 8 / 8.1), these filenames have apparently been butchered. What ends up coming out are filenames that look like this: (apparently they can't be copy/pasted, but picture 4 rectangles squeezed together)
I checked to see how these files are treated in the Direct Editor in IS. The FileName(s255) and ISBuiuldSourcePath(s255) tables show the Japanese, though the File(s72) key field is unable to handle these, so all the keys end up as something like "File5".
This is quite a serious issue for our Japanese localized version which we plan to release soon.
Any advice would be appreciated.
I checked to see how these files are treated in the Direct Editor in IS. The FileName(s255) and ISBuiuldSourcePath(s255) tables show the Japanese, though the File(s72) key field is unable to handle these, so all the keys end up as something like "File5".
This is quite a serious issue for our Japanese localized version which we plan to release soon.
Any advice would be appreciated.
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 18, 2013
08:30 AM
Try applying the InstallShield 2013 service pack 1 if you haven't already and see if that resolves the issue.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 18, 2013
08:55 AM
Did you set the "Build UTF-8 Database" to yes?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 18, 2013
06:16 PM
It looks like the "Build UTF-8 Database" release setting was our problem. Thanks for the help!