-
Notifications
You must be signed in to change notification settings - Fork 5
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.
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
Various fixes to EPUB 3 to DAISY 2.02 #153
Conversation
I tried running the test book from the nordic migrator through (C00000.epub), and the result is not valid when I use the Pipeline 1 DAISY 2.02 DTB Validator. I get similar results for our other books. I'm attaching the XML report from Pipeline 1: report.xml.txt (Also, the "validation" option should probably be a boolean rather than a string option, but that's not really related to this PR.) |
Thanks for testing. How have you tested it? In your report I'm seeing all the errors that this PR should have fixed. Why a boolean? It is currently a "choice": <choice>
<value>off</value>
<a:documentation xml:lang="en">No validation</a:documentation>
<value>report</value>
<a:documentation xml:lang="en">Report validation issues</a:documentation>
<value>abort</value>
<a:documentation xml:lang="en">Abort on validation issues</a:documentation>
</choice> |
Oh, maybe I tested it the wrong way then.
boolean/choice: oh, ok. It was a text input field with "off" as the default so I assumed it it would be "on" or "off". Maybe it has an incorrect option type. |
OK let me push a branch on which you can test it... Regarding the "validation" option: I'm also seeing this in the web UI now. It looks like the data type is not exposed. Will investigate. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks generally OK to me! (with a couple nitpicking details in inline comments)
self::html:h4 or | ||
self::html:h5 or | ||
self::html:h6 or | ||
self::html:span[matches(@class,'(^|\s)page-(front|normal|special)(\s|$)')]]"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if we should also accept element with ARIA role="heading"
…
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But shouldn't we first convert that to a h then in the HTML downgrading?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, this should rather be converted to a native heading element.
The SMIL already references a containing element. FIXME: Unlikely to | ||
happen for headings, but less unlikely for page numbers. | ||
--> | ||
<xsl:message terminate="yes">FIXME</xsl:message> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we not terminate here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess so. But we would be creating an invalid SMIL?
SMIL files with references to all headings are generated when needed. This is needed for the NCC to be valid. Some things have been left out for now: - support merging of existing par elements when they reference segments within a heading - page numbers are left out from the NCC See also issue #86.
…t to disk so that they can be manually inspected.
663e360
to
4010052
Compare
@josteinaj Check the epub3-to-daisy202 branch in the super project. |
I tried the new branch. Still getting errors, but some different errors: |
Thanks. I think the validator from Pipeline 1 is more strict than the one in Pipeline 2. I wonder why. These are the validation issues:
|
This one is solved. It was an error in the input EPUB. @rdeltour epubcheck didn't pick this up. See w3c/epubcheck#975 |
@rdeltour Do you think we should make the validator more strict? |
- correct computation of HTML base URLs - support xml:base in SMIL documents - normalize URLs before comparing - add comment in augment-smil.xsl about add-missing-ids.xsl see daisy/pipeline-scripts#153
Merged in daisy/pipeline-modules@98f901d and addressed most of @rdeltour's comments. |
- correct computation of HTML base URLs - support xml:base in SMIL documents - normalize URLs before comparing - add comment in augment-smil.xsl about add-missing-ids.xsl see daisy/pipeline-scripts#153
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good. The validation errors given by Pipeline 1 should be fixed in my opinion: #153 (comment)
Addresses the issues #86 and #92.