harry said:
> The ability to change font seems to be associated,
> almost inevitably, with the requirement that
> a document only contain a single font.
even if that is the case, i do not think it's a bad thing.
i'd rather have everything in the one font that _i_ like
than in the two (or more) fonts that a _designer_ likes.
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.
this is my opinion. but this is the way i built _my_ viewer.
-bowerbird
|