<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Improve size unparse?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80873#c13">Comment # 13</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Improve size unparse?"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80873">bug 80873</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=80873#c12">comment #12</a>)
<span class="quote">> I think this might be ready. Akira, can you please review?
>
> Thanks.</span >
Well, "it matches any value perfectly" approach ignores the score when it
exactly matches the value perfectly, doesn't it?
j is increased per matchers. speaking of FC_SIZE, j will be 9 at this moment.
given that one tries to query with :size=12 say, and a cache doesn't contain
FC_SIZE, the score will be 0 right. but if it has, the score will be 9. in this
case that works because an outlined font can takes care of it. how about the
sort of flags? I tend to agree with not having the unnecessary values in the
cache though, do we need to pay more attentions in FcDefaultSubstitute() to
prevent such situation or improve the score estimation to make better even
without it?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>