<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - font substitution fails if font name contains a dash" href="https://bugs.freedesktop.org/show_bug.cgi?id=75178#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - font substitution fails if font name contains a dash" href="https://bugs.freedesktop.org/show_bug.cgi?id=75178">bug 75178</a> from <a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> Behdad Esfahbod</a> <pre>(In reply to <a href="show_bug.cgi?id=75178#c10">comment #10</a>) > Well, this is a poppler issue. see: > <a href="http://cgit.freedesktop.org/poppler/poppler/tree/poppler/GlobalParams">http://cgit.freedesktop.org/poppler/poppler/tree/poppler/GlobalParams</a>. > cc#n1021 > > they are replacing a dash in a font name and fontconfig takes care of the > dash and the space in the name differently. > This change has been made based on older version of fontconfig: > > commit 82638babe89e402c0348619ec3205059b977c7e9 > Author: Albert Astals Cid <<a href="mailto:aacid@kde.org">aacid@kde.org</a>> > Date: Thu Jul 28 17:34:19 2005 +0000 > > Fontconfig patch is here, rejoice > > So I'm not surprised something went wrong. it may be the time to get rid of > this hack. reassigning to poppler. Wait. I *think* Poppler is chopping a PS font name and passing to fontconfig. So, if the real font name has space, Poppler has to convert dash to space, but if the real font name actually has dash, the conversion is bogus. Back to a known issue: we need matching by PS font name. That, or make fontconfig ignore dash in family name matching as it does for space. Or, make poppler remove the dash instead of replacing it with space.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>