Quote:
Originally Posted by JSWolf
The problem is that while you can do more advanced formatting with KF8, Mobi is a limiting factor since your eBook also have to work on obsolete devices that only support Mobi. For most books this is not an issue. But for some, it is. This is why I think Amazon should allow eBooks to be KF8 only and not support Mobi where that's not feasible.
|
I doubt that MOBI7 will be going away any time soon. Publishers need to make the best of the current situation.
Besides the older Kindle devices that only support it, MOBI7 is also used as the basis for the primary format in Amazon's Kindle Cloud Reader (
read.amazon.com) and as the fallback format in reflowable books produced using Amazon's Kindle Create publishing tool.
The discussion in this thread so far has been about tables. Previous threads on this topic have focused on the differences in how images are displayed between MOBI7 and KF8 and how to adapt books to have them display as nicely as possible in both formats. That is often a bigger concern for publishers.
Quote:
Originally Posted by stumped
tables are a bad idea, generally, for reflowable books
what looks great on one test device can look awful or be cropped on other different sized devices.
|
I agree that tables should be avoided in e-books when possible. Section 10.5 of the
Amazon Kindle Publishing Guidelines has some suggestions on creating tables, such as keeping them small and simple. The KFX renderer in newer Kindle apps and devices has a pop-up table viewer that helps a bit.
Many will suggest replacing tables with images, but that has some downsides. For example the text will not be in the reader's chosen font. Also text search and dictionary lookups will not function.