Quote:
Originally Posted by At_Libitum
I expect an eReader to honour the included CSS.
|
I believe Marvin respects it, apart from exceptions, which are bugs or Kris's strategic decisions that should be ironed out in future (for example, by making specific elements of CSS configurable on an
on/off-switch basis -- again, Moon+ Pro employs this principle nicely on Android).
Your example of the varying alignment is a very good one. If
2 various alignments are specified in the e-book's source code (default
and 1 non-default alignment), then Marvin should (perhaps optionally) respect that and display
2 various alignments in "Marvin's formatting", too. It's the perfect analogy to respecting publisher-
specified (as
opposed to default!) font and background colours (=
GitHub #99).