Quote:
Originally Posted by Peter Ahlstrom
I had a weird error with KDP and font embedding yesterday. KDP reencoded the fonts (that I was using for headings) and stripped out unused letters—except some of the "unused" letters were actually used on an html file toward the end of the ebook, and viewing the Paperwhite view in Kindle Previewer had those letters replaced with a default font. It looked terrible. (On the Kindle Fire preview pages, it was loading the font from my computer, so the error wasn't visible.)
I fixed this by making a "display:hidden" paragraph on the title page of the book that used all of those letters. Now the previously missing letters are embedded correctly and displayed fine on that late html file. The only letters that are missing from the embedded fonts now are the ones that are actually not used in the book.
Before I got this error, my fonts were refusing to embed at all (after running through KDP; kindlegen embedded them fine). I fixed that error by following the advice earlier in this thread: explicitly classing any tag that used an embedded font and getting rid of multiple-classed tags.
|
Peter:
Have you checked the post-KDP book on an iOS device? With an .azk file? Our experience with :hidden on the iOS K4iPad app has been murky and unpredictable, at best.
And, yes: that's what happens, along with a host of other, undefined, unexplained and inexplicable font weirdnesses at the KDP. That's why I'm a big believer in, no matter how fancy the layout LOOKS, keep the coding as simple as possible, even if it's more work. It's just wildly unpredictable in terms of what will work. We're at the point that if a book has fonts, we test-load it at the KDP to see the post-upload mobi--
just to be sure.
Hitch