Hi Morten, At 2026-02-10T19:15:58+0100, Morten Bo Johansen wrote: > Thanks for taking a look at it.
My pleasure! > On 2026-02-10 G. Branden Robinson wrote: > > Yes. "INSTALL" is a generic file that gnulib provides as an overview of > > the GNU build system. "INSTALL.extra" is the groff-specific supplement, > > and it documents the matter of URW fonts. > > > https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/INSTALL.extra?h=1.24.0.rc3#n142 [snip] > All right, so it seems there isn't a suitable place for it as of now. No, there is, and I linked to it--see above. I'll quote from the cited line number forward. ---snip--- 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, often named "Nimbus Roman", "Nimbus Sans", and "Nimbus Mono", and so forth, are. The PostScript and early PDF standards assumed that these base fonts would 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. ---end snip--- I see that I should mention the new "--without-urw-fonts" configuration option in "INSTALL.extra", so I'll do that. > But maybe there ought to be a file for something like this, not only > for Arch but for whatever quirks there might be with other distros as > well. The "MANIFEST" file in the top-level directory of the groff repository and distribution archive attempts to explain the purpose of the files and directories within the distribution archive. ("Repo-only" files that are not "distributed" are not described.) https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/MANIFEST?h=1.24.0.rc3 > > Please double-check this. I'm happy to add yet another directory to > > the search path (and, as noted in the foregoing file, update > > "Foundry.in" as well), but I want to be sure. > > $ pacman -Ql gsfonts-type1 > > gsfonts-type1 /usr/ > gsfonts-type1 /usr/share/ > gsfonts-type1 /usr/share/fonts/ > gsfonts-type1 /usr/share/fonts/Type1/ > gsfonts-type1 /usr/share/fonts/Type1/a010013l.afm > gsfonts-type1 /usr/share/fonts/Type1/a010013l.pfb > [...] Okay. I'm convinced. :) I'll update "groff.m4" and "Foundry.in" accordingly. Regards, Branden
signature.asc
Description: PGP signature
