@jphowell...
Quote:
|
Another example is "Pseudo selector counter type is not supported in Enhanced Typesetting. Unfortunately, Kindle does not currently support this markup. Amazon is actively working on this error. For now, we recommend to upload this book without Enhanced Typesetting enabled." That message also appears to explicitly give the publisher a pass on that problem.
|
Yes, that sort of error is bound to create confusion for Word doc uploaders for sure. And yup, I reckon professional formatters and Hitch are going to get more business because of it.
Quote:
I doubt that will be much of a factor in this situation. Any Enhanced Typesetting problem with a Word document that prevents it from being directly published will also prevent Kindle Create from accepting that document since KC performs the same checks during import.
Today 12:25 PM
|
Sorry, I don't agree with you here. When you ask why Enhanced Typesetting has been introduced and so fiercely pushed for Amazon ebooks then the answer has to be "To create higher quality ebook features and internals." As you say, this also applies to all upload formats -- including Word docs, epubs and KFX. But the easiest way for any indie author(without any epub or html knowledge) to achieve ET is just to create an ebook using either Word on it's own or Word/KC(which allows more useful options for better interior styling). I would have to also say that Kindle's proprietary fixed format(as KFX) is, frankly, godawful and still poorly supported by Amazon developers. With way too many painful downsides to ever be deemed as a useful format. Perhaps that's also deliberate Amazon policy to force authors to use the reflowable format instead. That's not such a bad policy I suppose but who really knows?