Quote:
Originally Posted by kso
Thanks for that. Can you confirm (or deny) that MOBI7 is what kindle used in medieval times, KF8/AZW3 is the last format used, KCR/AZK the one that introduced the switch from pure Mobi, and KFX is the Wall they're building? That would make sense to me as someone who's relatively new to kindling things.
Yes, I've read somewhere that (paraphrased) "If you're trying to do something fancy on a Kindle, don't". I'm close to agreeing.
And I fully understand that KFX is a one-way format (mostly anyway) and that "Enhanced Typesetting" is probably no more than a justification for switching to it.
What I don't know is: do old devices, like the Voyage or DX, get ET in line with newer ones or are they stuck at whatever capability and bugginess they are at now?
At the moment I'm thinking of getting a used Voyage. Any particular System Revision I should look out for if I want the device to match a large number of its siblings?
thanks
klaus
|
KF7 isn't that far back--the DX, which was sold fairly recently, in terms of this decade, was still KF7, as was the KKeyboard, and really, so is KCR.
AZK is not a real format. It's a testing/preview format, solely for the iOS devices. It has no purpose other than previewing iOS device appearance. KCR is a reader, not a format, in and of itself. The output files from KC are kpf, which result in KFX final files.
The Voyage is
not a KF7 device; it's a KF8, but has that image-display glitch. The DX is a bonafide KF7 device. NO, the older KF7s will never, afaik, have ET or KF8 or anything--I don't believe that they can. Amazon still supports them, unlike Apple and its devices/software, but they can't seem to upgrade them to match their newer brethren. It would be much, much easier on we of the bookmaking brigade if they could.
Honestly, you can do a lot on a Kindle--but the coding that you were trying would be difficult to implement, even in ePUB format. I wouldn't bet actual money, but I'd be surprised if that worked on all the Nooks, for that matter. eBook HTML is not web html; it's a very specific subset, whether it's for ePUB or MOBI. Yes, MOBI has some additional problems, but all in, I'd rather have a retailer that supports what it sells, philosophically, than one that doesn't.
Hitch