xsd text garbled on upgrade of oxygen and eclipse
Posted: Thu Sep 02, 2004 12:59 pm
I have been using oxygen 2.0.4 on eclipse 2.x and am migrating to oxygen 4.2_e3. I'm running XP Pro.
PROBLEM: an xsd file developed under 2.0.4 shows up as garbage
in the editor pane under 4.2_e3. It looks like an encoding incompatibility.
I was able to work around it by opening the xsd file in jedit; copying the text to the clipboard and, pasting the text into the editor window. That worked until I closed and re-opened eclipse, when the xsd file again showed up as garbled, and attempting to open the file in jedit produced the diagnostic:
'Cannot load with "Unicode" encoding. (sun.io.MalformedInputException: Missing byte-order mark)
The encoding can be changed in the Commands menu of the file system browser.
QUESTION: What steps should I take to resolve this problem and to rescue my now inaccessible xsd file?
Thanks,
PROBLEM: an xsd file developed under 2.0.4 shows up as garbage
in the editor pane under 4.2_e3. It looks like an encoding incompatibility.
I was able to work around it by opening the xsd file in jedit; copying the text to the clipboard and, pasting the text into the editor window. That worked until I closed and re-opened eclipse, when the xsd file again showed up as garbled, and attempting to open the file in jedit produced the diagnostic:
'Cannot load with "Unicode" encoding. (sun.io.MalformedInputException: Missing byte-order mark)
The encoding can be changed in the Commands menu of the file system browser.
QUESTION: What steps should I take to resolve this problem and to rescue my now inaccessible xsd file?
Thanks,