Quote:
Originally Posted by bowerbird
harry said:
but i don't necessarily think it's the case that we _must_
enforce such simplicity. any e-book viewer worth its salt
-- (and yes, quite sadly, there are _many_ that are not) --
should be aware of the _structural_ aspects of the book,
i.e., which parts of it are headers, which are block-quotes,
which are tables, and so on. and it should let an end-user
specify _how_ each structure is rendered (font, color, size).
note that this is quite different from mere "font families";
that's another way to do this, but i'd call it the wrong way.
|
Sure - that's basically the purpose of cascading style sheets in HTML. Very powerful indeed, but (to the best of my knowledge) none of the popular eBook readers support CSS.
Quote:
|
this is my opinion. but this is the way i built _my_ viewer.
|
What is your viewer?