Public bug reported:
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.
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 12.04 and 13.10 (x86_64)
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...
** Affects: fontconfig (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275136
Title:
font substitution fails if font name contains a dash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1275136/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
