MobileRead Forums - View Single Post

democrite · 07-06-2023, 07:01 PM

I am aware of the purpose of the NAV doc.

My request is perhaps from a mistsken understanding of how to have a nav doc but not have it shown when navigating the book.

Linear no was what I used to use but epubcheck now complains of no link. I could add one but its really not needed and I consider it inelegant.

Not having it in the spine is perhaps preferred yet Sigil from what I recall often auto adds any missing XHTML file to the spine, such that I need to often reverify if it has been readded. Perhaps that's a main issue. Forgot if there's an option; I haven't checked recently.

Thus I thought if nav and XHTML toc were combined, it'd be a way around such. Yet not the preferred method; I merely thought it was a possible workaround.

As for having separate NAV and XHTML TOCs. in contrast to a previous mention, nearly all epubs I read are designed as such, though all of them are from academic publishers.

The main issue I have been struggling with is having the NAV toc fully work with Apple Books. Once for some reason, for all my epubs, toc entries were not selectable in ios/ipados unless each entry had an anchor and didn't just point to a file, so I added an id to the body tag and had to do that for all my epubs, having had to do such for years. I'm not sure if that quirk is now fixed or why some epubs were as such, and others not.

The current true issue is I'm having trouble getting pagelist numbers to show up in Apple Books. Ok ok macOS not on iPhone iPad. This started maybe some months ago with some iOS update.

My typical workflow is to normalize, convert to epub 3 if not already, make a backup of the nav e.g. as nav2 that isn't in the spine or defined as nav but just as backup (just in case I mess up something in later edjting), create a new toc containing all H2+ headers, create a XHTML toc for such sections but have such not defined as the XHTML contents, copy such to the original XHTML toc such that it has the original formatting yet contains all sections of the book (tformattinlcontain only part and chapter headings), then copy back thformattinl nav.

I also rename all files to have part and chapter number. I do such since it makes it easier for regex replacement such as adding links to all headers that return to the toc, for easy navigation. Such also makes editing much quicker, for example so I know this or that file is chapter X in part X, appendix X, etc.

Somewhere along that process, despite many unmodified epubs showing page numbers fine in iOS Books, none of mine now do despite passing epubcheck. I tried but can't figure out why.

07-06-2023, 07:01 PM	#7
democrite Evangelist Posts: 441 Karma: 77256 Join Date: Sep 2011 Device: none	I am aware of the purpose of the NAV doc. My request is perhaps from a mistsken understanding of how to have a nav doc but not have it shown when navigating the book. Linear no was what I used to use but epubcheck now complains of no link. I could add one but its really not needed and I consider it inelegant. Not having it in the spine is perhaps preferred yet Sigil from what I recall often auto adds any missing XHTML file to the spine, such that I need to often reverify if it has been readded. Perhaps that's a main issue. Forgot if there's an option; I haven't checked recently. Thus I thought if nav and XHTML toc were combined, it'd be a way around such. Yet not the preferred method; I merely thought it was a possible workaround. As for having separate NAV and XHTML TOCs. in contrast to a previous mention, nearly all epubs I read are designed as such, though all of them are from academic publishers. The main issue I have been struggling with is having the NAV toc fully work with Apple Books. Once for some reason, for all my epubs, toc entries were not selectable in ios/ipados unless each entry had an anchor and didn't just point to a file, so I added an id to the body tag and had to do that for all my epubs, having had to do such for years. I'm not sure if that quirk is now fixed or why some epubs were as such, and others not. The current true issue is I'm having trouble getting pagelist numbers to show up in Apple Books. Ok ok macOS not on iPhone iPad. This started maybe some months ago with some iOS update. My typical workflow is to normalize, convert to epub 3 if not already, make a backup of the nav e.g. as nav2 that isn't in the spine or defined as nav but just as backup (just in case I mess up something in later edjting), create a new toc containing all H2+ headers, create a XHTML toc for such sections but have such not defined as the XHTML contents, copy such to the original XHTML toc such that it has the original formatting yet contains all sections of the book (tformattinlcontain only part and chapter headings), then copy back thformattinl nav. I also rename all files to have part and chapter number. I do such since it makes it easier for regex replacement such as adding links to all headers that return to the toc, for easy navigation. Such also makes editing much quicker, for example so I know this or that file is chapter X in part X, appendix X, etc. Somewhere along that process, despite many unmodified epubs showing page numbers fine in iOS Books, none of mine now do despite passing epubcheck. I tried but can't figure out why.