[Fontconfig-bugs] [Bug 80873] Improve size unparse?

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=80873

--- Comment #15 from Akira TAGOH <akira at tagoh.org> ---
(In reply to Behdad Esfahbod from comment #14)
> 9 is really small.  See:
> 
>   v = v * 1000 + j;
> 
> so if there's any difference, that would be at least 1000.  I don't think
> that's a problem.

Not exactly. when the value exactly matches to the pattern, v will be 0. so it
won't be more than 1000. that is how fontconfig figures out the best font and
to make difference with exact-match and fallback on scoring right.

> > 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?
> 
> Do you have a clear example of that?

maybe not at this moment. assuming we are about to have some state in the cache
that is keeping the available properties only there, just guessed it might be a
problem then. it may depends on how the default behavior is. for example, that
is "color". we always have that property in the cache at this moment though, if
we add it only when color is true, querying a font with :color=true won't work
as expected so that the score becomes higher when it doesn't have.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20150521/e0cfcdff/attachment.html>