<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#c13">Comment # 13</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:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>Thanks for investigation. (In reply to <a href="show_bug.cgi?id=58641#c12">comment #12</a>) > 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. I think there are similar issue about encoding on some BDF fonts which fontconfig can't deal with. so just wonder if fontconfig provides any way to embed the encoding information into the configuration as the meta data? As you have implemented the bitmap scaling, such fonts is still somewhat usable?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>