This produces weird results in Windows' Character Map. Some characters show only the 'undefined' symbol, while others seem to display glyphs borrowed from somewhere else (presumably some sort of emulation feature). Looking within the font in FontCreator, so far I cannot figure out why this is happening.
Worse that the above odd behaviour, this flawed font structure is apparently also preventing embedding of the fonts (or subsets thereof) into PDF files — even if none of those questionable characters are used in the font.
I have described this at length from the PDF-creation perspective on the Tracker Software forum for PDF-XChange Editor; the staff there are pretty good when it comes to general PDF issues, but it doesn't look as though I'm going to get a lot of insight there on the fundamental font issues.
I'd be interested to know the following.
- Do others also experience the same strange/defective behaviour with the OTF files for this font family?
- Where is the setting (or settings) that have caused all of these code-points to be defined?
- How can I remove the code-points that don't have any associated glyphs? (I tried loading the fonts into FontCreator and exporting them to new file names, still as OTF with cubic CFF (PostScript) outlines, but the glyphless code-points remained. The problems of glyphless characters and PDF-unembedability went away when I exported the fonts to new files as OTF with quadratic TTF outlines, but the resulting fonts didn't look/behave quite the same as the original fonts.)
Thanks,
DIV