Quote:
Originally Posted by DNSB
Remember as Hitch mentioned, if you try to use a body font in an ebook sent to Amazon, it will vanish like the disposasteins of yesteryear. Set a chapter header font, no problems.
On the last ebook I saw that attempted to get around this, the author styled each paragraph with the embedded font using style= and it didn't work.
|
That ^ is exactly right. Amazon caught on to that trick ages ago (2013, by my personal knowledge) and there's a styling limit, inside the renderer (the publishing workflow renderers/processors) for style= or font=. Nukes it altogether.
We had this truly godawful book. It was...I can't even describe it. It was like a person's journal/memoir/something. And it careened from font to font. It also made extensive use of Arial. Well, like good little obedient doggies, we licensed the fonts and off we go and we could NOT NOT NOT get Arial to "take." Something about the usages, too many fonts, too much Arial in conjunction with (IDK what else).
Seriously, if you removed a paragraph with Arial, you could add one. We demonstrated it over and over. There appeared to be hard limit, in how many paragraphs you could have, in Arial. We tried normal CSS; we tried inline; we even tried putting it on the HTML tags (the customer was ADAMANT!), and we never got it to work. Use it all the time for headings and subheads, and for books where it's the only font...but there is something, somewhere, that makes it explode with a certain (number/type) of other fonts.
Most bizarre font thing--well, almost--that I ever saw. The Daily Prophet Effect--the one where the text appeared to come "unstuck" from the page and float around, in Previewer and on-sale--that was the MOST bizarre. We'd upload this perfectly normal novel, and when you'd preview it, the text of the book simply...came apart. And floated around the page, as if unanchored to lines, grids...weirdest thing ever. Customer as horribly unhappy with us. Never did figure out
WHY.
Hitch