<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - webfonts support?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63096#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - webfonts support?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=63096">bug 63096</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=63096#c1">comment #1</a>)
<span class="quote">> Humm. Not sure about that.
>
> The matcher should not fail if something is missing. It should simply not
> match.</span >
Well, it actually doesn't match. but the problem is, it affects a score
differently. if something is missing, the score of that object is 1e99. but if
it's there but just not matching, the score of that object is 1000 + n. given
that first matched object is lower than that, it won't be selected as the best
font due to that "1e99" score.
If a warning is annoying, when the built-in objects are missing, we should take
care of it as "not matching" which gives 1000 + n score.</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>