View Single Post
Old 03-20-2013, 07:23 AM   #8
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: 27,549
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
But just to be clear, Harry: the css technique described above is a perfectly valid way of getting Kindlegen to build the joint mobi/kf8 from slightly different sources (albeit in one document) for select sections. But you're right. It has nothing to do with a device/app parsing the CSS and deciding which portion of html to "show." It's about telling kindlegen which code to include in which portion of the joint mobi/kf8 (and which portions to leave out).

Just didn't want anyone to think the CSS technique described was invalid. The media queries are build directives, rather than display directives. The code intended for KF8 won't even be included in the mobi portion of the joint file--and vice-versa.
DiapDealer is offline   Reply With Quote