Quote:
Originally Posted by Faterson
Not necessarily. And certainly no Marvin user should be required to edit any e-book he or she wants to read. 
If numeric values are assigned to the various font size options, then Marvin can approximate the resulting, actually displayed font size, regardless of the CSS used, to the font size set by the Marvin user as preferable.
This is definitely possible to achieve; look at Moon+ Pro Reader on Android. |
Marvin should not be doing what you say it should be. It should be respecting the CSS. If the font size is set to small, then it should display smaller then no font size. If the font size is x-small, then it should display yet even smaller. The problem is that sometimes a specific font size is properly used. For example, sometimes small is used for simulated smallcaps. Having small display the same or close to the size you use to read with, you lose the smallcaps. The way Moon+ does it is wrong and if Marvin was to do things that way, I'd have to report it as a bug.