Community
Participate
Working Groups
20041214 1.5 vm If you create a java project with a Hebrew name and then a jpage with an English name you will not be able to execute it. This is fine with a Hebrew page name and an English project name STEPS 1) Create a project with a Hebrew name 2) Create a file called test.jpage 3) Insert the following code: System.out.println(java.util.Locale.getDefault ()); 4) Highlight and select Display You will get the following error: !ENTRY org.eclipse.debug.core 4 120 2004-12-14 10:35:09.449 !MESSAGE Exception occurred executing command line. !STACK 0 java.io.IOException: CreateProcess: D:\R31\1214\eclipse\jre\bin\javaw.exe - class path D:\R31\1214\eclipse\plugins\org.eclipse.jdt.debug.ui_3.1.0 \snippetsupport.j ar -Xdebug -Xnoagent - Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:2 575 org.eclipse.jdt.internal.debug.ui.snippeteditor.ScrapbookMain file:/D:/R31/1 214/eclipse/workspace/.metadata/.plugins/org.eclipse.core.resources/.projects/% 3 F%3F%3F%3F/org.eclipse.jdt.debug.ui/ file:/D:/R31/1214/eclipse/workspace/%3F% 3F% 3F%3F/ error=267 at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.<init>(ProcessImpl.java:81) at java.lang.ProcessImpl.start(ProcessImpl.java:30) at java.lang.ProcessBuilder.start(ProcessBuilder.java:451) at java.lang.Runtime.exec(Runtime.java:591) at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:699) at org.eclipse.jdt.launching.AbstractVMRunner.exec (AbstractVMRunner.java :70) at org.eclipse.jdt.internal.launching.StandardVMDebugger.run (StandardVMD ebugger.java:199) at org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunchConfigur ationDelegate.launch(JavaLocalApplicationLaunchConfigurationDelegate.java:109) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConf iguration.java:588) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConf iguration.java:513) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConf iguration.java:150) at org.eclipse.jdt.internal.debug.ui.snippeteditor.ScrapbookLauncher.doL aunch(ScrapbookLauncher.java:219) at org.eclipse.jdt.internal.debug.ui.snippeteditor.ScrapbookLauncher.lau nch(ScrapbookLauncher.java:143) at org.eclipse.jdt.internal.debug.ui.snippeteditor.JavaSnippetEditor$14. run(JavaSnippetEditor.java:1146) at org.eclipse.swt.custom.BusyIndicator.showWhile (BusyIndicator.java:69) at org.eclipse.jdt.internal.debug.ui.snippeteditor.JavaSnippetEditor.lau nchVM(JavaSnippetEditor.java:1149) at org.eclipse.jdt.internal.debug.ui.snippeteditor.JavaSnippetEditor.bui ldAndLaunch(JavaSnippetEditor.java:402) at org.eclipse.jdt.internal.debug.ui.snippeteditor.JavaSnippetEditor.eva lSelection(JavaSnippetEditor.java:324) at org.eclipse.jdt.internal.debug.ui.actions.DisplayAction.run (DisplayAc tion.java:101) at org.eclipse.jdt.internal.debug.ui.actions.EvaluateAction.run (Evaluate Action.java:564) at org.eclipse.ui.internal.PluginAction.runWithEvent (PluginAction.java:2 43) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection (ActionContributionItem.java:555) at org.eclipse.jface.action.ActionContributionItem.access$2 (ActionContri butionItem.java:505) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent (ActionC ontributionItem.java:419) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:833) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2803) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2448) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1569) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1540) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench (Workbench.jav a:285) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144) at org.eclipse.ui.internal.ide.IDEApplication.run (IDEApplication.java:10 2) at org.eclipse.core.internal.runtime.PlatformActivator$1.run (PlatformAct ivator.java:220) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.ja va:273) at org.eclipse.core.runtime.adaptor.EclipseStarter.run (EclipseStarter.ja va:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.eclipse.core.launcher.Main.basicRun(Main.java:185) at org.eclipse.core.launcher.Main.run(Main.java:710) at org.eclipse.core.launcher.Main.main(Main.java:694)
*** This bug has been marked as a duplicate of 32206 ***
Todd, I think the problem is that the encoding used by the workspace and the encoding used by the Eclipse runtime are different in this case. When we send a command line to Runtime.exec(..), the command is interpretted in the encoding of the Eclipse runtime. I'm not sure if there is a way to detect that incompatible characters are present, and if there is a way to convert them to unicode. I can't find an environment variable on Windows to specify encodings, but if one were avaialable we might be able to set the evironment in which to interpret the command (via the Environment tab). Todd, do you have any insight on automated character conversion (i.e. from Hebrew to unicode)?
Another note - I noticed that IFiles have an encoding in Eclispe 3.0, but I do not see encodings for resources in general. Do you know if there is a way to determine the encoding of a resource name?
Not sure if that is what you asked, but container resources (the workspace root, projects and folders) have a default encoding (check IContainer#getDefaultCharset()). That may affect the encoding for any contained files, if their encoding cannot be determined by the content type for that file. Also, you can see the charset setting for any resource by checking the properties dialog, "Info" section.
