Summary: | GB18030:Could not set a GB18030 character as workbench classpath variable. | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Liu Yang <yangliu> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | RESOLVED WORKSFORME | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 2.1 | ||||||
Target Milestone: | 2.1 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Liu Yang
2003-01-21 03:03:42 EST
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 |