View Single Post
Old 07-28-2014, 07:07 PM   #19
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by GJ Coop View Post
I'm wondering if I have a similar problem as the one had by Mathew Reuther in the following forum thread:
Months of Runaround From KDP Support: Font Embedding Fails...HELP!

He says:




That looks altogether similar to what my issue is, guess KDP is choking on valid HTML and CSS once again.

I removed all those useless spans although to be honest the Pages .epub conversion managed to create about 60 separate classes of which I only need about 8.

Guess I'll have to whack a few back in, and test it again.

This thread was from just on a year ago, I thought maybe KDP might have fixed it.

You want my short version, or the long version?

Short: OTF bad.
TTF Good.

Long:

18 months ago, we had a similar font-stripping situation. Some fonts simply will NOT work at the KDP; either the font, in its entirety, along with all font formatting, styling, etc., is stripped in the KDP "PW" (Publishing Workflow, which is what occurs to the book after you hit "save and publish" but before it goes on sale), or the font itself is corrupted (want fun? Try the dreaded Papyrus!!!). We have screenshots of some books that look like the lettering actually came "unstuck" from the page (think a Harry Potter spell), and the letters just moved hither and yon.

Now, you can sit there and bang your head against the wall from now until hell freezes over, or you can find another font. I'd highly recommend you find another font, and as Amazon tells you to stay away from otf's, I would. Even when we've tried converting some otf's to TTF, for pathologically-determined clients, we've had issues, so we tend to stick to TTF. We have had an ongoing discussion with Seattle--not the dreaded customer service--about this issue, and I'm not sure that they know what it is; it's simply a glitch. But they've already said, in the Formatting Guidelines, IIRC, to stay away from otf fonts.

Once you've made the book, upload it at the KDP, and ensure that you download the preview mobi. If the preview mobi is solid, you're likely in good shape. That's not 100% certain that the font won't be stripped out in the PW, but you can be absolutely positive that if the preview mobi doesn't have it, it won't be magically reinstalled in the PW. You'll obviously have to re-download the book (contact customer service and have the new version delivered to your devices, as they'll keep sending you the original otherwise) to ensure that the font is really, really there.

In all likelihood, it's not your coding--Reuter's issue was unique. We spent a weekend troubleshooting that book with him, as a favor, and NO font worked in his book. That WAS a coding error. Most font issues, though, are the font, not anything else.

Simply try substituting a different font, that's a ttf, and see if your problem resolves.

Hitch
Hitch is offline   Reply With Quote