Originally Posted by DiapDealer
Regardless of table support in MOBIPocket vs Kindle1 vs Kindle2, my point is that it's not nearly time to start abandoning all concern for the older MOBI format/devices entirely (which is the impression I got from Oxford-eBooks). I myself, will continue to ensure that the MOBI portion of the hybrid MOBI/KF8 file is flawless and as visually appealing as possible; for as long as Amazon continues to sell ebooks for devices that only support the MOBI format (which I expect to be a good long time, yet). I would encourage other content creators to so the same.
Just worrying about the KF8 formatting being right and letting the MOBI portion just "happen" without a glance at—or concern about—its quality/viability is an example of shoddy craftsmanship, IMO. If that format (MOBI) is available to be delivered to the device of a customer who PAID FOR that ebook (and it is available if you're converting with Kindlegen and uploading to KDP), then you have a responsibility to make that MOBI version as good an experience as possible for that customer.
It's not nearly time to start selling ebooks whose creators just didn't know/care that the same code that creates pretty dropcaps in KF8 (or a tables that looks spectacular in KF8) will look atrocious in the MOBI version if you don't handle it correctly with the special media-queries that Amazon provides for such situations.
As long as people can still purchase your ebook in the boring old MOBI format ... then I feel you should still be concerned about the MOBI format looking smart.
I find that if I make it look good in KF8, then it is difficult to format for Mobi7 because of the HTML tagging. Any advice on how to make a nice looking Mobi at the same time as a decent KF8?