[ps67]

Originally Posted by hobnail

I can't remember if this was on the Kindle or the Kobo but I've developed this voodoo where I delete all font-family lines in the book's CSS when it's for the global font (i.e., not for monospace for things like typewritten letters). Like you I'm never bothered by whatever font is used in a printed book (but then I've noticed that fiction always uses some reasonable serif font). But with eink ereaders I always want the Cacaelia or Bookerly font.

I can't remember if they specify a specific font family, as in

body {
  font-family: Arial, Helvetica, sans-serif;
}

or just

body {
  font-family: sans-serif;
}

but in either or both cases I'm then not allowed to specify Cacaelia as the font I want to use in the ereader's settings.

I can't understand why people feel the need to set a font for the body/paragraph text; leave it up to the user.

I don't think that this css will prevent You to change the font in a Kindle with Caceilia or Bookerly, I will try because I never encountered that issue.

Edit: a Kobo is a different animal: if I remember correctly with epub it respect very strictly the css, but I patched it to always use my preferred font.