Quote:
Originally Posted by grannyGrumpy
I saw a post here on the forum about using HTML entities to help prevent the question mark/blank box that happens when a font can't support a special character.
|
That won't work. HTML entities only aid in the writing of the actual code (since keyboards generally don't have a key for emdashes or typographical quotes), they won't alter the requirement that the font needs the correct glyphs to show them.
What you're seeing is normal behaviour.
You'll only run into problems with missing characters if your book contains fancy wingdings or uses characters that fall outside the narrow set used in Western European languages.
ADE- (or RMSDK-) based readers support a default character set that's defined in tables D1 and D3 given in
this document. Apple's iBooks supports a much wider character set, though it's not properly documented in any open location.
Obviously, you can avoid this problem by embedding a font which supports the characters you need if this is an issue.
[Edit]: I see Adobe has updated its docs to reflect PDF's status as an ISO standard. The character set supported by basic ADE implementations can now be found in tables D2 and D5 of
this document.