Malformed entity references flagged on wrong line
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 4
- Joined: Tue Dec 19, 2006 8:06 pm
- Location: Oxford, UK
- Contact:
Malformed entity references flagged on wrong line
Hi,
In the attached file, I get an error flagged on line 6 when the actual error is on line 9. This happens in both the standalone and Eclipse editors. Is this a known bug, or is it something peculiar to do with my setup? It seems pretty fundamental to me, and means I currently have to resort to the command line to find such errors in long XHTML files.
Any thoughts?
Cheers,
TIM
In the attached file, I get an error flagged on line 6 when the actual error is on line 9. This happens in both the standalone and Eclipse editors. Is this a known bug, or is it something peculiar to do with my setup? It seems pretty fundamental to me, and means I currently have to resort to the command line to find such errors in long XHTML files.
Any thoughts?
Cheers,
TIM
Code: Select all
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyleft Tim Booth blah blah etc
-->
<foo>
<bar>This line is nice & well-formed.</bar>
<baz>
but
<this line="is naughtly & has an unescaped ampersand!" />
</baz>
</foo>
-
- Site Admin
- Posts: 2095
- Joined: Thu Jan 09, 2003 2:58 pm
Hi Tim,
Thanks for reporting this issue, it looks indeed like a problem introduced by the part that tries lo locate more precisely the error, it locates the previous entity assuming the error is related to that but in this case the entity in error is not reported.
We will fix this in short term.
Best Regards,
George
Thanks for reporting this issue, it looks indeed like a problem introduced by the part that tries lo locate more precisely the error, it locates the previous entity assuming the error is related to that but in this case the entity in error is not reported.
We will fix this in short term.
Best Regards,
George
George Cristian Bina
-
- Site Admin
- Posts: 2095
- Joined: Thu Jan 09, 2003 2:58 pm
Hi Tim,
The problem was fixed in the current development stream and it will be available in the 8.1 maintenance release, expected to be generally available this month. If you really need this fix we can make available for you an early access build but the workaround is easy, just search for the next ampersand to find the error location.
Best Regards,
George
The problem was fixed in the current development stream and it will be available in the 8.1 maintenance release, expected to be generally available this month. If you really need this fix we can make available for you an early access build but the workaround is easy, just search for the next ampersand to find the error location.
Best Regards,
George
George Cristian Bina
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ 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