Quote:
Originally Posted by JSWolf
I do sometimes. KDP is stupid at times. Not allowing the ToC at the back of the book is stupid.
|
Wolfie, Wolfie, Wolfie {sigh}. That's definitely vestigial Calibre. After all, nothing else puts the TOC at the end. Yes, I know what you then said in your follow-up, going there now. Below, I mean.
Quote:
Originally Posted by JSWolf
I've a KF8 eBook that does have the ToC at the end of the eBook. The ePub version has the HTML ToC not part of the spine, but listed in the guide. When you run the ePub through Kndlegen, the HTML ToC is put at the end of the eBook.
|
Sure, but that's because it's been "instructed" to do so, by not being included in the Spine. Not sure I understand what point you're making, there?
Quote:
|
Amazon has two standards. One for the publishers and the other for the self-published.
|
Well, sure, sweetie--what else would you expect? Even
I have that.
It's one thing to deal with publishing houses--the file comes in, in final, we make it, bada-bing, bada-boom, it's one and done. New authors? We make it, and we make it, and 8 more revisions later, it's done.
Of course, Amazon has different standards. Their publisher clients upload via FTP. (Now, be honest: can you guys imagine some of my less-techie clients--you've all read the stories--uploading an ePUB/MOBI and onix data via FTP?? Really?).
I am 99.99%
sure that Amazon has NO desire to provide "tech support" to the hundreds of thousands of self-pubs that don't know from FTP. Look at how much they
grossly underestimated the tech support that they'd have to provide, just in the arena of eBooks!
Hitch