Taking a Look At Kindle Format 8
Nate the greatest writes "Got a Kindle Fire? Here's your chance to try the new Kindle Format 8. The new format is in beta testing right now with a limited number of publishers, and a few days ago one of those publishers leaked the tools and the guidelines to me. It turns out KF8 isn't all that new. I've looked at the code, and I'd call it an attempt to graft a number of Epub features onto the existing Kindle format. It simply adds a lot of new formatting and is only slightly more capable than Epub. There's a number of screenshots at the link as well as a demo file. You can probably also find more KF8 ebooks in the Kindle Store; look for the Kindle Fire exclusive magazines and graphic novels."
It makes me sad that Amazon don't support it natively.
I'm wondering how many different "exclusive" editions publishers are going to publish in.
This is stupid. The only paid "exclusive" iPad publications I have are magazines that had a free iPad subscription when you bought the dead-tree edition.
It may be a sign of getting old, but seriously - if I laid down hard cash for something, I'm not in much mood to be a beta tester on it. This is doubly true for items which are locked down to one proprietary vendor. Triply true for an item (like, say, this tablet) which should be homogeneous to the point where developers really don't have to account for a wild variety of configurations, so the whole idea of accounting for differences should be pretty frickin' moot.
Now sure, I'll hackintosh my desktop box (which I had done) or happily goof off with a new Linux distro, but only because the former is assembled out of older parts, and the latter is in a VM first, before I decide whether or not to migrate it to my main home server box.
OTOH, the Kindle Fire is a product that (much like the iPad, to be fair) serves as nothing more than a front for Amazon's app/media store. Screw that - if they want me to test it out that bad for them, they can damned well pay me as a tester.
Quo usque tandem abutere, Nimbus, patientia nostra?
It's already a nightmare trying to cover all the bases as a book writer/publisher, adding more to the mix just makes things more annoying, confusing and likely to pop up crazy formatting mistakes. The forums are already filled with people having enough grief getting a decent looking eBook generated (though I blame them for using MSWord... tsk tsk *hugs LaTeX*). A lot of us would LOVE it if Amazon simply supported ePub, though that would in many ways erode their empire, at least in their view. Right now a lot of publishers are pushing out mobi / ePub / pdf as the main 3 formats to support, at least along with print publishing, unfortunately even within ePub there's a few quirks and you have to generate slightly different versions for iPad, Nook and 'everything else'. ... reminds me of the bloomen browser wars at their worst ... and to think I switched to doing novels / writing / publishing to try avoid this sort of crap *maniacal laugh*.
http://elitadaniels.com/
The AZW format got broken a long time ago, and while I don't purchase a lot of content from Amazon, I don't buy ANYTHING I can't break the DRM on so I can move it [sell it, give it away, etc] at my convenience.
I'm sure not going to purchase a bunch of content on Amazon that's lost/stuck because I decided I wanted to get a different device to read it with.
So, hows the cracking with the new format going? Once it's cracked, I'll consider buying it, at least once I decide to buy a KF.
Seriously, once books move into a more reasonable price range in general, I'd guess that it clearly doesn't make sense to use DRM. MP3's made this transition once the vendors realized that $20 for a CD wasn't going to fly for MP3's. Books are going to do it too, I suspect, and sooner rather than later.
But until then, I'll avail myself of the tools to do what the publisher failed to do right - and if that's not possible - well, I just won't buy it at all.
-Greg
This is rather some news, because up until now, Amazon Kindles have used *.AZW which is *.MOBI (mobile book) based. _NOT_ *.EPUB which is a main competitor.
I do not see anything about compression, which is my main reason for preferring EPUB over MOBI . The files are ~50% smaller unless there are photos/dwgs.
I really don't follow ebook formats because pdfs have always been my portable format of choice, and I have no ebook reader. I skimmed the article, but I could not find any points on what makes this superior to a pdf file. What advantages does the Kindle format or epub format offer which a pdf cannot do?
I saw some mention of audio and video and javascript, but pdfs can support that. Why recreate the wheel? From reading the article (where perhaps the author doesn't know what he is talking about?), it sounds like it's trying to do everything HTML can, but not be HTML.
Can anyone please clarify this for me?
Instead of coming up with yet another format that people will now have to support. I love my kindle, but they're seriously pulling a Sony on this one.
Yes Francis, the world has gone crazy.
From the sample file:
<package version="2.0" xmlns="http://www.idpf.org/2007/opf" unique-identifier="BookId">
It's version 2.
1 SVG images so that math books can be written. I heard KF8 is supporting it, but I found no reference.
2 Ruby annotations, essential to Japanese books. Still not supported.
Why can not they just go html?