feat: no longer check .xhtml extension in EPUB 2.0.1
#1388
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EPUB 2.0.1 does not specifically require XHTML content documents to have the `.xhtml` extension. EPUBCheck reported this as a warning (`HTM-014`), now suppressed. The sibling `HTM-014a`, which checked the same for EPUB 3, was already suppressed. Note: this change will only be effective when the checks of the `ctc` package are disabled.
mattgarrish
approved these changes
Dec 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EPUB 2.0.1 does not specifically require XHTML content documents to have the
.xhtmlextension.EPUBCheck reported this as a warning (
HTM-014), now suppressed.The sibling
HTM-014a, which checked the same for EPUB 3, was already suppressed.Note: this change will only be effective when the checks of the
ctcpackage are disabled.