Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Closed
iherman opened this issue Feb 16, 2022 · 0 comments
Closed

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

iherman opened this issue Feb 16, 2022 · 0 comments
Assignees
@rdeltour
Labels
spec: EPUB 3.3 Impacting the support of EPUB 3.3 status: completed Work completed, can be closed type: false-positive This issue is about valid content being incorrectly rejected
Milestone
v5.0.0-beta

Comments

@iherman
Copy link
Member

iherman commented Feb 16, 2022 •
edited
Loading

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
@iherman iherman added the spec: EPUB 3.3 Impacting the support of EPUB 3.3 label Feb 16, 2022
@iherman iherman mentioned this issue Feb 16, 2022
Merged
@rdeltour rdeltour self-assigned this Feb 17, 2022
@rdeltour rdeltour added status: accepted Ready to be further processed type: false-positive This issue is about valid content being incorrectly rejected labels Feb 17, 2022
@rdeltour rdeltour added this to the v5.0.0-beta milestone Feb 17, 2022
@rdeltour rdeltour added status: in progress The issue is being implemented by the development team and removed status: accepted Ready to be further processed labels Nov 17, 2022
@rdeltour rdeltour added status: completed Work completed, can be closed and removed status: in progress The issue is being implemented by the development team labels Dec 1, 2022
@rdeltour rdeltour mentioned this issue Dec 2, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rdeltour rdeltour

Labels
spec: EPUB 3.3 Impacting the support of EPUB 3.3 status: completed Work completed, can be closed type: false-positive This issue is about valid content being incorrectly rejected
Projects
None yet
Milestone
v5.0.0-beta
Development

No branches or pull requests
2 participants
@iherman @rdeltour