From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Mychaela Falconia <falcon@freecalypso.org>
Cc: tuhs@tuhs.org, groff@gnu.org
Subject: [TUHS] Re: Documenting a set of functions with -man
Date: Tue, 25 Jun 2024 14:27:58 -0500 [thread overview]
Message-ID: <20240625192758.aokbtpkgsgpkczy2@illithid> (raw)
In-Reply-To: <20240625191539.D35A33740343@freecalypso.org>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
Hi Mychaela,
At 2024-06-25T11:15:32-0800, Mychaela Falconia wrote:
> G. Branden Robinson <g.branden.robinson@gmail.com> wrote:
> > 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.
>
> Are you certain that the bold in that book is real B font and not .bd
> construct? I am not sure about the full K&R book, but the C Reference
> Manual doc in vol 2 seems to have been troff'ed with .bd for bold
> (while keepting R, I, S and adding CW), ditto for the UNIX Programming
> doc in the same volume that similarly uses CW for program listings.
I definitely am not certain, and I am mindful of the possibility that
that the C Language Reference part of the book was typeset at a
different stage of production than the rest of the volume.
C was still in relative ferment at that time, as we can tell from
<https://www.bell-labs.com/usr/dmr/www/cchanges.pdf>, a document that
was included in some printings of Volume 2 of the Seventh Edition Unix
manual.
Thanks for pointing out this alternative explanation.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-06-25 19:28 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
2024-06-25 19:15 ` Mychaela Falconia
2024-06-25 19:27 ` G. Branden Robinson [this message]
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=20240625192758.aokbtpkgsgpkczy2@illithid \
--to=g.branden.robinson@gmail.com \
--cc=falcon@freecalypso.org \
--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).