Re: proposed "headline" items for groff 1.24.0

Deri via GNU roff typesetting system discussion <[email protected]>
Newsgroups gmane.comp.printing.groff.general
Message-ID <12107315.uu3HMy921B@pip>
On Thursday, 29 January 2026 20:40:52 GMT G. Branden Robinson wrote:
> At 2026-01-28T22:15:21-0500, Peter Schaffter wrote:
> > 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

With groff in intermediate mode (urw no, gs yes) all the 256 glyph default 
foundry fonts are available and can also be embedded. So you can use N & P.

In basic mode (urw no, gs no) if you want typesetting.mom built stick to H, T, 
C families. Of course  you could do something like:-

.ie F NR .FAM N
.el .FAM H

Which would work in all pdf modes and ps would always use N (because NR is 
always available).

Cheers

Deri
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.