View Single Post
Old 07-17-2021, 07:27 PM   #7
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: 46,445
Karma: 169098492
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by Sirtel View Post
I have had no issues whatsoever with Vellum-generated books on any of my ereaders. And I only remove the body font and change the paragraph indent (sometimes the line-spacing as well) in them. I don't bother with media queries and other crap. It can stay for all I care.
Since she is reading on a Kobo using RMSDK (i.e. .epub not .kepub.epub), media queries are dysfunctional. As a trivial example, if you have a media query to display a graphics for a scene break and a fallback to display ***, you get both of them.

The body tag with it's sole content being: "font-family: Palatino, Malabar, Merriweather, "Droid Serif", serif;" is replaced since none of my ereaders have any of those fonts installed.

Sample of what I add:
Code:
body {
  display: block;
  font-size: 1em;
  line-height: 1.2;
  margin: 0 0 0 0;
  padding: 0 0 0 0;
  text-indent: 0;
  widows: 1;
  orphans: 1;
}

p {
  padding: 0.2em 0 0 0;
}

p.subsq {
  text-indent: 2.4em;
}
DNSB is offline   Reply With Quote