Quote:
Originally Posted by Hitch
OK: that's a completely *different* problem. The font-stripping problem removes the font folders, entirely, from the built mobi. You're using character slots outside of what Amazon has available, basically, sort of like Mandarin, if I had to guess.
|
Nope. US ASCII. No high ASCII characters, a handful of standard special characters like curly quotes, em dash, en dash, prime, double-prime....
My best guess is that the KF8 file that came out of KDP actually contained the embedded fonts, but in a badly broken form that caused them to act like they contained no glyphs.
On OS X, if you opened the file, it used the Mac font system, which correctly refused to open the broken fonts; the result was that it fell back to default fonts.
By contrast, Kindle Previewer on whatever platform the website uses (Linux?) is much dumber, and tried to use the broken fonts from the bundle, resulting in the broken characters.
Of course, this still raises the question of why an innocuous line of CSS asking for geometric precision in font rendering would cause KDP to spit out a MOBI containing corrupted font resources, but....
