Quote:
Originally Posted by Notjohn
Charles Seper has this to say on the subject:
If this was true yesterday, it isn't true today. I just tried it and monospace works all by its lonesome. This is what works for monospace:
font-family: monospace;
font-family: 'Courier New', Courier, monospace
These do NOT work:
font-family: 'Courier New', monospace
font-family: Courier, monospace
|
Yes; that's something similar to the discussion I had with my colleague.
Quote:
As to heading fonts, they've been very hit and miss for a long time now. Some fonts work, others don't. And some only work if you list them in a specific way. My way of making helvetica still works fine:
font-family: Helvetica, sans-serif
Specifying Arial doesn't:
font-family: Arial, sans-serif
|
To this....MANY fonts work. LOTS. I have not found fonts, generally, to be "hit and miss." Yes, occasionally, Amazon does something behind the curtain that affects the font intake, and occasionally, some fonts, for reasons that are utterly unclear, don't work. (Personally, I think we should all send TY notes to Amazon for nuking Papyrus, for which the design community loves them.) However, I've used Adobe Fonts, Linotype Fonts, MS fonts...all without the earth falling in.
I suspect our facility with it is because of all the white-label and INDD work that we do; we
have to make fonts work. Most conversion houses don't even offer it, so...{shrug}. And frankly, if we're one of the few that's figured out the secret sauce, {more shrugging}, then that's okay with me, too. Odin knows, we've certainly put enough hours into it, not only initially, but during the prior wonkiness in 2014, and now
again with this new bit of crazy, to want to recoup
some of the costs of figuring it out. After all, troubleshooting at my shop isn't freebies to me; there are very real, hard, cash costs associated with that.
Hitch