-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XMLDom error #182
Comments
hi Gregorio. Would you be able to send me a sample EPUB? |
Here you have: |
Thanks for the sample file! I could reproduce the issue. |
- Use @fchasen’s fork of xmldom to parse the HTML named character references defined in HTML, even when the document is XHTML. Note however that this is a willful violation of the HTML standard, since the entities are only declared when the document has one of the allowed public identifiers (see https://html.spec.whatwg.org/#parsing-xhtml-documents) - Set an error handler to xmldom’s `DOMParser` to catch parsing errors (like undeclared entities) and log them with winston. - Add tests. Fixes #182
This should be fixed in the proposed PR. Note that these named entities references are only allowed in EPUB 2, which Ace doesn’t fully support. The PR makes it so the all the entities defined in HTML are parsed even when the mime type is XHTML (regardless of the doctype). It also catches XMLDOM warnings and errors to log them properly with Ace’s logging system. |
Thanks |
- Use @fchasen’s fork of xmldom to parse the HTML named character references defined in HTML, even when the document is XHTML. Note however that this is a willful violation of the HTML standard, since the entities are only declared when the document has one of the allowed public identifiers (see https://html.spec.whatwg.org/#parsing-xhtml-documents) - Set an error handler to xmldom’s `DOMParser` to catch parsing errors (like undeclared entities) and log them with winston. - Add tests. Fixes #182
- Use @fchasen’s fork of xmldom to parse the HTML named character references defined in HTML, even when the document is XHTML. Note however that this is a willful violation of the HTML standard, since the entities are only declared when the document has one of the allowed public identifiers (see https://html.spec.whatwg.org/#parsing-xhtml-documents) - Set an error handler to xmldom’s `DOMParser` to catch parsing errors (like undeclared entities) and log them with winston. - Add tests. Fixes #182
Ace version 1.0.0
Node version 8.7.0
MacOs 10.12.6
During Ace checking on an EPUB file I'm getting "[xmldom error] entity not found:–"
The text was updated successfully, but these errors were encountered: