[Fontconfig-bugs] [Bug 75178] New: font substitution fails if font name contains a dash

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 18 14:38:47 PST 2014


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

          Priority: medium
            Bug ID: 75178
          Assignee: fontconfig-bugs at lists.freedesktop.org
           Summary: font substitution fails if font name contains a dash
        QA Contact: freedesktop at behdad.org
          Severity: blocker
    Classification: Unclassified
                OS: Linux (All)
          Reporter: joachim.schwender at web.de
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: library
           Product: fontconfig

Created attachment 94316
  --> https://bugs.freedesktop.org/attachment.cgi?id=94316&action=edit
Example PDF wit such a font that is not embedded and gets not substituted
properly

I have PDF that contain a font named Code-128, not embedded. Just installing
this font does not help: it is not picked properly and evince uses DejaVu for
rendering, which is bad for a barcode font!
A fc-list does show the installed font. A fc-match does not work and always
returns "DejaVu Sans" "Book"

Expected: fontconfig picks the installed font and uses it for rendering in
evince. fc-match returns the font name it it matches, no matter what character
is contained in the name.

Tested on Ubuntu 12.04 and 13.10 (x86_64) with fonconfig 2.10.93

Temprary workaround i currently use:
I used fontforge to change the font by removing the dash in the font name. Then
i implemented a substitution for Code-128 to be substituted by Code128.

Result: evince displayed the font properly but fc-match still does not work.

Unfortunately i have no influence on the PDF generation, they are generated by
a German Ministry of Interior and i have been struggling for three years now to
get them to create only PDF-A (fonts embedded), but they refuse to implement
that without giving meaningful arguments. We, like many other companies are
forced(!) to utilize these buggy PDFs, probably most companies use
Windows+AdobeReader and don't have that problem...

-- 
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/20140218/862aae35/attachment.html>


More information about the Fontconfig-bugs mailing list