View Single Post
Old 01-07-2021, 11:21 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,737
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by netsrak View Post
There is no NCX any more in Epub 3 (except as fallback for older devices), instead there has to be a table of contents in xhtml-format now.
I often convert short stories without chapters into e-books, so they wouldn't need a TOC — there's a title page, the story and that's it. I try to avoid unnecessary files, if possible.

My first idea was to use the title page as TOC, because what constitutes the story is already there — the title. So i assigned the nav-property to the title (page). It worked, Sigil and Epubcheck found no errors.

Is there any "official" solution for one-text-books like that?
How would you do that?
Your solution will break on my Kobo reading it as an epub3 (much like an epub2 with no toc.ncx). I would suggest just leaving the nav.xhtml file in place. It's not like it takes up all that much space.
DNSB is offline   Reply With Quote