Follow-up Comment #5, bug #65974 (group groff): Hi Morten,
Is this still a live problem?
At 2024-07-11T15:23:15-0400, Morten Bo Johansen wrote:
> Follow-up Comment #4, bug #65974 (group groff):
>
> Okay. The groff configure script did not find the fonts on my Arch
> Linux system, even though I have the ghostscript package installed.
>
> Therefore I installed these urw-base35 fonts manually and as always
> when I install something outside of the package system, I prefer to do
> it in my home directory. The solution with the groff.m4 file at least
> worked for me, even if it may not be the correct solution.
>
> Now, I noticed that the type 1 fonts actually are included in the Arch
> ghostscript package, but they lack the *.t1 extension which I suppose
> is the reason that the groff configure script doesn't see them.
What file names does the Arch ghostscript package use?
Our configure check does the following:
for k in $_list_paths
do
for _font_file in \
URWGothic-Book \
URWGothic-Book.t1 \
URWGothic-Book.pfb \
URWGothicL-Book.pfb \
a010013l.pfb
do
if test -f $k/$_font_file
then
AC_MSG_RESULT([found in $k])
groff_have_urw_fonts=yes
urwfontsdir=$k
break 2
fi
done
done
What naming convention does Arch ghostscript use, if not one of the
foregoing?
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65974>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
