Thanks both JSWolf and Tex2002ans.
Tex2002ans, your question about what version of EPUB-Checker made me check out updates. I have now updated it, and EPUB-Checker has changed it's Validation to "EPUB version 3.2 rules, and now there are "no errors or warnings detected. EPUB is valid!"
However, your comment, Tex2002ans, about the need to gracefully fallback and work better across a variety of readers does concern me. I also used the FlightDeck service to check it, and it says Apple doesn't like the endnotes and endnote declarations (even though in tests they work fine in Apple's Books app on my Mac. I changed the endnote/s to footnotes and footnote respectively and it no longer rejects the page in Flightdeck. Go figure.
Concerning using the<ul> list, they are not mammoth (the largest is around 20), as, according to everything I've read here and elsewhere including books, it's best to use HTML properly. These are a list of footnotes at the end of each chapter (endnotes), hence my choice. Another reason for going for the list (or even p or div tags)instead of wrapping each footnote in an aside tag was that I read in these forums that this stops iBooks from using its pop-up feature. I tested this out with Apple's Books app, and it's true. The list tags semantically are correct as well as they work in Books (iBooks). The list works fine in ADE, but haven't tried a Kindle yet.
As for where I got the code suggestion from, what I meant was the epub:type declarations appear to be correct. I haven't seen footnotes used in a list before, but, to me, it is logical. However, if it's a problem, I'll take them out and put them in div or p tags (as others on this forum have suggested).
Thanks for the responses. Any advice is welcome. It's a long time since I put together an ebook and things have moved on quite a bit.
|