<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - font "Wingdings" is displayed incorrectly and the bug in fontconfig crashes xfd" href="https://bugs.freedesktop.org/show_bug.cgi?id=58641#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - font "Wingdings" is displayed incorrectly and the bug in fontconfig crashes xfd" href="https://bugs.freedesktop.org/show_bug.cgi?id=58641">bug 58641</a> from <a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> Behdad Esfahbod</a> <pre>The change indeed was a result of removing the Apple Roman encoding. However, I don't think it's incorrect. The font has two cmap tables: 1. Apple Roman. This one incorrectly maps Latin characters to the wingding symbols. 2. MS Symbol. This one maps private-use-area characters to the symbol. Now, for some reason we are NOT reading the second table, so previously we were relying on the first one, which we don't read anymore. The problem is, symbol fonts have no defined encoding. One would never know what the glyph at position one really is. So I think it's correct for fontconfig to NOT enumerate those glyphs.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>