View Single Post
Old 06-22-2023, 12:57 AM   #1458
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,324
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Renate View Post
I really don't understand what you're objecting to.
Your ereader app should have a default sane CSS.
Reading plain text in my chosen font with justified layout is fine with me.
I'm not saying that I do this to all books, just books with egregiously offensive style.
Default sane CSS? Are you living in the same world as the rest of us?

Basically, I've found renderers come in two flavours. One that defaults to the CSS defaults which aren't all that well defined or useful and tend to give a pretty ugly page display and the other that has it's own builtin CSS and very often make it a pain to try to use the epub's builtin CSS.

An example of the first type would be Adobe's ADE and it's derivatives, an example of the second type would be Moon+ and all too many other Android renderers.
DNSB is offline   Reply With Quote