Fedora Account System
Red Hat Associate
Red Hat Customer
The ghostscript-9.20-13 package does not reference /usr/share/fonts/urw-base35 in the output of 'gs -h'. So, how are programs that need access to the .afm files supposed to locate them without having been specifically developed with awareness of the urw-base35-fonts paths? Also, in Ghostscript 8.64 there was a utility called "genfontmap.ps" which we have been using to generate a fontmap dump from Ghostscript. This works as expected with ghostscript-9.20-13, but in the map it creates there are now a lot more listed fonts which are not present on the system. There were some missing fonts before, but now there are even more.
Hello Lee, sorry for late response, I was on a vacation yesterday... Anyway, thanks for spotting that out. Looking at the ghostscript source code, it should be easily fix by adding '--with-fontpath <path>' to %configure in specfile. I will create a new version of the package today.
Okay, so fixing this I have just noticed that this is just a cosmetic problem. The ghostscript still works okay, even though the 'gs -h' does not show the exact 'search path' for 'urw-base35-fonts'... And that's because of this: > Search path: > /usr/share/fonts/default/cmpsfont/pfb : /usr/share/fonts : The /usr/share/fonts contains the /usr/share/fonts/urw-base35, and I suspect that Ghostscript just does a recursive search for all the search paths. Anyway, I'm preparing the new build now. :)
ghostscript-9.20-14.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b765f9d358
ghostscript-9.20-14.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b765f9d358
ghostscript-9.20-14.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.