Community
Participate
Working Groups
OS: Windows2000 Simplified Chinese Version + GB18030 Patch Eclipse Build: 20020321 Stable Build Abstract: Eclipse can't identify that a classpath variable whose name contains a GB18030 Character. Re-Produce Steps: 1.Start Eclipse 2.Click Window->Preferences 3.Preference window show up 4.Select Java->Classpath Variable, then click New Button 5.Input a GB18030 character into name box 6.a warning show up(as is shown in var1.jpg) Comments: Before the process,I have changed the Eclipse font to a GB18030 enabled font in workbench preference. I also change the windows display font to GB18030 enabled font. I can create a folder with the name which contains GB18030 character in Windows Explorer. In the same window,I can input a GB2312 character and then create the classpath variable successfully. ------- Additional Comment ------- Verify with following test environment: Eclipse Build: 20021218 Stable Build (bug occured) JRE version: J2RE 1.3.1 IBM Windows 32 build cn140-20020902 (JIT enabled: jitc) Result: A classpath variable name COULD NOT contain a GB18030 character. Eclipse Build: 20021218 Stable Build (bug disppeared) JRE version: J2RE 1.4.0 IBM Windows 32 build cn140-20020902 (JIT enabled: jitc) Result: A classpath variable name COULD contain a GB18030 character.
Created attachment 3052 [details] var1.jpg (Screen Cut of the step 6)
Moving to JDT UI for comment.
Martin, I think that we use JDT Core API to validate a Java identifier. If so please move on to JDT Core.
One additional question for the reporter: have you switch the local for Eclipse to GB18030 using the Preferences>Workbench>Editors.
using JCore validator. moving to jcore
You have the problem because you use a VM 1.3.x that doesn't support your encoding (GB8030). Eclipse encoding support works fine if you use a VM that can support such an encoding. In bug 29863, I gave you two links that state what encoding is supported by each VM. http://java.sun.com/j2se/1.3/docs/guide/intl/encoding.doc.html you will see that a 1.3 VM doesn't have the GB18030 encodings charset, whereas at this link http://java.sun.com/j2se/1.4/docs/guide/intl/encoding.doc.html, you can check that a 1.4 VM has this encoding in its charsets.jar file. The GB8030 is not a supported encoding for your VM, therefore don't expect Eclipse to be able to handle it. The best would be a check that the encoding is supported and a failure should be returned if not.
Closing
