Quote:
Originally Posted by Hitch
dg:
We, you and I, are discussing this very situation--your font characters are outside of the available character slots--in another thread. On any device that can't show an embedded font, you're going to have that problem. Even if you could FTP the files, you'll have the same issue.
|
No, they aren't. That's what is so bizarre. The book's HTML was 100% low ASCII, with all special characters entity-encoded. If all the text fell outside the standard range of characters supported by normal fonts, the books would fail on the Kindle DX, which doesn't support embedded fonts. It works fine on the DX. It only failed on devices that support embedded fonts, and only on certain versions of Kindle Previewer.
What's fascinating is that both problems—the online reader showing square boxes and Kindle for Mac using the default fonts when opening the downloadable preview—went away completely when I removed the
Code:
text-rendering: geometricPrecision;
line from the stylesheet.
So apparently, there are many different triggers that can cause KDP to do something really bizarre, and at least one of those triggers causes KDP to somehow corrupt the MOBI output in such a way that some readers believe that the font files are there, but cannot parse them, resulting in a failure to correctly load the font, but still resulting in an attempt to use the font, thus the square boxes (caused by trying to display a font that contains no glyphs).
It's really quite bizarre, and may or may not be in any way related to the bugs you saw.