View Single Post
Old 03-21-2013, 01:19 AM   #10
dgatwood
Curmudgeon
dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.dgatwood ought to be getting tired of karma fortunes by now.
 
dgatwood's Avatar
 
Posts: 629
Karma: 1623086
Join Date: Jan 2012
Device: iPad, iPhone, Nook Simple Touch
Quote:
Originally Posted by HarryT View Post
Sorry, but that's not true. Mobi has no - zero - support for CSS. It just plain doesn't support it. The conversion tools (Kindlegen, Calibre) will do the best they can to convert CSS into the HTML tag attributes that Mobi uses, but puttting CSS into an actual Mobi file will get you nowhere.
I'm not talking about in the raw MOBI file—nobody sane modifies those. I'm talking about CSS in the source content. Kindlegen translates more CSS than most of the ePaper readers reliably handle. The iOS version of Kindle then interprets the resulting HTML tags where some of the other readers would ignore them.

For example, in iOS, you can have font colors other than black and white. You can set background colors (which are handled to varying degrees in different ePaper readers). And so on.
dgatwood is offline   Reply With Quote