Community
Participate
Working Groups
Language: Simplified Chinese OS: Windows 2000 Eclipse Build: 200302061700 Stable Build (M5) JRE version: JRE 1.4.0 IBM build cxia32140-20020917a (JIT enabled:jitc) <<Summary>> Can't set jre in a path contain GB18030 character. <<Re-produce steps>> 1. Launch Eclipse. 2. Click menu: Window -> Preference. 3. Click: Java ->Installed JRE. 4. Click Add button a "Add JRE" window shows up. 5. Input a JRE name. 6. Input a JRE home directory that path contain GB18030 character. (refer to jre1.jpg) 7. Click OK. 8. Check on the new JRE, and click OK. 9. Eclipse warn can not find class.(refer to jre2.jpg) <<Expected Result>> It runs correctly <<Execution Result>> Build error. <<Comments>> 1. I can run it with GB2312 character. 2. I have change the Fonts for workbench and system to GB18030 character.
Created attachment 3769 [details] Screen Shot
Confirmed bug in build 2.1 RC1 Notice in the first screen shot that it failed to detect all the necessary JARs in this case. There is an entry in the log file that looks to be related to this. I will attach that log. However, even when I add all the necessary JARs manually, it still fails to compile anything. I have a GB18030-enabled machine available for testing this.
Created attachment 3835 [details] Log file showing stack trace when auto-detecting JARs
Olivier - please investigate using John's machine
I have entered a separate bug for the failure to auto-detect libraries. See bug 33844.
The problem is that the java.util.zip library cannot open a file with a name that contains GB18030 characters. I put a breakpoint in the ZipFile opening and we got it trying to find out if "java" is a package. It failed and then of course nothing can be compile properly because java.lang.Object is not found. With John, we tried to use the jar utility on the command line and it could not open the file. Could you please confirm on your machine that the command "jar tvf ............../core.jar" doesn't work? Specify the right name on the command line. Thanks.
Created attachment 3857 [details] Error we got using the tool jar This is the error message we got using the tool. I put it in a zip file on the chinese encoding machine. Hopefully you will be able to read it. Do you get the same kind of errors?
1. Translate the error message: "file name, directory name or driver lable syntax error". 2. I notice in your error file that you are in Traditional Chinese DBCS, not Simplified Chinese GB18030.
Could you please tell me if the jar tool works for you on your machine? We believe the java.util.zip package is boggus to read a file name that contains GB18030 characters.
Could you please try to read a zip file using a path that contains GB18030 characters? We believe that the java.util.zip package has some bugs with these paths. We need a confirmation from you. Thanks.
We have executed the command in Windows (as is shown in the attachment below). The result is nearly the same as before: "File name, directory name or driver label syntax error". If the directory name only contains GB2312 character, it runs correctly. I also tried this command in linux (Redhat 8), it runs correctly. btw: the GB18030 code we use to verify is 8139ee39, whose unicode is 3400.
Created attachment 3937 [details] jar1.jpg (command result in win2000)
Then it is a bug in the library and we cannot fix it.
Could you please confirm that the original problem cannot be reproduced on Linux? It looks like this is a bug in the Windows library code.
Yes, I can confirm that this jar command runs correctly in redhat 8 platform.
I meant that the steps to reproduce doesn't show the problem on a Redhat platform. If the jar command works fine for Linux, then the problem should not occur on Linux. Could you please confirm that you can set a JRE in a path that contains GB18030 characters on Linux? The bug seems to be only in the Windows zip support.
I can set a JRE in a path that contains GB18030 characters on Linux. And I can create and run a project successfully with this JRE. The environment is Redhat 8, Motif RC1 build.
The problem is that the bug is located in the zip library on Windows. This is not an Eclipse bug as Eclipse is using the java class libraries. I think you should enter a problem report against the JRE you are using. The problem is located in the java.util.zip.ZipFile class when creating a zip file with a path that contains GB18030 characters. Ok to close?
accept, this is not a eclipse bug. please change the resultion to wontfix.
Closed.
Verified
