Quote:
Originally Posted by kAlvaro
I happen to be a web developer and I admit that CSS typographic controls are not as fine-grained as those you find in desktop publishing software but
|
That's not what I meant.
With Ebooks you have a conflict of interest: There is the CSS that says the book should look so-and-so; but whoever reads the ebook has its own personal preferences so the reader offers some settings to make it look so-and-so.
Which setting prevails? Unfortunately most of the time it's the CSS and the readers preference is ignored.
You almost don't have this problem with webpages, people just accept a webpage the way it was intended to be by the web designer, although browsers do have an option to mix custom CSS in (or there are even addons for monkeypatching), most people don't use this [and if they do it breaks a lot of sites, even setting a minimum font size in firefox can ruin the design of some pages].
With ebooks you get crazy font sizes, custom paragraph indentation line spacing etc. etc. etc. and that's fine, readers should be allowed to do all of this stuff - but the reality is, ebooks come with a ton of unnecessary embedded CSS bloat rendering most of those settings ineffective.
An ebook is not a webpage. Webpages need lots and lots of CSS to make them look good. Ebooks look better [and give readers more freedom] the less CSS they have.