Quote:
Originally Posted by Tex2002ans
Yuck... that reminds me when I read Steven King's 11/22/63.
34 embedded fontfaces, so many were meaningless.
|
I have read
11/22/63. I know why that was done. It was done to simulate the way it was done in the pBook. The thing is, 34 complete fonts were embedded. S&S should have subset all of those fonts. That would have saved a lot of space.
But the way Penguin does it is 100% useless. It's just an advert.
I've taken to removing most embedded fonts and using sans-serif where a sans-serif font was embedded. If I do decide to keep any of the fonts embedded, I will subset. Most fonts are not actually needed. There are times when some extended characters are used and yes, it better to make sure they are available. But why do some eBooks have a span around these characters? That's just silly.
Most of the time, I convert these ePub 2 in ePub 3 clothing back to ePub 2 because I don't like the excess span this and span that with epub:type all over the place. It would be a lot better to have this sort of thing once in the header of the HTML file and be done with it. Role, epub:type, figure, section and other stuff that's actually not needed is what I get rid of. If I could put a section code into the header that tells what role the HTML file plays in the ePub, that would be OK.
But as for fonts, it seems most embedded fonts are not tested with an eInk screen as they are too light. For example, Adobe Garamond Pro is used sometimes and it's way too light. Use the semi-bold versions for normal and italics and extra bold for bold and bold-italics. Then it would be OK.
I cannot see anyone getting in trouble for using a graphic image that contains someones copywritten fonts that were not paid for. But you never know what could happen. So the thing to do is try to find a font that's similar enough that's free.