Quote:
Originally Posted by dgatwood
If you mean my books, then no, it was straight US ASCII. No high ASCII characters except for a handful of entity-encoded bog-standard special characters like curly quotes, em dash, en dash, prime, double-prime, degree, and maybe one or two others.
My best guess is that the KF8 file that came out of KDP actually contained the embedded fonts, but in such a badly broken form that they effectively 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, hence it looked like the fonts had been stripped.
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 missing glyph boxes.
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 now that I know that it does, I've removed that line of CSS for now, and everything goes through cleanly, at least for me.  |
dg:
When you say:
Quote:
|
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, hence it looked like the fonts had been stripped.
|
...what do you mean? Do you mean, KindlePreviewer on a Mac? Something else on a Mac? Can you clarify?
Hitch