Quote:
Originally Posted by newrome
The styling a publisher chooses has a purpose. Personally, when i am reading a text which has an inset quote, i would like it to appear as...an inset quote. The same goes for font attributes... I don't want that information stripped out of the text. To suggest that this makes for a better reading experience makes little sense to me... But you don't care about such things, that's great.
|
You might want to check that you don't have Stanza set to ignore CSS. I've never had a problem with stanza on iPhone recognizing inset quotes, font sizes and weights, etc. Most of that boils down to authors/publishers properly formatting their ebooks in the first place (PDF is
NOT a valid ebook format, as so many publishers seem to believe). For example, if you want to have an inset quote, then it should be rendered in a blockquote tag in the epub. If it's not, whoever laid out the ebook failed.
Unfortunately it's still very rare to find books that are well-formatted for an ereading experience. Until that day comes, I'd rather have a reader that lets me make up for their shortcomings by overriding many settings (font, indent, paragraph spacing, line spacing, etc).
And for what it's worth, iBooks, Kindle, and many dedicated ereading devices override font choices anyway. If an author is more specific than serif or sans serif, the chance that the font they want is one of the few that are provided by the reader or that the reader supports embedded fonts is pretty slim.