Quote:
Originally Posted by ChaJudLeoBit
Thank you so very much for your reply.
I used the TOC builder in Sigil that uses headings. I took a screen shot of the TOC and my manifest to show you.
The B&N instructions say this:
Manifest – The manifest identifies every file contained in the epub – if a file is not identified, it will not be accessible. Example of different file statements:
< item id="pt" href="my_page.xpgt" media-type="application/vnd.adobe-page- template+xml" />
< item id="style" href="mystyle.css" media-type="text/css" />
< item id="image001" href="image001.jpg" media-type="image/jpeg" />
< item id="image002" href="image002.png" media-type="image/png" />
< item id="cover" href="cover_page.xhtml" media-type="application/xhtml+xml" />
< item id="toc" href="content_page.xhtml" media-type="application/xhtml+xml" />
< item id="ncx" href="toc.ncx" media-type="application/x-dtbncx+xml" />
Note that item id "toc" refers to the physical contents page while item id "ncx" refers to the file that controls eBook navigation.
And I am afraid to make any big changes in my manifest until I understand what I need to change.
Can you offer any advice?
Thanks!
Cat  |
Did you tell NookPress to use the original file you uploaded, versus a file that they will create "over" the file, inserting their own CSS, etc.?
Hitch