After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 746629 - dvi backend does not load type 1 fonts as it should
dvi backend does not load type 1 fonts as it should
Status: RESOLVED OBSOLETE
Product: evince
Classification: Core
Component: backends
3.15.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-03-23 06:00 UTC by axel.struebing
Modified: 2018-05-22 16:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fix for is_encoding (500 bytes, patch)
2015-03-23 06:00 UTC, axel.struebing
none Details | Review

Description axel.struebing 2015-03-23 06:00:48 UTC
Created attachment 300111 [details] [review]
fix for is_encoding

opening a simple file (cwebman.dvi) from my texlive tree shows that mdvi-lib loads/generates pk-fonts for showing glyphs.
Configuring evince and texlive for postscript font rendering works with this file, but not for others.
I traced the problem down into backend/dvi/mdvi-lib/fontmap.c not parsing my psfonts.map correctly.

The wrong cases look like
AGaramondPro-Bold-lf-t1--base AGaramondPro-Bold " AutoEnc_r4qhref7d7ussrbmo4nkqwsxhd ReEncodeFont " <[a_r4qhre.enc <AGaramondPro-Bold.pfb

where the encoding part is overwritten by the pfb filename.

I attach a simple patch that corrected the problem for me.
Comment 1 GNOME Infrastructure Team 2018-05-22 16:11:34 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/582.