Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3733 - xpdf missing font errors

Attached to Project: Arch Linux
Opened by Simon Morgan (sjmorgan) - Monday, 09 January 2006, 22:43 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 10 January 2006, 07:16 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'm not sure if this has already been considered so apologies if it has. The problem is that xpdf has no font dependencies so that if a package that provides fonts usable by xpdf (e.g. ghostscript) isn't installed you get the following errors when you run xpdf and, if the document doesn't have fonts embedded in it, no text.

Error: No display font for 'Courier'
Error: No display font for 'Courier-Bold'
Error: No display font for 'Courier-BoldOblique'
Error: No display font for 'Courier-Oblique'
Error: No display font for 'Helvetica'
Error: No display font for 'Helvetica-Bold'
Error: No display font for 'Helvetica-BoldOblique'
Error: No display font for 'Helvetica-Oblique'
Error: No display font for 'Symbol'
Error: No display font for 'Times-Bold'
Error: No display font for 'Times-BoldItalic'
Error: No display font for 'Times-Italic'
Error: No display font for 'Times-Roman'
Error: No display font for 'ZapfDingbats'
This task depends upon

Closed by  Tobias Kieslich (tobias)
Thursday, 26 January 2006, 00:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in testing, be changing the preferences hardcoded into source code
Comment by nackd (Prieto) - Tuesday, 10 January 2006, 13:31 GMT
xpdf should depend on gsfonts.

Besides, gsfonts has just moved the fonts from the "standard" location in /usr/share/ghostscript/fonts to /usr/share/fonts/Type1. For xpdf (and other programs based on it, such as kpdf) to find them, there are some alternatives:

1. Put the fonts back in /usr/share/ghostscript/fonts
2. Symbolic link from /usr/share/ghostscript/fonts to /usr/share/fonts/Type1
3. displayFontT1 options in /etc/xpdfrc

A document you may use to test is http://www.byteofpython.info/files/120/byteofpython_120.pdf
Comment by nackd (Prieto) - Tuesday, 10 January 2006, 13:35 GMT Comment by Tobias Kieslich (tobias) - Wednesday, 25 January 2006, 05:15 GMT
Isn't this actually a testing issue? Did you file it current accidentally?
Comment by Jan de Groot (JGC) - Wednesday, 25 January 2006, 07:58 GMT
This is an issue with the current xpdf package when not having an old version of ghostscript installed. AFAIK, ghostscript and ghostscript-fonts are already in current. The workaround in comment1 for displayFontT1 in /etc/xpdfrc is the same workaround used by Ubuntu and Debian. We have to change this for poppler 0.5.x when that becomes stable also.
Comment by Simon Morgan (sjmorgan) - Wednesday, 25 January 2006, 12:02 GMT
It still doesn't look like there are any ghostscript font packages in current, you still have to install the whole ghostscript package for xpdf to work.
Comment by Jan de Groot (JGC) - Wednesday, 25 January 2006, 12:23 GMT
Ah, the ghostscript 8.x package is still in testing. I thought I moved it to current a while ago, but seems I didn't.
Comment by Tobias Kieslich (tobias) - Wednesday, 25 January 2006, 17:23 GMT
the comment that, xpdf should depend on gsfonts is absolutely correct. The (old) path is hardcoded in one of the sourcefiles. I caan change that to whatever we want, which I tested and it seems the easiest solution to me. Jan, does gsfonts stay in /usr/share/fonts/Type1?

Loading...