To KF8 or MOBI, that is the question…Posted by Guido ·
I’ve been working my way through Amazon’s new KF8 format specs a little bit, buy and while it is a great format, viagra order taking the Kindle eBook format to where EPUB has been for some time, for sale I have to say there are a few things that stick out like a sore thumb.
One of the issues that truly and really disturb me is the lack of support on anything but the Kindle Fire. Although Amazon had initially announced that the current generation Kindles and software readers would be KF8 capable, that statement was simply not true. It has since been revised that these devices will support KF8 some time in the future. In the real world that is a big difference.
It means that if you’re using KF8, you are currently limiting yourself to the Kindle Fire platform. While it is clearly a successful platform, it is nonetheless a niche.
The other thing that sorely disturbed me is the fact that Amazon is in no real way accommodating MOBI alongside KF8. By this I mean that Amazon is not willing to allow you to upload a KF8 version of a book and a MOBI version of the same book in order to enable proper support for all their Kindles. This problem extends not only into the publishing platform but actually starts at the root, the authoring of eBook.
Although with the new tools, Amazon has set up media queries, using an HTML @-rule, which allows you to define different styles for the KF8 and MOBI builds generated from your submission file, it is sadly a rather mediocre solution. It does help, however, in some cases. If you want text to flow around an image, a feature the KF8 format finally supports, you can tell it to use a different style setting for the MOBI version, in which you could center the image and then force a line-break and start the text on the next line. In theory, this would work. The problem seems to be that the old Kindles do not understand the
display: block property that would be necessary to enforce the line break. Unless I find some way to tell the old Kindle that it needs to perform a line break after an image, this media-query fix is useless in this case.
The same is true with tables. Old Kindles have no table support. It’s been a major problem in the past, as it makes tabulating information impossible. If you display a KF8 table on an old Kindle it will be flattened, which means every table column will appear in a separate line. From a technical standpoint it makes sense because it is the easiest way to parse a table without actually implementing support. In practice it defeats its purpose, because it completely mangles and intermingles data that should, by rights, be separated — hence the use of a table.
Sadly the newfangled media queries won’t help in this case either, because the only real substitutes for tables on old Kindles are either completely restructured data, which requires different structural code and cannot be managed using a style, or you could replace the table with an image, which also requires code and cannot be achieved via a style setting. Ergo, the media query once again misses the mark.
Nonetheless, the media queries are great and will help on occasion to allow a certain degree of “correction” between versions. At least it’s a try…
In my opinion, however, Amazon should allow publishers to upload separate KF8 and MOBI versions in the future. It would be the only way to make sure that both versions can be authored to the best of the respective format’s capabilities and look as best as they can. Trying to automate the process – even with a media query hint has never been a good idea. The Smashwords Meat Grinder is the living proof that this Least Common Denominator approach is getting you nowhere but in trouble, and therefore I sincerely hope that Amazon will rethink their strategy in that respect, and while they’re at it, maybe they should look at their documentation also and rework the CSS selector listing they have in there, because as it stand, it would lead you to believe that old Kindles can’t handle any CSS, as every single selector is marked off as “unsupported.”
I wonder if they have actually corrected some of the issues I raised a while ago in the new platforms, such as incorrect em calculation, the right margin and padding issues, the missing borders, and so forth. Maybe some of you reader can enlighten me on that, since I have no Kindle Fire and none of the latest Kindles at my disposal.