Community
Participate
Working Groups
Bug: Class name, method name, variable name can not contain GB18030 character in some version of Eclipse for Linux. Language: Simplified Chinese Testcase: #JS1 Build driver: 200212181304 Stable Build (M4) with Motif build 200212181304 Stable Build (M4) with GTK build OS: RedHat 8.0 JRE Version: J2RE 1.3.1 IBM build cxia32131-20021102 (JIT enabled: jitc) J2RE 1.4.0 IBM build cxia32140-20020917a (JIT enabled:jitc)) Summary: Class name, method name, variable name can not contain GB18030 character in Eclipse GTK build (with JRE 1.3.1 and JRE 1.4.0) and Eclipse Motif Build (with JRE 1.3.1) Steps to recreate problem: 1.create a new project. 2.declare a class name contains a GB18030 character. View the information of building. 3.declare a method name contains a GB18030 character. View the information of building. 4.declare a variable name contains a GB18030 character. View the information of building. 5. Click menu Project->Rebuild All, rebuild the project . <<Error>> In GTK ( with JRE 1.3.1 and JRE 1.4.0) and in Motif (with JRE 1.3.1), it reports build error in the task list: Syntax error on token "Invalid Character", "Identifier" expected (As is shown in JS1_Motif_131.jpg). If use GB2312 character instead of GB18030 character, it works correctly. In Motif(with JRE 1.4), it is correct. <<Expected Result>> The java file compiles correctly.
Created attachment 3226 [details] Screen shot of error window: JS1_Motif_131.jpg
Created attachment 3227 [details] Sample Java Source File: GB18030.java
Did you check that the libraries of your JRE contains the GB8030 encoding?
I have no problem to compile your test case if the encoding 18030 is available. So this is a problem with the settings of your workspace. On my JDK1.4.1, this encoding is in the charsets.jar. Please ensure you have this file on your classpath and that this encoding is provided in it. According to the doc I put in a previous message, this encoding is not available for a 1.3.1 VM.
Change milestone.
I reopen it since I checked on WIN32. I will try to find a Linux box to ensure this is the same setting problem on Linux.
I checked that it works on the IBM 1.4.0 VM on a GTK box. A 1.3.1 VM doesn't officially support your encoding. So stop using this VM if you want to use the GB18030 encoding. I could import your test case without a problem in eclipse running on the 1.4.0 VM you listed. I firmly believe your encoding problem is related to a setting problem on your linux box. This is beyond the code of eclipse. Close as WORKSFORME.
Verified with the following test environment: Eclipse Build: 200302061700 Stable Build (M5) JRE version: JRE 1.3.1 IBM build cxia32131-20021102 (JIT enabled: jitc) JRE 1.4.0 IBM build cxia32140-20020917a (JIT enabled:jitc) Bug exists with IBM JRE 1.3 SR3, resolved with IBM JRE 1.4.0 => This bug is due to IBM JRE 1.3.1 SR3 limitation
