A-HA!!!
This actually brings up two questions, one was my original source of frustration. First:
Is there a particular issue with using
display: block in this case? After some research, it seemed to be the way to go in regards to centering images. When the page does show up in the resulting .mobi file (buit again, not in its TOC) the image is centered perfectly. Do you have any preference to using
text-align in this case?
And my second question, thank you for reminding me, was my original headache:
Quote:
|
In any case, this is only to have Sigil automatically add the title page to the TOC. But if you can (and are willing to) manually edit the NCX file, you can always add a link to anywhere without adding an <h1> or any other trick.
|
THAT was originally my concern. You see, I
did have to manually edit the toc.ncx file to add a few sections or pages to it. And they show up fine in Sigil, they are functional navpoints, BUT...they are not read or recognized by Calibre. That, of course, means that even though Sigil shows them as TOC items, these are not parsed to the new format (.mobi).
This is why I'm interested in this h1 solution...I am hoping that the Chapter Detection functionality in Calibre will read the h1 and give it its "rightful place" in the resulting eBook, because h1 is used everywhere else in the book as, both the Chapter title's formatting and obviously the chapter marker to create the TOC. All these other pages using the h1 show up on both Sigil's TOC and the end product's TOC.