JDK-4094685 : (i18n) The VM does not handle i18n issues related to class file names correctly
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: solaris_2.6,1.1,1.1.5,1.1.6,1.2.0
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS:
    generic,solaris_2.5.1,solaris_9,windows_95,windows_nt generic,solaris_2.5.1,solaris_9,windows_95,windows_nt
  • CPU: generic,x86,sparc
  • Submitted: 1997-11-21
  • Updated: 1999-02-05
  • Resolved: 1999-02-05
Related Reports
Duplicate :  
JDK-4146969 - Error occurs when using Japanese Shift-JIS code for class name.
Duplicate :  
JDK-4193134 - (1.1) Problems loading classes named with non-English characters
Duplicate :  
JDK-4115121 - (i18n) jvm throws exception when class name contains multibyte character
Duplicate :  
JDK-4023102 - (i18n) Class.forName doesn't work with a non-ASCII name
Relates :  
JDK-4213486 - (1.1) JDK118[Sol] Error msg is different from 1.1.7 when loading Japanese class
Description
The VM treats class file names on disk as UTF8 strings, although they
can be in arbitrary platform encoding.

As a result, if the programmer creates a class file using a name that
includes, for example, Japanese characters, the VM will not be able
to read it correctly.
Comments
EVALUATION LoadClassLocally() in classload.c must be made to understand local encoding when reading local file system directories. This might slow down class loading a bit, so must be special cased for non-iso8859 encodings. Also there is a bootstrap problem -- what if the class you are loading is in fact the converter you should be using to do the encoding (this is not an issue in the deployment scenario where the converters are in i18n.jar). anand.palaniswamy@Eng 1998-06-30
30-06-1998