EpubCCEPUBCheck OPF-063: Adobe page-map item missing
Updated:
EPUBCheck OPF-063 is a warning message: “Referenced Adobe page-map item "…" was not found in the manifest.” The spine's Adobe page-map attribute names an item that is not in the manifest. The attribute points to a proprietary page-map file, and EPUBCheck could not find it.
The official message
Referenced Adobe page-map item "%1$s" was not found in the manifest.
- Default severity
- Warning. The EPUB is still valid, but something is likely to cause problems in some reading apps. EPUBCheck exits with 0 unless you pass --failonwarnings.
- EPUBCheck version
- 5.4.0
%1$s, %2$s… are filled in with the file, value or element EPUBCheck found.
Typical causes
- The page-map.xml file was removed but the attribute stayed on the spine.
- A typo in the id given to page-map.
- A spine copied from another book.
How to fix it
- Read the id EPUBCheck names.
- If you no longer use Adobe's page map, remove the page-map attribute from the spine element.
- If you do, add the page-map file to the manifest with that id; for EPUB 3, a page list in the navigation document is the standard replacement.
When it's not this
If the page-map item exists, EPUBCheck only reports the usage note OPF-062.
Terms used here
Other OPF messages
OPF-062Found Adobe page-map attribute on spine element in opf file.OPF-065Invalid metadata declaration, probably due to a cycle in "refines" metadata.OPF-060Duplicate entry in the ZIP file: "…" (file names must be unique after Unicode canonical normalization and full case folding).OPF-066Missing "dc:source" or "source-of" pagination metadata. The pagination source must be identified using the "dc:source" and "source-of" properties when the content includes page break markers.OPF-067The resource "…" must not be listed both as a "link" element in the package metadata and as a manifest item.OPF-070Custom collection role "…" is an invalid URL.
Sources
Message text and severity from EPUBCheck 5.4.0 (W3C, BSD-3-Clause). Explanation by EpubCC.