epubcheck icon indicating copy to clipboard operation
epubcheck copied to clipboard

The conformance checker for EPUB publications

Results 194 epubcheck issues
Sort by recently updated
recently updated
newest added

Consider the following content file: ``` CSS test for :is :is(h1,h2,h3,h4,h5,h6,a) abbr{border:none} This is a possible epubcheck bug... ``` the epubcheck response is as follows: > Validating using EPUB version...

status: accepted
type: false-positive

Epubcheck always emits an error on `link rel="record"` if the `media-type` attribute is missing, but we changed the requirement for 3.1 so that `media-type` is only required for resources in...

type: spec
status: accepted

I noticed this test in package-document.feature refers to issue #522 for making it a warning: ``` Scenario: default vocabularies must not be assigned a prefix Note: This should be an...

status: accepted
type: false-negative

Another weird test/restriction I've come across is in content-publication.feature where the "Report a `poster` attribute that references an invalid media type" scenario doesn't recognize a manifest fallback. Even if I...

status: accepted
type: false-positive

epubcheck reports the CSS `font-size: initial;` as an error. ``` $ epubcheck --locale en -mode exp "$epubdir" Validating using EPUB version 3.2 rules. ERROR(CSS-020): …/stylesheet.css(435,2): CSS font selector declaration uses...

status: accepted
type: false-positive

For a URI like `Test 2`, epubcheck 4.2.6 reports: > ERROR(RSC-020): example.epub/EPUB/xhtml/epub30-overview.xhtml(8,35): "mailto:abc|@example.com" is not a valid URI. According to RFC5322, the pipe character is an allowed character for the...

status: accepted
type: false-positive

Test case : - the viewport (height or width) without proper value, such as `height=705, width=` ePubCheck 4.2.4 : - output `ERROR(HTM-046)` in **fixed layout** epub - but `all pass`...

status: accepted
type: false-negative

This test in content-publication.feature checks that the media types declared on `object` tags match the manifest. > Scenario: Report an `object` element with a media type not matching the Package...

Currently, `` is url-decoded to `difficult_filename_#.png` and then interpreted as a url fragment, which feels like incorrect behavior. It's unlikely this change is in the right place, so I'm making...

status: needs review

type: improvement
status: ready to merge