View Single Post
Old 01-28-2012, 12:54 PM   #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,358
Karma: 203720150
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
You may have a point! I'm still yet to figure out how Kindle handles CSS, if it essentially doesn't use CSS.

Do you know which CSS the KindlePreviewer for iPad/iPhone uses?
The regular-old mobi format does not use CSS... correct... but KindlePreviewer (and Kindlegen) both convert user-provided source CSS to HTML 3.2 attributes when converting.

The new KF8 format does use CSS (very similarly to ePub), but the Kindle Fire is currently the only device that supports KF8 (the various reading apps will likely support KF8 sometime in the future).

So right now... KindlePreviewer and Kindlegen are building a hybrid MOBI that contain both the regular-old MOBI and the new KF8. Devices that support KF8 will use that (currently only Kindle Fire) and everything else will use the fall-back MOBI.

The new Kindle Publishing Guidlines (Section 8: Media Queries) provides about four different ways to differentiate between the CSS that's used to build the MOBI and CSS that's used to build the KF8.
DiapDealer is offline   Reply With Quote