<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - poppler doesn't render any glyphs from a wrong embedded font" href="https://bugs.freedesktop.org/show_bug.cgi?id=84270#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - poppler doesn't render any glyphs from a wrong embedded font" href="https://bugs.freedesktop.org/show_bug.cgi?id=84270">bug 84270</a> from <a class="email" href="mailto:Thomas.Freitag@alfa.de" title="Thomas Freitag <Thomas.Freitag@alfa.de>"> Thomas Freitag</a> <pre>The truetype font SFBMTB+Frutiger-Bold has a POST entry in format 2. (This contains the data needed for the FontInfo dictionary entry as well as the PostScript names for all of the glyphs in the font) The spec for this entry says: If you do not want to associate a PostScript name with a particular glyph, use index number 0 which points to the name .notdef. But the software which embeds this font makes it in another way: All not associated glyphs points to the end(!!) of the Postscript name table (entry for this glyphs: 270). That's why poppler invalidates this font and therefore don't render any glyphs of it, and it does so without giving any error message. But since ghostscript and acrobat reader show the glyph of this font I think poppler should do it either.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>