View Single Post
Old 11-07-2020, 09:07 PM   #3
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,377
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by hobnail View Post
The same thing happens with Sigil. From start.xhtml I copied the stuff between the body tags into a new .xhtml file in a new epub3 in Sigil and generated the table of contents and the sub and superscripts are lost.
ADE rendering an epub2 file and other epub2 renderers will use the ncx file as the source for ToC information. An inline HTML ToC is not necessary and not used by the renderer. The ncx file format is XML not HTML. To quote: "XML stores data in plain text format. This provides a software- and hardware-independent way of storing, transporting, and sharing data." You will notice that you can not link a stylesheet to the ncx file anymore than you can link it to the opf file.

If you are creating an epub3, you can use formatting in the nav document and you can see this if the nav document is in the spine and you are viewing that document. Otherwise, it will be displayed as a plain text document.

Last edited by DNSB; 11-07-2020 at 09:15 PM. Reason: Added comment about epub3 nav document
DNSB is offline   Reply With Quote