<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - font substitution fails if font name contains a dash" href="https://bugs.freedesktop.org/show_bug.cgi?id=75178#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - font substitution fails if font name contains a dash" href="https://bugs.freedesktop.org/show_bug.cgi?id=75178">bug 75178</a> from <a class="email" href="mailto:freedesktop@behdad.org" title="Behdad Esfahbod <freedesktop@behdad.org>"> Behdad Esfahbod</a> <pre>(In reply to <a href="show_bug.cgi?id=75178#c5">comment #5</a>) > (In reply to <a href="show_bug.cgi?id=75178#c3">comment #3</a>) > > That fc-match Code-128 doesn't work is expected, you need to escape the dash > > in there. It wouldn't happen with the API though, so that can't explain the > > issue you are seeing. > > I found that it works only by using escaping PLUS double quotes around the > match string. Unfortunaltely only escaping does _NOT_ work. This is not > mentioned in the man page, would it be an idea add that? You sure?! behdad:~ 0$ fc-match 'Code-128' DejaVuSans.ttf: "DejaVu Sans" "Book" behdad:~ 0$ fc-match 'Code\-128' Code-128.ttf: "Code-128" "Normal" behdad:~ 0$ fc-match '"Code-128"' DejaVuSans.ttf: "DejaVu Sans" "Book" Oh, you mean this doesn't work: $ fc-match Code\-128 DejaVuSans.ttf: "DejaVu Sans" "Book" That has nothing to do with fontconfig. Bash / your shell will consume that escaping. You want the backslash to reach fontconfig.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>