The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: robpike@gmail.com, pugs@ieee.org
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Brian Kernighan and very early *roff history
Date: Fri, 14 Jan 2022 00:38:20 -0700	[thread overview]
Message-ID: <202201140738.20E7cK9S007222@freefriends.org> (raw)
In-Reply-To: <CAKzdPgwpifqN2-RvcyxevwZvWTuvS6+WP-Uw3_EBv_dK6s4xdQ@mail.gmail.com>

The name 'ditroff' for Device Independent Troff was how AT&T marketed /
sold / licensed it when they released it to the world.  The new name
was necessary to distinguish it from the original troff in V7 / System III /
System V.

It's understandable that inside Research no such distinction was made.
Nonetheless, the V8 and V10 archives show that the C/A/T variant was
still around (at least in /usr/src/cmd) under the name otroff.

HTH,

Arnold

Rob Pike <robpike@gmail.com> wrote:

> Dennis spent quite a bit of time cleaning up the troff code in the late
> 1980s, if I remember right, moving it to modern C. He got annoyed by it one
> day. It was the "ditroff" variant although honestly I don't remember us
> ever calling it that. It was just the current version of troff. Not sure
> where the name came from. Perhaps it was us but I think of it as a foreign
> name.
>
> -rob
>
>
> On Fri, Jan 14, 2022 at 11:05 AM Tom Lyon via TUHS <tuhs@minnie.tuhs.org>
> wrote:
>
> > Most of y'all are aware of Brian Kernighan's troff involvement. My
> > understanding is that he pretty much took over nroff/troff after Joe Ossana
> > died, and came out with ditroff.
> >
> > But Brian had much earlier involvement with non-UNIX *roff.  When he was
> > pursuing his PhD at Princeton, he spent a summer at MIT using CTSS and
> > RUNOFF.  When he came back to P'ton, he wrote a ROFF for the IBM 7094,
> > later translated to the IBM 360.  Many generations of students, myself
> > included, use the IBM ROFF (batch, not interactive) as a much friendlier
> > alternative to dumb typewriters.  I don't know if 360 ROFF spread beyond
> > Princeton, but I wouldn't be surprised.
> >
> > BTW, during my summer at Bell, nroff/troff was one of the few programs I
> > could not port to the Interdata 8/32 - it was just a mess of essentially
> > typeless code.  I don't think Joe Ossana got around to it either before he
> > died.
> >
> > --
> > - Tom
> >

  reply	other threads:[~2022-01-14  7:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14  0:04 Tom Lyon via TUHS
2022-01-14  0:10 ` Rob Pike
2022-01-14  7:38   ` arnold [this message]
2022-01-14 10:13   ` Jaap Akkerhuis
2022-01-14 11:48     ` Rob Pike
2022-01-14 14:08     ` Larry McVoy
2022-01-14 11:59 ` Angelo Papenhoff
2022-01-14 13:07 Noel Chiappa
2022-01-14 13:27 ` Angelo Papenhoff
2022-01-14 13:35   ` Ralph Corderoy
2022-01-14 13:55     ` Will Senn
2022-01-14 13:58       ` Will Senn
2022-01-14 14:25   ` Will Senn

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=202201140738.20E7cK9S007222@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=pugs@ieee.org \
    --cc=robpike@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).