<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c14">Comment # 14</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 <span class="vcard"><a class="email" href="mailto:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> <span class="fn">Akira TAGOH</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=75178#c12">comment #12</a>)
<span class="quote">> 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.</span >
Oh yes, that's true. that said there are nothing we can do in fontconfig - we
did that already. poppler just needs to match it on FC_POSTSCRIPT_NAME rather
than FC_FAMILY_NAME.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>