Community
Participate
Working Groups
Operating System: Linux - RHEL4.0/GTK Enterprise Edition, Linux - SLES 9 Sp1/GTK, and Windows 2003 - Standard Edition Build ID: I20050505 Locale: ar_EG.UTF-8 on Linux, and ar_EG.CP1256 on Windows Steps to re-create the problem: 1- Create new Java project (File->New->Other... select Java/Java Project) 2- In the "Package Explorer" (can be viewed from "Window"->"Show View"), right click on the project, create "New"->"Package" and give it an Arabic name that contains the "062F" Unicode character 3- In the "Package Explorer", right click on the package u created in '2', create New class java file 4- In the "Package Explorer", right click on the java file, and "run" Expected results: The program runs with no errors Actual results: A runtime-error occurs saying "The java class is not found: , <Garbage1>/<Garbage2> (wrong name: <PackageName>/<ClassName>" Even if there is an error, it is expected to have Arabic strings displayed correctly in the console, however it appears correctly in only one part of the error message <Garbage1> is supposed to be <PackageName> <Garbage2> is supposed to be <ClassName> Note: - The error occurs if the "062F" character was in the package name or class name - "062F" is not a special character, and the resulted behavior is so vague
Known problem/limitation *** This bug has been marked as a duplicate of 32206 ***
It is not a duplicate of the so-called bug as this problem happens only with this character. Using any other Arabic character generates no errors and the application runs successfully.
Can you successfully launch the application from the command line using a similar scenario (i.e. the bidi character in class/package name)?
I could not launch the application from the command line using the BiDi character "062F" in class or package names FYI, this Scenario was tested using different versions of sun JREs (1.4.2_06, 1.4.2_07, 1.5.0_02)and the application was executed successfully without producing any run-time errors note: only IBM j2re1.4.2 (downloaded from the IES site ) produces this error
If the scenaior works properly with the Sun VMs, but not IBM, I suggest that a bug should be opened against the VM. It does not sound like a debugger problem in this case.
Ok, then this defect should be closed. but as IBM JVM is the defult VM used with the IES, I think it should be, somehow, stated in product documentation that this VM may have some limitations with some unicode characters
I can add it as a README. Please provide the exact version information about the VM that this is a problem with.
The exact version information about the used VM is: JavaM<TM> 2 Runtime Environment, Standard Edition <build 1.4.2> Classic VM (Build 1.4.2, J2RE 1.4.2 IBM windows 32 build cn142-20040926 (JIT enabled: jitc)) Thanks Darin
