Quote:
Originally Posted by jcsalomon
A book I’ve just typeset had its EPUB start location set to Preface.xhtml, just after the TOC (nav.xhtml) and just before Chapter01.xhtml. Kindlegen produces a file that correctly opens where I want it to. And Amazon set the SRL to Chapter 1.  |
Yup. You're uploading a MOBI, I'm inferring, from your information?
Quote:
Here’s the entire body of the preface, as the author wants it displayed:
Code:
<body>
<h2 class="sigil_not_in_toc">Once upon a time [author’s text elided]</h2>
</body>
I know there won’t be any guarantees, but has anyone had any luck with something like this? Perhaps if I included a dummy
Code:
<h1 style="display: none;">Preface</h1>
or something like that?
On second thought… Hmm, I’d been abusing the <h2> tag for this formatting. What happens if I add this Preface to the TOC? I’ll get back to this thread after I’ve tried it.
|
Gotta say, yes, that's abuse. I'm unclear as to why you think creating a heading class for that would do anything whatsoever for the SRL? We use heading classes for all our headings, not to be redundant, e.g., "preface," "acknowledgements" and so on, and I don't see that that's had bupkus to do with it. What's your thinking?
Amazon's position--and trust me, I've had scads of emails with Seattle's KDP department about this--is that the SRL *will be set* to the first page of relatively full text, after the TOC.
Period. However, if the author-pub emails them, post upload, once the book is on sale, the every-day KDP will adjust the SRL, generally speaking, to where the author-pub wants it to be. That's been our experience.
Quote:
Originally Posted by stumped
It is true
. I had a game guide from KU. TOC sent me to a single page of actual relevant guide at end of book. Before that, visible in Kindle for PC, were 200+ pages of misc junk, including a wedding planner guide, in French.
{SNIP}
KU is a scammers paradise, there are several other scams ongoing.
http://selenakitt.com/blog/scamazon-...ting-millions/ |
My ponderment is, how does that possibly work? Obviously, the tricked reader will return the book to Amazon, and tell them why. Payment isn't made instantaneously to the scammer, so...I can only assume that the entire thing is contingent upon the scammees (the readers) NOT reporting the scamming book to Amazon, AND, having received it via KU, so that the scammer gets the payment from KU on pages read.
So--the simple way to kill off scammers is for the reader/purchaser/downloader to report the book to Amazon. Amazon would "return" the book, and deduct any payment.
It's on the readers, then. I did some very rough math last night and I think we can safely assume that 1,000 books a day have been published pretty much every single day--7/days/week--since the first day of 2010, on average. Amazon would need 125 people doing NOTHING but book-checking (8 books/day per checker) to keep up with that. If I were Amazon, AND I did that, bygod, I'd be taking more than 30%.
That's my $.02. If the reading public makes even a tiny effort--any effort at all--the scammers won't get a dime. But expecting Amazon to do
everything--including finding every scamphlet--that seems unreasonable, to me.
Yes? No?
Hitch