The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix tools to aid in the production of Internet RFCs?
Date: Wed, 26 Aug 2020 18:02:08 -0400	[thread overview]
Message-ID: <CAC20D2N6o7YYFZQwbwdb9gdhXs_oWOtNr=MszFeiMp2UUvXm-g@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W7jn06yFP4SPaZ3bxZGWkMc8zgRFRWdLM91yZ1Kgq9V4g@mail.gmail.com>

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

On Wed, Aug 26, 2020 at 5:25 PM Dan Cross <crossd@gmail.com> wrote:

> So I'm curious: what tools did people use to produce those documents?
>
What was available at the time?  Some of the first were done with a
typewriter ;-).   That said, a lot of the early ones (1960-thru late 70s)
were done using one of the different flavors of the runoff schemes, with
the PDP-10 family being pretty popular since many of the Arpa supplied
systems were based on PDP6/10s. The output, as you see, was formatted ASCII
printer listings. Once Unix hit the scene, particularly with Vaxen, nroff
took the lead, but since other than CMU/Stanford/MIT, XGPs (or later
Dovers) were rare.  Using a plotter (*a.k.a. *vcat and family) troff starts
to take off it some places beyond folks with an XGP (like UCB).   By the
time of the many different JAWS, and the Apple Laserwriter and eventually
different HP printers, the nroff/troff family was very much the norm, with
some Tex/LaTex at some point.  MS-Word does not start to show up until
about 15-20 years into the process.

As you noted, Bakul has a pointer to the current set of tools; but you
asked in the past tense; so I'm assuming you mean, how did the first 1-2K
or so get created.

[-- Attachment #2: Type: text/html, Size: 2002 bytes --]

  parent reply	other threads:[~2020-08-26 22:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26 21:24 Dan Cross
2020-08-26 21:30 ` Bakul Shah
2020-08-26 22:02 ` Clem Cole [this message]
2020-08-27 17:51   ` Tony Finch
2020-08-27 18:32     ` Clem Cole
2020-09-02  6:03     ` Random832
2020-09-02 15:39       ` Fabio Scotoni
2020-09-02 15:50         ` Richard Salz
2020-09-02 23:11 ` Dan Cross

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='CAC20D2N6o7YYFZQwbwdb9gdhXs_oWOtNr=MszFeiMp2UUvXm-g@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=crossd@gmail.com \
    --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).