Quote:
Originally Posted by jhowell
I believe that how a book renders as AZK/KCR is no longer relevant unless the book will not be supporting Enhanced Typesetting, such as a fixed layout children's book.
|
Sez you {grumble grumble}. I wish someone would tell that to my clients. If I deal with one "I sent my mobi to my iPad and it looks HOOORRRIBLE!," complaint per week, I deal with 3. It's just...
grrrrrrrrr.
Does anyone here think it's possible that the old xpgt doodad plays a part in this? The original iBooks app was built on ADE, right? I realize that sounds a bit backwards, but...I wonder. I mean, the cheapie shops, like the Big publishers used for backlists, used to just take the scanned crap, slam it into ePUB format, slam in an xpgt page template and then build the mobis by dropping the ePUB's OPF onto KG, right? I realize that we're talking K4iOS, not iBooks, but...I mean, what I've seen in the old big-shop backlist conversions is pretty criminal.
I realize that's an unformed idea, but I was trying to think what might cause that. I've NEVER seen this and that's bloody odd.
Quote:
|
Most books will support ET and Amazon will deliver them in KFX format to the K4iOS app when actually published. (Perhaps a few customers still have iOS devices that only run a very outdated version of the app, but I doubt that there are very many of those left.)
|
Hmmmm..well, all my customers seem to have the old one.
Quote:
|
I do occasionally want to see how a book will look under K4iOS, not because I am publishing, but because I want to understand how the Kindle platform works. I use my KFX Output calibre plugin in CLI mode to convert from EPUB to KFX and sideload that via iTunes. (Using the CLI mode of the plugin avoids manipulation of the book by calibre's conversion pipeline.)
|
Hunh, interesting. I don't think I knew that. Thanks!
Hitch