View Single Post
Old 02-13-2020, 06:13 PM   #11
hobnail
Running with scissors
hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.hobnail ought to be getting tired of karma fortunes by now.
 
Posts: 1,590
Karma: 14328510
Join Date: Nov 2019
Device: none
Quote:
Originally Posted by Blakestr View Post
What about KFX? Doesn't it let you take advantage of the different fonts, again it's been awhile but I know I have some books whose font can't be changed.
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

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

Code:
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.
hobnail is offline   Reply With Quote