xsd text garbled on upgrade of oxygen and eclipse
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 37
- Joined: Tue Nov 25, 2003 3:31 am
xsd text garbled on upgrade of oxygen and eclipse
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,
Bill W.
-
- Site Admin
- Posts: 2095
- Joined: Thu Jan 09, 2003 2:58 pm
Hi Bill,
Can you send over a sample file that has this problem at support@oxygenxml.com ? That will help us understand what happens.
A possible workaround will be to edit specify UTF-8 as the file encoding. Oxygen should work without problems with this.
Best Regards,
George
Can you send over a sample file that has this problem at support@oxygenxml.com ? That will help us understand what happens.
A possible workaround will be to edit specify UTF-8 as the file encoding. Oxygen should work without problems with this.
Best Regards,
George
-
- Site Admin
- Posts: 2095
- Joined: Thu Jan 09, 2003 2:58 pm
Hi Bill,
Just to have the discussion updated also here.
--
Thank you for sending the file.
The file actual encoding is UTF-8 but it contains UTF-16 in the XML header
and this confuses oXygen as it reads the header and uses UTF-16 further. Now I tried to reproduce this with oXygen 2.0.4 but it saves the xml files that specify UTF-16 in the XML header correctly so I do not understand how you end up with this file. The solution will be to specify UTF-8 in the file
header instead of UTF-16 in an editor that shows correclty the file content,
for instance you can do this in oXygen after you paste the content from
JEdit.
--
Best regards,
George
Just to have the discussion updated also here.
--
Thank you for sending the file.
The file actual encoding is UTF-8 but it contains UTF-16 in the XML header
and this confuses oXygen as it reads the header and uses UTF-16 further. Now I tried to reproduce this with oXygen 2.0.4 but it saves the xml files that specify UTF-16 in the XML header correctly so I do not understand how you end up with this file. The solution will be to specify UTF-8 in the file
header instead of UTF-16 in an editor that shows correclty the file content,
for instance you can do this in oXygen after you paste the content from
JEdit.
--
Best regards,
George
-
- Posts: 37
- Joined: Tue Nov 25, 2003 3:31 am
Thanks George,
We're OK now. after the following steps:
1. Select and delete the garbage source in the oxygen edit pane.
2. Paste the correct source into the oxygen edit pane.
3. Change line 1 from
<?xml version="1.0" encoding="UTF-16"?> to
<?xml version="1.0" encoding="UTF-8"?>
4. Saved the file
After this it closed and opened normally.
Bill.
We're OK now. after the following steps:
1. Select and delete the garbage source in the oxygen edit pane.
2. Paste the correct source into the oxygen edit pane.
3. Change line 1 from
<?xml version="1.0" encoding="UTF-16"?> to
<?xml version="1.0" encoding="UTF-8"?>
4. Saved the file
After this it closed and opened normally.
Bill.
Bill W.
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ Artificial Intelligence (AI Positron Assistant add-on)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service