View Single Post
Old 04-05-2012, 08:07 AM   #4
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,840
Karma: 207000000
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
CSS doesn't work at all in the MOBI format (pre-KF8). All CSS gets converted to HTML 3.2 attributes (if possible) when the MOBI gets built.

You say you've "deconstructed" some Kindle books, but I'm seeing calibre CSS, so I suspect you've either converted it to ePub or HTML (or you've captured the intermediate OEBPS step of a conversion using calibre's debug feature). That's not deconstruction per se... that's conversion. You'd need to use something like mobi_unpack.py to view the raw mobi markup code that's actually being implemented inside a MOBI file. There's also a calibre plugin version of the mobi_unpack.py script that may be of use to you.

The KF8 format can achieve pretty much anything that can be done with the ePub format.

Last edited by DiapDealer; 04-05-2012 at 08:11 AM.
DiapDealer is offline   Reply With Quote