Thread: Using Google Fonts as fallback for Adobe Fonts
View Single Post
Old 01-26-2022, 04:38 PM   #10
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 80,061
Karma: 147983159
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by ValTim View Post
Is there a problem with Quicksand as font? Why do you remove it from eBooks? I've used other fonts from Google, and they are correctly displayed in almost every app.
I need VAG because the client is using this font in the print version, and requires it to be in the eBook as well. Apple is going to be the major vendor, and it should work there. The free alternatives to the font (Fredoka One, Quicksand) are not so similar.
If you are selling eBooks for Kindle, then you don't want embedded fonts if you can help it. Most people won't be trying the Publisher font option to see if there are embedded fonts.

Then you have ePub where you do see the embedded fonts, but if the person doesn't like the font, s/he won't be happy.
JSWolf is offline   Reply With Quote