Community
Participate
Working Groups
Reporter:Louis Cai OS: windows 2003 Standard Edition Language: CHS/CHT/KOR Build level: wswb-30M8-200403291703 JDK Version: IBM JDK 1.4.2 Beta Test case #: Summary: DBCS: Can not input DBCS in the workspace selection dialog Description: Steps to recreate problem: 1-Double click the eclipse.exe, then popup a dialog of workspace selection 2-Place cursor in the field, and try to input DBCS in the field <<Error>> You can not input DBCS in the workspace selection dialog <<Expected Result>> You can input DBCS in the workspace selection dialog
Created attachment 9207 [details] picture for step 1
This problem also happened when we export project with JAR and ZIP file.The DBCS cann't input in the JAR or ZIP file export destination.
I suspect that this is obsolete.
Karice, could you help me with testing this?
Using 3.2 RC1 I can enter the Japanese (Katakana) characters in the text but found something odd. When I start the workspace without using -data to specify a location and enter some Japanese characters, all is well. The workspace starts up and the workspace directory named with the typed characters is created. BUT if I do Switch Workspace, and enter some Japanese characters, another workpsace is used - a new workspace folder with the new name i entered is not created. This is because I am using the same root directory in which i have a bunch of other workspaces. If I use another root directory that doesn't have other workspaces in it I get an message that *I believe* says the associated workspace is already in use.
Reassigning bugs to reflect changes in ownership.
Prakash is now responsible for watching bugs in the [WorkbenchLauncher] component area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.