Quote:
Originally Posted by Man Eating Duck
For one, Amazon don't sell epubs, and their Kindle conversion tool all but requires an inline TOC  |
No, but one may, and many of our clients, do, upload ePUBs for conversion at the KDP. We make mobi's for our retail clients, but we make optimized ePUBs for our publisher clients, and that's what they upload at KDP.
Which means, therefore, an inline TOC. Moreover, if you do not include an inline TOC, it bollixes up the SRL (this is new, folks). And remember, you must have an inline TOC for mobi, as the "go to" for the TOC, from the Guide, only works with an html toc, not an NCX. (Yes, yes, excluding the K4PC app).
Lastly, as I think I mentioned elsewhere here on MR, this whole discussion is moot. The new ePUB3 spec has a TOC that is far more an html TOC than an NCX, so shortly, that's what we'll all be using, because certainly other than multimedia, the first thing that will be adopted is
probably that TOC--which means that the ncx will go the way of the Dodo. {shrug}.
And, yes, Wolfie's hatred of all things html.toc is legendary here.
h