The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: groff@gnu.org
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Documenting a set of functions with -man
Date: Tue, 25 Jun 2024 11:13:36 -0500	[thread overview]
Message-ID: <20240625161336.loxy43ra3n67gbg6@illithid> (raw)
In-Reply-To: <CAKH6PiVHkOfua8TSgn0Fj1f-JszPZud61o00xdzTChJwH6frcQ@mail.gmail.com>

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

[looping the groff list back in; Doug's reply went to TUHS]

At 2024-06-25T08:51:39-0400, Douglas McIlroy wrote:
> > The lack of a monospaced font is, I suspect, due either to
> > physical limitations of the C/A/T phototypesetter[1] or fiscal
> > limitations--no budget in that department to buy photographic
> > plates for Courier.
> 
> Since the C/A/T held only four fonts, there was no room for
> Courier.

The TUHS list is a good place to solicit recollections about the CAT-4
and CAT-8 models.  I surmise (mostly based on some Henry Spencer
"cat2dit" code that I cannot now lay my hands on) that the model numbers
indicated the number of mounting positions in the font plate carousel.

Does anyone have any recollections of dealing with the CAT-8?

I had assumed that Kernighan & Ritchie got their hands on a CAT-8 during
the course of preparing _The C Programming Language_ (1978), since it
exhibited use of Courier (upright, normal weight only) alongside Times:
roman and italic, and, for headings, bold.

Looking over the pages of the book now, though, it occurs to me that
K&R might have managed to set it with a CAT-4 by eschewing the special
font S, using Courier roman in its place.  A glance over a few dozen
pages does not reveal to me any of the unique symbols from the special
font, not even ASCII characters that GSI's Times roman lacked.[1][2]
Everywhere a double-quote ", backslash \, or underscore _ is required,
it's monospaced.[3]

...but wait.  On page 210 I see a times sign.  ("If E is an
n-dimensional array of rank i×j× ··· ×k, then E appearing in an
expression is coverted to a pointer to an (n−1)-dimensional array with
rank j× ··· ×k.")  Moreover, the capital "E" is in Courier roman.  The
section sign § also appears on the same page.

So maybe they had access to a CAT-8 after all, and used a whopping 5
different font plates.  Or they used a CAT-4 and had to compose many
pages in two passes.  That would have been mightily tedious.

> But when we moved beyond that typesetter, inertia kept the old ways.
> Finally, in v9, I introduced the fixed-width "literal font", L, in
> -man and said goodbye to boldface in synopses. By then, though,
> Research Unix  was merely a local branch of the Unix evolutionary
> tree, so the literal-font gene never spread.

Regards,
Branden

[1] The groff_char(7) man page in groff 1.23.0 lists the glyph
    repertoires of the GSI fonts for the convenience of those who don't
    have a scan of CSTR #54 (1976) handy.  The Bell System logo is
    missing, though.

[2] Some interesting symbols appear on page 18.  But as noted in the
    text, these can be constructed via overstriking.  :)

[3] The "double-quotes" appearing in Times in the book are obviously
    repetitions of the single typesetter's quotes that the GSI Times
    roman font had; you can see that they are not closely kerned.  One
    can infer ``this input''.

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

  reply	other threads:[~2024-06-25 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 12:51 Douglas McIlroy
2024-06-25 16:13 ` G. Branden Robinson [this message]
2024-06-25 19:15   ` Mychaela Falconia
2024-06-25 19:27     ` G. Branden Robinson
2024-06-28 10:07     ` arnold
2024-06-28 19:38       ` G. Branden Robinson

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=20240625161336.loxy43ra3n67gbg6@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=groff@gnu.org \
    --cc=tuhs@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).