Re: proposed "headline" items for groff 1.24.0

"G. Branden Robinson" <[email protected]> Thu, 29 Jan 2026 14:40:52 -0600

Newsgroups	gmane.comp.printing.groff.general
Message-ID	<20260129204052.xrd663tbqng67ghi@illithid>

At 2026-01-28T22:15:21-0500, Peter Schaffter wrote:
> On Wed, Jan 28, 2026, G. Branden Robinson wrote:
> > Generation of "typesetting.pdf" from "typesetting.mom" fails hard if
> > the "U" foundry is not available.  The document composes its pages
> > carefully, and uses the New Century Schoolbook and Palatino
> > families, which are not in the Base 14, so I judged that it's better
> > to not produce a PDF at all than to render the wrong font.  I
> > welcome feedback from Peter if he was unaware that this was a
> > failure scenario and would like to take some alternative approach.
> 
> I didn't know.  I thought we'd resolved family issues when we switched
> N and P for U-N and U-P ages ago.  At the time, I proposed simply
> editing the document to use families that didn't cause trouble.  I
> can't recall why, but I was discouraged from pursuing that path.  I
> propose it again if it simplifies things.

If I understand this Base 14 vs. Base 35 stuff correctly, it _wouldn't_
help, or not much.  Families N and P aren't in the Base 14 set, so
they'd need to be embedded in PDF anyway, and if their font files
weren't found, such embedding is not going to happen.

Maybe Deri can shed some light on why the foundry was made explicit.  A
quick glance over "typesetting.pdf" suggests to me that you're _not_
using exotic glyphs.  What you do use--I assume--is satisfied by the
256 glyphs of Adobe's N and P families.

Regards,
Branden

signature.asc (application/pgp-signature, 833 B)