View Single Post
Old 11-14-2012, 10:47 PM   #5
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: 9,515
Karma: 43764640
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
The problem is that you've not converted the html from your original source (whatever that may be) into any kind of valid mobi markup. It's a MOBI by all external appearances (the binary database structure is valid), but that's about it. Your internal mobi markup frankly looks like straight-up HTML4 -- complete with inline CSS. That'll never fly on any MOBI app/device. Calibre views it because calibre's viewer doesn't really render MOBIs. It extracts the contents of all ebooks into an OEBPS-compliant format for viewing.

Hit up the MOBI WIKI here, and use something like Mobi_Unpack.py to see what the markup looks like inside some valid MOBIs.

Last edited by DiapDealer; 11-14-2012 at 10:50 PM.
DiapDealer is offline   Reply With Quote