Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: P5
Fix Version/s: None
Affects Version/s: solaris_2.6, 1.1, 1.1.5, 1.1.6, 1.2.0
Component/s: hotspot
Labels:
- i18n
- japanese
- jdk122-ja
- kestrel-ja
- licbug

Subcomponent:
runtime
CPU:

generic, x86, sparc
OS:

generic, solaris_2.5.1, solaris_9, windows_95, windows_nt

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.

duplicates

JDK-4146969 Error occurs when using Japanese Shift-JIS code for class name.

Closed

JDK-4023102 (i18n) Class.forName doesn't work with a non-ASCII name

Closed

JDK-4115121 (i18n) jvm throws exception when class name contains multibyte character

Closed

JDK-4193134 (1.1) Problems loading classes named with non-English characters

Closed

relates to

JDK-4213486 (1.1) JDK118[Sol] Error msg is different from 1.1.7 when loading Japanese class

Closed

Assignee:: Anand Palaniswamy (Inactive)

Reporter:: Sheng Liang (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 1997-11-21 13:57

Updated:: 1999-02-04 18:22

Resolved:: 1999-02-04 18:22

Imported:: 17/Sep/12 10:12 PM

Indexed:: 28/Jul/12 5:30 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates