Quote:
Originally Posted by synosure
Once you've hard-coded the TOC, the NCX, and the OPF, then you can test it by making sure Amazon's kindlegen software runs smoothly on it.
|
That test only tests if your hand coded files work with kindlegen, a completely meaningless test.
Quote:
|
First bug note - The bug mentioned in the first post still exists. To replicate, create an ebook where chapters are marked with class="toc1", but have some of the tags be h3, and some be img. The images won't make it into the table of contents. (If the TOC search is //*[re:test(@class, "toc1", "i")])
|
That's not a bug TOC elements need to have text, images dont. If you want to use images as chapter headings, andd a <a id="..." style="display:none">some text</a> after the image and have the Xpath detect that.
Quote:
|
Second bug note - Take a properly formed, hand-coded e-book, as defined in the body of this post. Run it through kindlegen, and it works perfectly, including setting the cover image. Zip it all up and open the zip file in Calibre. The TOC et al work perfectly, but Calibre does not recognize the cover image.
|
[/quote]
Again the fact that your hand coded files work with kindlegen is completely meaningless. calibre is not a kindlegen clone.