© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
(In reply to comment #1)
> Humm. Not sure about that.
>
> The matcher should not fail if something is missing. It should simply not
> match.
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.