I understand, as I mentioned in the original bug report, the script patch is a
kludge.
Carlo
On August 15, 2019 12:12:36 PM CDT, Nicholas Breen wrote:
>On Tue, Aug 13, 2019 at 12:47:07AM -0500, Carlo Segre wrote:
>> If the links ending in *.t1 in the /usr/share/grace/fonts/type1/
>directory
>>
On Tue, Aug 13, 2019 at 12:47:07AM -0500, Carlo Segre wrote:
> If the links ending in *.t1 in the /usr/share/grace/fonts/type1/ directory
> are renamed as *.pfb, then grace identifies all the fonts correctly and
> makes them all available with their proper name designations. This
> indicates that
Package: grace
Version: 1:5.1.25-6
Followup-For: Bug #934662
I can confirm that the fonts in grace have been badly broken for a
month or more now, with the error message "Failed mapping a font"
emitted.
I confirm also that Carlo's patch fixes the problem, restoring fonts
to the expected
I have attached a patch to the /usr/sbin/update-grace-fonts script which
will provide the kludgy solution described in my original submission.
It is also inserted below
Carlo
--- /usr/sbin/update-grace-fonts~ 2018-04-28 12:50:28.0 -0500
+++ /usr/sbin/update-grace-fonts
Package: grace
Version: 1:5.1.25-6
Severity: important
Dear Maintainer,
When the latest ghostscript (9.27~dfsg-3) is installed, it forces the
installation of the fonts-urw-base35 package which contains binary font
files ending in a *.t1 instead of *.pfa or *.pfb. The grace package updates
its
5 matches
Mail list logo
