From: "Ron Natalie" <ron@ronnatalie.com>
To: "The Unix Heritage Society mailing list" <tuhs@tuhs.org>
Subject: Re: [TUHS] troff was not so widely usable (was: The UNIX Command Language (1976))
Date: Thu, 11 Feb 2021 00:27:17 +0000 [thread overview]
Message-ID: <em3e463dd7-fcad-4f96-842a-683d12f2216c@r1.local> (raw)
In-Reply-To: <CAKr6gn0qSLtnQ46f_dxXKTCo8TR9_+3sUtM6HC1n8k2rJEDqpg@mail.gmail.com>
We used nroff quite a bit with both the Model37 teletype (for which it
wsa designed, ours even had the greek box on it) and with output filters
for the lineprinter and the Diablos.
Later on we drove troff into cat emulators that used Versatec printers.
I don’t knwo wher Berkely’s vcat got their fonts, but the JHU verset
had an amusing history on that.
George Toth went down to the NRL which had a real CAT and printed out
the fonts in large point size on film. In the basement of the
biophysics bulding was a scanning transmission electron microscope which
used a PDP-11/20 as its controller and an older (512x512 or so)
framebuffer. George took the scanning wires off the microsope nad
hooked them up to the X and Y of a tektronics oscilliscope. Then he
put a photomutlipler tube in a scope camera housing and hoked the sense
wire from the microscope to that.
He now had the worlds most expensive flying spot scanner. He’d tape
one letter at a time to the scope and then bring up the microscope
sofware (DOS/BATCH I think) and tell it to run the microscope. Then
without powering down the memory in the framebuffer, he’d boot up
miniunix and copy the stuff from the framebuffer to an RX05 pack.
After months of laboriously scanning he was able to write the CAT
emulator.
I had gone to work for Martin Marietta wirking on a classified project
so I wrote hacks to the -mm macro package to handle security markings
(automatically putting the highest on each page on thte top and bottom).
Later when ditroff became available I continued to use it with
various laserprinters. I even wrote macropackages to emulate IBM’s
doc style when we were contracting with them.
This was all to the chagrin of my boss who wanted us to switch to
Framemaker.
next prev parent reply other threads:[~2021-02-11 0:28 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 3:10 [TUHS] The UNIX Command Language (1976) Joachim via TUHS
2020-11-30 8:30 ` Thomas Paulsen
2020-11-30 13:36 ` Brantley Coile
2020-11-30 15:12 ` Tom Ivar Helbekkmo via TUHS
2020-11-30 15:52 ` Clem Cole
2020-11-30 16:25 ` Dan Cross
2020-11-30 16:38 ` Warner Losh
2020-11-30 16:41 ` Dan Cross
2020-11-30 16:37 ` Larry McVoy
2020-11-30 16:54 ` Clem Cole
2020-11-30 18:13 ` Theodore Y. Ts'o
2020-11-30 18:25 ` John Cowan
2020-11-30 18:37 ` Clem Cole
2020-11-30 20:11 ` arnold
2020-11-30 21:49 ` Will Senn
2020-12-01 2:55 ` Jon Steinhart
2020-11-30 18:46 ` Nemo Nusquam
2021-02-10 20:48 ` [TUHS] troff was not so widely usable (was: The UNIX Command Language (1976)) Greg A. Woods
2021-02-10 21:44 ` Larry McVoy
2021-02-10 22:05 ` Clem Cole
2021-02-11 21:58 ` Greg A. Woods
2021-02-12 5:22 ` George Michaelson
2021-02-12 22:13 ` Dave Horsfall
2021-02-12 22:18 ` Ron Natalie
2021-02-10 22:36 ` Jon Steinhart
2021-02-10 23:05 ` George Michaelson
2021-02-11 0:27 ` Ron Natalie [this message]
2021-02-11 0:36 ` Larry McVoy
2021-02-11 1:53 ` Clem Cole
2021-02-11 1:59 ` Richard Salz
2021-02-11 2:04 ` George Michaelson
2021-02-11 2:44 ` Richard Salz
2021-02-11 3:02 ` Steve Nickolas
2021-02-11 4:07 ` Toby Thain
2021-02-11 16:55 ` Ron Natalie
2021-02-11 20:27 ` John Cowan
2021-02-11 2:30 ` [TUHS] troff was not so widely usable Mary Ann Horton
2021-02-11 2:52 ` Larry McVoy
2021-02-11 6:42 ` Andrew Hume
2021-02-11 7:12 ` Rob Pike
2021-02-11 13:06 ` John Gilmore
2021-02-11 17:34 ` Jon Forrest
2021-02-11 18:09 ` John Cowan
2021-02-11 18:43 ` Rich Morin
2020-12-01 3:59 ` [TUHS] The UNIX Command Language (1976) jason-tuhs
2020-12-01 4:03 ` Jon Steinhart
2020-12-01 9:27 ` Steve Nickolas
2020-12-01 15:09 ` Jim Capp
2020-12-01 15:35 ` Toby Thain
2020-12-01 15:38 ` arnold
2020-12-01 16:24 ` Warner Losh
2020-12-01 16:39 ` arnold
2020-12-01 20:13 ` Rob Pike
2020-12-02 7:08 ` arnold
2020-12-02 7:29 ` Rob Pike
2020-12-01 20:20 ` Steffen Nurpmeso
2020-12-01 20:39 ` Bakul Shah
2020-12-01 21:24 ` Dan Cross
2020-12-01 23:44 ` John Cowan
2020-12-12 19:50 ` scj
2020-12-01 16:47 ` Larry McVoy
2020-12-01 20:13 ` Dave Horsfall
2020-12-01 20:49 ` John Cowan
2020-12-01 16:04 ` Tyler Adams
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=em3e463dd7-fcad-4f96-842a-683d12f2216c@r1.local \
--to=ron@ronnatalie.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).