The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: tuhs@minnie.tuhs.org, groff@gnu.org
Subject: Re: [TUHS] [TUHS/groff] Provenance of .SB macro in man pages
Date: Sun, 26 Jan 2020 06:36:58 +1100	[thread overview]
Message-ID: <20200125193655.g6mwesmitjkxjebf@localhost.localdomain> (raw)
In-Reply-To: <alpine.NEB.2.21.2001251254310.50@t1.m.reedmedia.net>

[-- Attachment #1: Type: text/plain, Size: 2168 bytes --]

Thanks for the quick follow-up, Reed!

At 2020-01-25T13:13:44-0600, reed@reedmedia.net wrote:
> On Sun, 26 Jan 2020, G. Branden Robinson wrote:
> 
> > I'm inlining my findings in rendered and source form below, but
> > there's one feature I haven't been able to sort out--where did .SB
> > (small bold) come from?  The oldest groff release I can find online
> > is 1.02 (June 1991), and .SB is already there, but I can't find it
> > anywhere else.  Is it a GNUism?  Did it perhaps appear in a
> > proprietary Unix first?
> 
> I see .SB used in the 
> C Manual - Language
> Edited by R.P.A. Collinson
> Document No: DOC/UNIX.K3.10/1
> and UKC IO Library docs also from Collinson at Univ. of Kent.
> as found in the usenix-78-uk1 tape.
> Maybe that is uk1.tar at 
> https://www.tuhs.org/Archive/Applications/Spencer_Tapes/

There's definitely an .SB macro used in that and a few other *roff
documents in the uk1 archive, all of which have filenames ending in
".n".

They're not laid out like man pages, there's no tmac.n file in the
archive, and the macros used don't seem to come from Matt Bishop's News
macro package, also named tmac.n.

Given the absence of the macro package source it's hard to say what the
semantics of these documents' ".SB" might be.  They appear to be used as
section headings, but C function prototypes are used with them as well.
But since a C library is being documented alongside the language, maybe
that's not too surprising.

> I also see a SB Stymie Bold font in v7 troff.

That's a different namespace.  Something it took me an embarrassingly
long to figure out was the ridiculously terse naming convention of *roff
font description files.

The "foundry" name gets the first letter, and after that you get "R" for
roman, "B" for bold, "I" for italic, "BI" for bold italic, and "S" for a
"special" font (symbols for math typesetting or dingbats).  Bold and
italics didn't apply to special fonts.

So, if your system has Helvetica you'll have files called:
	HR
	HB
	HI
	HBI

If my guess is right, alongside Stymie Bold you'll see SR, SI, and
possibly SBI as well.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2020-01-25 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 15:00 G. Branden Robinson
2020-01-25 19:13 ` reed
2020-01-25 19:36   ` G. Branden Robinson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200125193655.g6mwesmitjkxjebf@localhost.localdomain \
    --to=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).