Thread: Cover in TOC
View Single Post
Old 09-20-2014, 09:25 AM   #4
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,707
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by perkin5 View Post
But the TOC generator only seems to pick up h tags and the cover page has none by default.
Yes, that's to be expected. Your approach (if you want the cover page included in the TOC) to add the display:none styling should work as you expect.

What doesn't make any sense is why the validator (I'm assuming you're using the built-in Flightcrew validation) doesn't think the cover page is in the manifest and/or spine.

When I use the same procedure, the newly created cover page is indeed added to the epub's manifest, the spine, and to the guide section of the OPF file. I don't get those errors in Flightcrew.

What version of Sigil are you using (and are you indeed using the built-in validator when getting those errors)?
DiapDealer is online now   Reply With Quote