JDK-4448053 : unlocalized screen on zh_TW Win95 installer
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.0.1
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_95
  • CPU: x86
  • Submitted: 2001-04-19
  • Updated: 2001-05-04
  • Resolved: 2001-04-30
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.0.1 1.0.1Fixed
Related Reports
Relates :  
JDK-4452391 - solaris native message i18n does not work right
Relates :  
JDK-4450488 - Unlocalised strings in Win2000 install, b16
Description
Tested bundle: 
javaws-1_0_1-fcs-bin-b16-win-int-19_apr_2001.exe

Tested environment:
Windows 95 (Traditional Chinese)

Problem found:
When the user tries to install javaws-1_0_1-fcs-bin-b16-win-int-19_apr_2001.exe on a system with no previous installation of JRE, the following message is displayed during installation in English:

"Bad installation. Error invoking Java VM (SysExec)."

This message should be displayed in T.Chinese. There is a localized resource file with this message translated:

javaws1.0.1_l10n/src/share/native/messages_zh_TW.properties
error.badinst.sysexec=\u5b89\u88dd\u932f\u8aa4\u3002\u547c\u53eb Java VM (SysExec) \u6642\u767c\u751f\u932f\u8aa4
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: 1.0.1 INTEGRATED IN: 1.0.1 VERIFIED IN: 1.0.1
31-08-2004
EVALUATION Although the localized message files were created and put into the source directory src/share/native, the makefile in build/share/GNUmakefile was never modified to copy these files into the resource directory: (build/solaris/bin/resources, or build/win32/exe/resources). I will fix this now andy.herrick@East 2001-04-20 Now the resource file is included, but will not work with multi-byte chars ... andy.herrick@East 2001-04-25 We were missing a layer of translation from UCS-2 format to locale-dependent encoding. Needed to translate "\uxxxx" where xxxx is 4 hex digits, to binary data, to locale-specific encoding (e.g. BIG5). In Windows this is easy, and I've fixed it there. Have not yet figured out how to do this properly on Solaris. As we are closing in on the last putback time, I will mark this fixed and open a new bug against Solaris. -stephen.bohne@East 2001-04-30 I believe we don't need a bug for Solaris since the Solaris installer is different. It's just a shell script and the installation is mostly English (4446795). I was unable to let the installer display "Bad installation. Error invoking Java VM (SysExec)." The installer just keeps on asking for path of JRE until a valid path is entered. michael.fang@eng 2001-04-30 The synopsis of this bug is misleading, the bug is not actually in the installer, it's in the native code that is run upon invocation of Javaws. (javaws.exe on Windows, javawsbin on Solaris). It was believed to be in the installer because javaws is run during the install process. You can reproduce this bug by specifying an invalid JRE in the javaws.cfg file. I added the Solaris version of this bug to the "see also" section. -stephen.bohne@East 2001-05-01
01-05-2001