From: johnl@johnlabovitz.com (John Labovitz)
Subject: [TUHS] CSTR files
Date: Fri, 25 Aug 2017 16:27:04 -0400 [thread overview]
Message-ID: <31E4B337-C3D7-4B80-AB7F-23EAD058630F@johnlabovitz.com> (raw)
In-Reply-To: <201708251827.v7PIRiRZ079233@elf.torek.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Aug 25, 2017, at 2:27 PM, Chris Torek <torek at torek.net> wrote:
>> As a *roff fan, I'd love, love, love to see the original roff sources.
>
> The *original* original (Unix) roff (not sure if there was
> a precursor elsewhere) was in pdp-11 assembly.
Last fall, I wrote an article for the American Printing History Association called 'The Electric Typesetter: The Origins of Computing in Typography.’ In doing research, I found the earliest succession of roff predecessors went something like this:
TJ-2 -> RUNOFF (capitals) -> runoff (lowercase) -> rf -> roff
TJ-2 is described at <http://www.dpbsmith.com/tj2.html>. I don’t have info on the other processors at hand at the moment.
Folks here might be interested in my article, but sadly the journal doesn’t tend to put their content online for quite a while. The TOC for the issue is at <https://printinghistory.org/publications/printing-history/ns/#21>.
—John
next prev parent reply other threads:[~2017-08-25 20:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 11:01 Aharon Robbins
2017-08-25 11:30 ` Warren Toomey
2017-08-25 12:32 ` arnold
2017-08-25 14:04 ` Larry McVoy
2017-08-25 18:27 ` Chris Torek
2017-08-25 20:27 ` John Labovitz [this message]
2017-08-25 21:04 ` Arthur Krewat
2017-08-25 21:16 ` Warner Losh
2017-08-26 9:48 ` Mutiny
2017-08-27 15:11 ` arnold
2017-08-27 15:48 ` Steve Simon
2017-08-27 21:03 ` William Cheswick
2017-08-25 20:59 Noel Chiappa
2017-08-25 21:33 ` John Labovitz
2017-08-25 21:47 Noel Chiappa
2017-08-28 3:04 Doug McIlroy
2017-08-28 4:00 ` Noel Hunt
2017-08-28 4:16 ` arnold
2017-08-28 4:10 ` Toby Thain
2017-08-28 12:47 ` John Labovitz
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=31E4B337-C3D7-4B80-AB7F-23EAD058630F@johnlabovitz.com \
--to=johnl@johnlabovitz.com \
/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).