Skip to content

fragment identifiers in manifest #1085

@dauwhe

Description

@dauwhe

As an experiment I tried to put a fragment identifier on an item:

  <item id="content_001"  href="content_001.xhtml#p2" media-type="application/xhtml+xml"/>

EPUBCheck seems to interpret the fragment as part of the file extension:

WARNING(HTM-014a): ..epub/OPS/package.opf(11,91): XHTML Content Document file name 'OPS/content_001.xhtml#p2' should have the extension '.xhtml'.
ERROR(RSC-001): ..epub/fragment.epub(-1,-1): File 'OPS/content_001.xhtml#p2' could not be found.
ERROR(RSC-008): ..epub/OPS/nav.xhtml(8,33): Referenced resource 'OPS/content_001.xhtml' is not declared in the OPF manifest.
WARNING(OPF-003): ..epub/fragment.epub(-1,-1): Item 'OPS/content_001.xhtml' exists in the EPUB, but is not declared in the OPF manifest.

Perhaps EPUBCheck could provide a more informative message.


While researching this haven't yet found anything in EPUB 3.2 that forbids fragment identifiers in href attributes! Stay tuned.

Metadata

Metadata

Assignees

No one assigned

    Labels

    status: completedWork completed, can be closedtype: improvementThe issue suggests an improvement of an existing feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions