From: "Ron Natalie" <ron@ronnatalie.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
"Jaap Akkerhuis" <jaapna@xs4all.nl>
Cc: "Jacobson, Doug W [E CPE]" <dougj@iastate.edu>,
"tuhs@tuhs.org" <tuhs@tuhs.org>,
groff@gnu.org
Subject: [TUHS] Re: Old troff files (1988-2007)
Date: Sun, 06 Oct 2024 16:21:44 +0000 [thread overview]
Message-ID: <ema62b50de-925b-4e29-84be-f13f910649f2@60fbdfec.com> (raw)
In-Reply-To: <20241006151133.fbj6pmujpvuuo47d@illithid>
For years JHU had a KSR37 with a Greek box and nroff drove it direcly
sending all those ESC-8 and ESC-9 things. There were some output
filters that converted this to things like the Diablo daisy wheels and
even the rather crude dot matrix lineprinter we had.
Eventually, George Toth, one of our programmers came up with the idea of
building a C/A/T simulator. He went to the Naval Research Lab and
printed out a full typeface on film from their CAT. He then cut them
out and glued them to the front of an oscilliscope, one letter at a
time.
There was a PDP-11/20 that ran a Scanning Transmission Electron
Microscope (at the time one of the few in captivity). He would take
the scanning driver cables from the microscope and put them on the X/Y
of the oscilliscope and then took the sense wire and put it on a
photomultiplier tube that was mounted in a scope camera. He then fired
up the (DOS/BATCH) microscope software to tell it to do a scan. He’d
then swap the RK05 packs and bring up Minunix and read his scanned
character out of the frame buffer.
One character at a time he accumulated an entire Roman, Bold, Italic,
and Symbol set. He wrote the emulator and we could TROFF through his
software to the Versatec lineprinter we had. The chemicals from those
printers makes my skin break out just thinking about it. It was the
only printer we had at BRL for political reasons for quite a while. It
also would eat the ink of the government issued (made oddly by a
workshop for the blind) pens.
-Ron
next prev parent reply other threads:[~2024-10-06 16:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 21:42 [TUHS] " Jacobson, Doug W [E CPE] via TUHS
2024-10-04 21:50 ` [TUHS] " Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-10-04 21:52 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-04 22:10 ` Bakul Shah via TUHS
2024-10-04 23:01 ` Clem Cole
2024-10-04 23:16 ` Clem Cole
2024-10-05 0:14 ` G. Branden Robinson
2024-10-05 4:09 ` Peter Yardley
2024-10-05 13:14 ` Clem Cole
2024-10-05 22:22 ` G. Branden Robinson
[not found] ` <CAC20D2NgmzDxhQu5P5hjrZ3ciSv=KayiUg8GwsFRpu0wPasprw@mail.gmail.com>
2024-10-06 5:53 ` [TUHS] Why groff ms doesn't completely support historical documents G. Branden Robinson
2024-10-06 12:54 ` [TUHS] Re: Old troff files (1988-2007) Jaap Akkerhuis
2024-10-06 15:11 ` G. Branden Robinson
2024-10-06 16:21 ` Ron Natalie [this message]
2024-10-09 21:02 ` Ron Natalie
2024-10-07 14:50 ` Leah Neukirchen
2024-10-08 6:45 ` G. Branden Robinson
2024-10-08 10:33 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-08 10:49 ` G. Branden Robinson
2024-10-08 11:24 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-16 21:40 ` Anton Shepelev
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=ema62b50de-925b-4e29-84be-f13f910649f2@60fbdfec.com \
--to=ron@ronnatalie.com \
--cc=dougj@iastate.edu \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=jaapna@xs4all.nl \
--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).