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
- :
- InstallAnywhere
- :
- InstallAnywhere Forum
- :
- Re: Japanese License in License Panel
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 20, 2012
04:08 PM
Japanese License in License Panel
Hi -
I'm trying to display a Japanese version of our product license agreement during the install in the license agreement panel. I've succeeded in getting it to display on Japanese installs on both Windows and Linux. On Linux, it looks great. On Windows, it does not display correctly at all.
The file is a UTF-8 file, but the Windows panel doesn't recognize it as such. The Linux panel shows it fine.
How do I get InstallAnywhere on Windows to display the file correctly?
- Scott
I'm trying to display a Japanese version of our product license agreement during the install in the license agreement panel. I've succeeded in getting it to display on Japanese installs on both Windows and Linux. On Linux, it looks great. On Windows, it does not display correctly at all.
The file is a UTF-8 file, but the Windows panel doesn't recognize it as such. The Linux panel shows it fine.
How do I get InstallAnywhere on Windows to display the file correctly?
- Scott
(10) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 02, 2013
08:03 AM
If I am not wrong, you have to change your windows system locale to Japanese.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 02, 2013
09:30 AM
I agree, and our machines are set to the Japanese locale. But the problem persists.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 02, 2013
11:45 PM
Could you please post a snap shot of the screen?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 03, 2013
12:52 PM
Sure. Here's the installer running on Linux:
![](/legacyfs/online/vb/9892_IA_Linux.png)
And here's how it looks on Windows 7:
![](/legacyfs/online/vb/9893_IA_WIN7.PNG)
The display on Windows is identical to what I see when I type it out on Windows, i.e., the text is treated as ANSI. But the IA docs say files are treated as UTF-8 by default. I had hoped that would mean it would display correctly, but clearly not.
- Scott
![](/legacyfs/online/vb/9892_IA_Linux.png)
And here's how it looks on Windows 7:
The display on Windows is identical to what I see when I type it out on Windows, i.e., the text is treated as ANSI. But the IA docs say files are treated as UTF-8 by default. I had hoped that would mean it would display correctly, but clearly not.
- Scott
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 04, 2013
05:05 AM
Yes there seems to be a difference in chars displayed.
I think it is some thing to do with the OS rather than IA.
I'm sorry, i have run out of ideas.
My sincere apologies for not being of any help to you.
I think it is some thing to do with the OS rather than IA.
I'm sorry, i have run out of ideas.
My sincere apologies for not being of any help to you.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 24, 2013
03:37 AM
Maybe that was an issue with IA 2011. Have you tried to rebuild your installer with IA 2012, in order to see if you reproduce the issue?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 25, 2013
08:59 AM
pv7721 wrote:
Maybe that was an issue with IA 2011. Have you tried to rebuild your installer with IA 2012, in order to see if you reproduce the issue?
No, not yet. We'll be moving to 2012 at the end of the month, and I'll try it again with that. Thanks for the suggestion.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 19, 2014
12:20 PM
Hi,
I'm having the exact same issue using InstallAnywhere 2013 version.
Works well on Linux but not on Windows.
Did you (or anyone else) got a solution for this issue?
--Jerome
I'm having the exact same issue using InstallAnywhere 2013 version.
Works well on Linux but not on Windows.
Did you (or anyone else) got a solution for this issue?
--Jerome
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 19, 2014
12:47 PM
Ok, running some more tests, it looks like it works well with HTML files but not with TEXT files.
So I'll use html license agreements
So I'll use html license agreements
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 24, 2014
03:52 AM
Support points me to this link: http://flexerasoftware.force.com/articles/en_US/PROBLEM/Q202182
Workaround
The issue can be worked around in one of two ways:
1. The localized file can be saved in ANSI encoding. Note that the localized file must be saved on a machine matching whose local matches the local of the file; otherwise, corruption of the file may result.
2. If the localized file is UTF-8 encoded, the Java System Property file.encoding can be set to UTF-8. This property can be set by specifying the following value under project->JVM Settings->Installer Settings (in InstallAnywhere 2011).
-Dfile.encoding=UTF-8
As an alternative, the following environment variable can be set prior to launching the installer:
_JAVA_OPTIONS=-Dfile.encoding=UTF-8
--Jerome
Workaround
The issue can be worked around in one of two ways:
1. The localized file can be saved in ANSI encoding. Note that the localized file must be saved on a machine matching whose local matches the local of the file; otherwise, corruption of the file may result.
2. If the localized file is UTF-8 encoded, the Java System Property file.encoding can be set to UTF-8. This property can be set by specifying the following value under project->JVM Settings->Installer Settings (in InstallAnywhere 2011).
-Dfile.encoding=UTF-8
As an alternative, the following environment variable can be set prior to launching the installer:
_JAVA_OPTIONS=-Dfile.encoding=UTF-8
--Jerome
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)