I agree with danrodney. The ability to override the content creator's CSS is a handy feature... but there's just no
way that ignoring the content creator's CSS
by default makes any kind of sense.
Punishing the many (who are creating tasteful content with embedded fonts for chapter headers or other special text) because of the few that are causing more tech support calls...
Quote:
|
Or to put it another way the user complaint of "I can't see the content" trumps "This looks bland"
|
... seems quite draconian.
Unless I've completely misread the situation (which is always possible).
The way I'm reading this, is that the font I embedded to use for dropcaps at the beginning of chapters would now be ignored by default. Same with chapter headings. If so: making the user jump through hoops in order to see exactly what the content creator intended them to see seems incredibly presumptuous and short-sighted.
I agree that some overuse font embedding in an attempt to micro-manage every single aspect of the reader's experience with their book—and there needs to be a way to circumvent that—but punishing the vast majority that are doing it "right" doesn't make a whole lot of sense to me.
Again... maybe I'm misreading.
