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.