<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - Extend metric-aliases.conf" href="https://bugs.freedesktop.org/show_bug.cgi?id=60783#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - Extend metric-aliases.conf" href="https://bugs.freedesktop.org/show_bug.cgi?id=60783">bug 60783</a> from <a class="email" href="mailto:pgajdos@novell.com" title="Petr Gajdos <pgajdos@novell.com>"> Petr Gajdos</a> <pre>(In reply to <a href="show_bug.cgi?id=60783#c9">comment #9</a>) > difference between <accept> and <default> is a priority where specified font > appears in the pattern. behavior depends on other recipes and what fonts are > installed on system though, given that one doesn't have Liberation Sans but > Arrial, fontconfig may picks up Arrial in <accept> but not necessarily in > <default>. particularly other fonts are set to the pattern by other recipes. Because we are talking about 30-*.conf file, most likely first conf file read by fontconfig which deals with <alias>es, there very probably isn't nothing behind 'Liberation Sans Narrow' in the family list if the requested pattern itself doesn't contain more families, so <default> and <accept> should do identical work, correct? So yes, we can use <default> but I do not see the reason right now why not do it consistently for both rules in question.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>