View Single Post
Old 03-10-2020, 06:26 PM   #17
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by beiti View Post
I already did tests of different fonts on different e-readers (in case I have to embed one). For books to sell it's always a legal issue, too. (One more reason to avoid embedding if possible.) Most font collections include the right to use them für print and PDF, but not for EPUB. But I do have some fonts I'm allowed to use in my ebooks – and "America Typewriter" happens to be one of them. What also works is "Courier Prime". Both look okay (but not always perfect) on different e-readers I tried.

BTW I found out that there can also be a difference between different readers with 800x600 resolution. The old Kindles seem to use a different font rendering method than e.g. the Tolinos. On Kindle everything looks sharper, but with some fonts also less smooth (what makes using alternative fonts more difficult). The Kindle 800x600-devices work best with the built-in Caecilia font (easier to read than Bookerly on the higher resolution Kindles, if you ask me). And of courese there are different font sizes which make a difference, too. Very hard to find a font to embed that works everywhere, so embedding will never be my first choice.
I have a stoopid question:

How do you know that you named these fonts correctly? I mean, I deal with this sort of thing all the time. How do you know that Bitter isn't "Bitter_reg" or Bitter_Normal? You have "Source Sans," but my Source Sans are all named something like "Source Sans Pro" or the like.

Baskerville? Hell, which one? BaskervilleMtStd-Regular, or ITC New Baskerville Roman, or...well, you get the idea. I run into this in Archetype, often--if I don't name the precise weight of the font I want, it doesn't work at all.

Your embedded fonts work because a) they're embedded and b) they're identified--named. Those you're trying to call, not so much.

I just think that part of the problem here is that you're using generic, "street" names for fonts and they can be, IME, downright picky, particular and persnickety about that stuff.

One last comment--any bookmaker worth their salt can make a Kindle ebook in which they can grace the book with a body font that the reader can override with a click. Thus, best of both worlds--can see if if'n they wanna, can turn it off if'n they wanna, don'tcha know?

Hitch
Hitch is offline   Reply With Quote