Skip to content

Unnecessary requirement for a fragment ID in a SMIL file #1301

New issue
New issue
Closed
Closed
Unnecessary requirement for a fragment ID in a SMIL file#1301
Assignees
rdeltour
Labels
spec: EPUB 3.3Impacting the support of EPUB 3.3status: completedWork completed, can be closedtype: false-positiveThis issue is about valid content being incorrectly rejected
Milestone
v5.0.0-beta

Description

@iherman
iherman
opened on Feb 16, 2022

In a MO file if I have something like:

<body epub:textref="file.xhtml">
	<par>...
    ...

I get the following error message when I run the EPUB 3.3 version of epubcheck (v5.0.0-beta-1):

Validating using EPUB version 3.3 rules.
ERROR(MED_014): mol-navigation.epub/EPUB/mo/ch1.smil(2,37): A non-empty fragment identifier is required.

This in spite of the spec saying:

The value MUST be a path-relative-scheme-less-URL string, optionally followed by U+0023 (#) and a URL-fragment string.

(Emphasis is mine.)

Cc https://github.com/marisademeglio

Activity

  1. iherman
    added
    spec: EPUB 3.3Impacting the support of EPUB 3.3
    on Feb 16, 2022
  2. rdeltour
    self-assigned this
    on Feb 17, 2022
  3. rdeltour
    added
    status: acceptedReady to be further processed
    type: false-positiveThis issue is about valid content being incorrectly rejected
    on Feb 17, 2022
  4. rdeltour
    added this to the v5.0.0-beta milestone on Feb 17, 2022
  5. rdeltour
    added
    status: in progressThe issue is being implemented by the development team
    and removed
    status: acceptedReady to be further processed
    on Nov 17, 2022
  6. rdeltour
    added a commit that references this issue on Nov 28, 2022

    feat: check fragment requirements on overlays links to text content

    2091d14
  7. rdeltour
    added
    status: completedWork completed, can be closed
    and removed
    status: in progressThe issue is being implemented by the development team
    on Dec 1, 2022
  8. rdeltour
    closed this as completedin 2091d14on Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

spec: EPUB 3.3Impacting the support of EPUB 3.3status: completedWork completed, can be closedtype: false-positiveThis issue is about valid content being incorrectly rejected

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions
    ⌂ 换网址