View Single Post
Old 08-29-2011, 05:28 PM   #21
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,696
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by JSWolf View Post
Try Calibre to convert the same ePub to Mobipocket and post the results. I'd be interested in reading about this.
It's a given that calibre does a much better job of converting the ePub's CSS into coherent (and visually similar) mobi's. That's not really even a question.

The problem is that since MOBI is still ultimately a proprietary format, many want to ensure complete compatibility with Kindle devices/apps by using the approved tools. Especially if it's a commercial project. I may be being a bit alarmist just to make a point, but what if there's a tiny detail that's been overlooked in calibre's (or anybody's) assumptions about the MOBI format? Would it not then be possible that a future Kindle firmware/software update could render previous calibre converted MOBI's defective in some way?

Basically I'm saying that just because calibre conversions may be easier and even often look better... that ain't the whole picture.
DiapDealer is offline   Reply With Quote