Quote:
Originally Posted by hobnail
Of course I forgot to add, "but why"?
Does the EPUB spec say what to use for the nav.xhtml in an EPUB 3? Sigil is using ol/li. I always use that nav.xhtml for the book's TOC that the user sees, by opening it in calibre's editor and dragging the nav.xhtml to the front of the book (doesn't work in sigil for whatever reason; it stays at the end).
I've used dt/dd for glossaries without any problems. I agree with Turtle91. (Let them eat cake!)
|
I have two separate methods for working on ebooks. For myself, I'll use whatever I want as long as I can make it look good on my ereader collection. This is very different from when I am working on an ebook for another person, I tend to go as vanilla as possible to improve the chances of the book looking, if not good, at least readable on as many devices as possible.
As for nav.xhtml and lists? The spec is publicly available so you may want to check
5.4 EPUB Navigation Document Definition which does specify the use of ol/li elements.
Given that most of the associated text is rather short ( a short single line), there shouldn't be some of the issues I've seen with lists with multiline/multiparagraph text. Then there have been the times I've run into the use of nested lists. That use tends to end rather badly for all concerned.