Bugzilla – Full Text Bug Listing
| Summary: | Setting of "osgi.console.encoding" is being ignored | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Mário Guimarães <mljrg> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | darin.eclipse, remy.suen |
| Version: | 3.5.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | stalebug | ||
You likely need to set the encoding on the "Common" tab of the launch configuration to match. Does this work? Bug 244708 "Not able to manually type console encoding on Run Configurations" prevents me from doing that. This is addressed by bug 244708 *** This bug has been marked as a duplicate of bug 244708 *** Sorry, but the reason given to close this bug is not valid because it is not a duplicate of Bug 244708: Bug 244708 requested manual editing of the encoding in "Run Configurations->Commons" tab, but Bug 322932 concerns editing the encoding via "Run Configuration->Arguments->VM arguments tag" (e.g., "-Dosgi.console.encoding=Cp437" on this last tab) or directly when running eclipse from the terminal (e.g., "eclipse.exe ... -Dosgi.console.encoding=Cp437 ..."). So these two bugs are different though their purpose is to set the same VM property. In addition, you need to decide which setting wins when the VM property is set differently at different places. In this case, I suggest that the "-Dosgi.console.encoding=XXXX" setting should win. Cheers! 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. -- The automated Eclipse Genie. |
Build Identifier: M20090211-1700 The VM system property "osgi.console.encoding" is being ignored by the Console View. Well, at least the Console View does not show the right characters for the encoding set via this property. Reproducible: Always Steps to Reproduce: 1) Create the following "Java Application" inside Eclipse: import java.io.IOException; public class Encode { public static void main(String[] args) throws IOException { System.out.println(System.getProperty("osgi.console.encoding")); System.out.println((char)0xC3); } } 2) Create a "Run Configuration" and set "-Dosgi.console.encoding=Cp437" on the VM arguments tab 3) Run it from Eclipse. On the Console View you will see that the property was set correctly, but a character (Ã) will appear instead of a box drawing character (├) 4) If the same application is run from the MS-DOS command prompt it will print the box drawing character correctly.