Quote:
Originally Posted by Hitch
I want to add, that I'm extremely pleased for you, BUT:
Just the past few days, we've noticed that EVERY FONT, of every kind, whether put on the HTML (inline), CSS, added for the body, bodysection, individual elements, (etc. ad infinitum) has been getting completely ripped out, in toto, by Amazon.
I was in communication with them starting late on Friday (at 5:05, naturally, when we confirmed that it was not a freak incident with one book), over the entirety of the weekend. I don't think that THEY know what's causing it. The problem seemed intermittent on Saturday.
Dreamwriter:
You got your book through? So, as of the post step-6, your book has fonts? If you make it that far, it seems you're home free, and then use that mobi as your "final."
What a giant PITA. As "youse guys" know, we do a ton of white label, which means a TON of fonts, and we've had agita since Friday on this.
Hitch
|
Hitch, the new development you're reporting is very troubling—and exasperating!
Yes, my four e-books now have embedded chapter/title fonts and the "called" body fonts specified earlier, in both downloadable samples and purchased books. No fonts were stripped from those e-books, and the Publisher Font option is available in the device menu once again.
However, the last files I uploaded for my four e-books were sent to KDP between March 31 and April 3—well before you noticed the new problem.
It's gotten to the point that I'm reluctant to upload updated files to KDP since the results are so unpredictable. It'll be "interesting" to see what happens when I publish my next book in a few months.
I definitely won't update the back matter in my other e-books at that time unless the problem's fixed!