[Fontconfig-bugs] [Bug 75178] font substitution fails if font name contains a dash
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Feb 19 13:40:16 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=75178
--- Comment #9 from Behdad Esfahbod <freedesktop at behdad.org> ---
(In reply to comment #5)
> (In reply to comment #3)
> > 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.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20140219/dfc71a1a/attachment.html>
More information about the Fontconfig-bugs
mailing list