Quote:
Originally Posted by Faterson
Jon, I basically agree with you. But whereas those CSS deficiencies are typically invisible, or at least inconspicuous, to the naked/non-expert eye, missing or buggy functionality – such as no option to sync annotations in Marvin, or the corruption of source text when exporting annotations in every e-reader app I've yet encountered – is glaringly obvious to everyone.
So, yes: Marvin is very good, and so is MapleRead on iOS and Moon+ Reader on Android – but none of these apps is truly "great", or "5-star software", or "professional-grade" software (whichever epithet one might prefer).  |
First off, lets fix the rendering bugs and then work on the annotations.
The CSS deficiencies are not invisible. They are very very noticeable. For example, with Marvin, in publisher layout, if you don't have a good embedded font, whatever the default font is, it's AWFUL! You don't get hyphenation. There's no reason not to allow a choice of default font. Then there are the major bugs in the override mode.I've seen simulated blockquotes not display properly (left/right margins ignored). This is a major bug.
So we need all ePub reading software to start off respecting the CSS. Then allowing overrides from there with all the overrides being able to be turned off and the CSS values being used.
I want to know why it is most ePub reading software feels it's OK to toss out the CSS?