Re: [BUG] man(7) page not showing footer

[G. Branden Robinson]

Hi Alex,

At 2022-11-08T13:12:17+0100, Alejandro Colomar wrote:
> I'm having issues compiling groff:
[...]
>   GROFF    doc/groff-man-pages.pdf
> /home/alx/src/gnu/groff/gropdf:src/utils/addftinfo/addftinfo.1: fatal error: 
> unable to open font 
> '/usr/share/ghostscript/9.56.1/Resource/Font/NimbusRoman-Italic' for embedding

At last this revised diagnostic message is paying dividends.

> I don't see the dependency being documented in the INSTALL.REPO file.

It's discussed in INSTALL.extra, which INSTALL.REPO recommends reading.
:)

>>>
Dependencies
------------

The dependencies documented in the 'INSTALL.extra' file are required, as
are several others.
<<<

But this issue is troublesome; Deri James and I are trying to get it
sorted out because I fear a lot of problem reports about this for RC2 if
we don't.

Here's what INSTALL.extra says about this topic.  It is admittedly a lot
to swallow.  (This is my working copy, but it differs from Git HEAD
only in formatting.)

>>>
URW fonts
---------

The 'configure' script searches for PostScript Type 1 fonts originating
with the URW foundry; these are metrically-compatible replacements for
the Adobe PostScript Level 2 base 35 fonts required by that standard.
These URW fonts are packaged with Ghostscript and in various derivative
versions.  The Adobe fonts are not free software, but the replacements,
named "Nimbus Roman", "Nimbus Sans", and "Nimbus Mono", and so forth,
are.  The PostScript standard and early versions of the PDF standard
assumed that these base fonts will be supplied by the rendering device
(a printer or PDF viewer).  Nowadays the PDF standard expects all fonts
to be embedded in the document; if groff's gropdf(1) output driver knows
where to find these fonts, you can use its "-e" option for this purpose.

The build process populates "Foundry" and "download" files that tell
gropdf where to find their groff font descriptions and the font files
themselves, respectively.  If you have multiple versions of the URW
fonts available on your system, or the 'configure' script cannot locate
them on its own, use its "--with-urw-fonts-dir" option to tell the
script where to find them.  If you never use groff to generate
PostScript or PDF documents, you can ignore any output from the
'configure' script about URW fonts.
<<<

Please share with us the configuration banner of your build.

It's the part that looks roughly like this.

GNU Troff version 1.23.0.rc1.3365-2653e-dirty
----------------------------------------------------------------------
 installation directory prefix    : /usr/local
 C++ compiler and options         : g++ -Wall -Wextra
 use libgroff's memory allocator  : no
 C compiler and options           : gcc -Wall -Wextra
 Perl interpreter version         : 5.32.1
 X11 support                      : enabled
 X11 app defaults directory       : /usr/local/lib/X11/app-defaults
 'groff -l' uses print spooler    : lpr
 use URW fonts for PDF output     : yes
 URW fonts directory              : /usr/share/fonts/type1/gsfonts/
 preconv can use uchardet library : yes
 can build groff.dvi, groff.pdf   : yes
 tests can use poppler PDF tools  : yes
----------------------------------------------------------------------

You might also look over https://savannah.gnu.org/bugs/?62860 and
consider reopening it.

Deri, do you have the changes you mentioned in
https://savannah.gnu.org/bugs/?62950#comment5 ready to push?

Regards,
Branden

signature.asc
Description: PGP signature