Hi Branden, On Mon, Mar 25, 2024 at 12:40:07PM +0100, Alejandro Colomar wrote: > > The grops(1) and gropdf(1) man pages in groff 1.23.0 discuss using this > > tool to prepare fonts so that groff can read them. > > Hmmm, so I could add a Makefile target to produce this .pfa font from > the packaged .pfb one, and then get gropdf(1) to use this one. --Using > a Makefile pays for itself.-- The process is fast, it seems. > > $ time pfbtops \ > /usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos.pfb \ > | wc -l > 19570 > > real 0m0.012s > user 0m0.015s > sys 0m0.001s > > I'll try it. This should remove a gigantic file from the project > repository. Thanks! =) I'm a bit worried that with the font regenerated from the packaged one and pfbtops(1) I get a lot more warnings. The PDF still seems okay at first glance, but I'm not sure if there's something wrong with what I'm doing: $ pfbtops \ /usr/share/texlive/texmf-dist/fonts/type1/google/tinos/Tinos.pfb \ >scripts/LinuxManBook/devpdf/Tinos.pfa ; $ make build-man -j24 >/dev/null; $ make build-pdf-book |& wc -l; 1349 $ git stash; Saved working directory and index state WIP on contrib: 49e6388bb share/mk/: srcfix $ rm .tmp/man-pages-*.pdf; $ make build-pdf-book |& wc -l; 260 Maybe I also need to regenerate the TINOR file? And how do I regenerate that one, and what's its source? Cheers, Alex -- <https://www.alejandro-colomar.es/> Looking for a remote C programming job at the moment.
Attachment:
signature.asc
Description: PGP signature
