The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem cole)
Subject: [TUHS] Who used *ROFF?
Date: Mon, 14 May 2018 11:04:36 -0400	[thread overview]
Message-ID: <6447802C-34AD-4F73-ACBC-8C14D9500306@ccc.com> (raw)
In-Reply-To: <F6DADFE5-62B0-4312-9668-90FD45AF1CC6@ccc.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

Thinking about this typesetter C may have been later with ditroff.  

Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 

> On May 14, 2018, at 10:45 AM, Clem cole <clemc at ccc.com> wrote:
> 
> Runoff from other systems begat Unix roff.   Which begat new roff - aka  nroff.  both assume an ASR 37 as the output device.  When the first typesetter was procured typesetter roff aka troff, was born which assumes the C/A/T as the output device (which is a binary format).    This is also were typesetter C comes from.   Note these are 3 separate and different programs although nroff and troff mostly take the same input language.  These were included in V5/6/7 IIRC 
> 
> 
> 
> When newer typesetters were obtained and after the death of troff’s author,  Brian rewrote the nroff/troff package to create ditroff- device independent typesetter roff which also could support ASCII output nroff style
> 
> This version was released independently of the OS and took a separate license.   
> 
> Ditroff was reimplemented by Clark (IIRC) to create today’s groff which takes mostly a superset of the ditroff input language.  
> 
> Sent from my PDP-7 Running UNIX V0 expect things to be almost but not quite. 
> 
>>> On May 14, 2018, at 8:41 AM, Dave Horsfall <dave at horsfall.org> wrote:
>>> 
>>> On Mon, 14 May 2018, Doug McIlroy wrote:
>>> 
>>> Here's part of the story.
>> 
>> [...]
>> 
>> You mentioned "nroff" a few times; would it not have been "troff" for their C/A/T photo-typesetter?  At least, that was the lore that I heard...
>> 
>> And what was "C/A/T" anyway (assuming that my memory is not failing me)?
>> 
>> -- Dave


  parent reply	other threads:[~2018-05-14 15:04 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-14 12:19 Doug McIlroy
2018-05-14 12:41 ` Dave Horsfall
2018-05-14 13:00   ` Ralph Corderoy
2018-05-14 14:45   ` Clem cole
2018-05-14 15:04     ` Larry McVoy
2018-05-14 15:11       ` Larry McVoy
2018-05-14 15:21         ` Jon Steinhart
2018-05-14 15:46           ` Larry McVoy
2018-05-14 15:57             ` Jon Steinhart
2018-05-14 16:41           ` Nemo Nusquam
2018-05-14 18:13             ` arnold
2018-05-14 18:18               ` Jon Steinhart
2018-05-14 18:25                 ` Larry McVoy
2018-05-14 18:33                   ` Warner Losh
2018-05-14 15:04     ` Clem cole [this message]
2018-05-14 15:33       ` arnold
2018-05-14 21:32       ` Jaap Akkerhuis
2018-05-14 21:35         ` Clem Cole
2018-05-14 16:37     ` Ralph Corderoy
2018-05-14 23:04   ` Dave Horsfall
2018-05-14 23:42   ` Ron Natalie
2018-05-14 14:34 ` Larry McVoy
2018-05-14 14:46   ` Clem cole
2018-05-14 21:02   ` Dave Horsfall
2018-05-15 14:07     ` Nemo
2018-05-15 14:37       ` Dan Cross
2018-05-15 14:55         ` Clem cole
2018-05-15 14:59           ` [TUHS] PWB - what is the history? Larry McVoy
2018-05-15 15:13             ` Warner Losh
2018-05-15 15:14             ` Dan Cross
2018-05-15 19:48               ` Lyndon Nerenberg
2018-05-15 20:33                 ` John P. Linderman
2018-05-15 21:11                   ` Clem Cole
2018-05-15 21:41                     ` Lyndon Nerenberg
2018-05-15 15:14             ` Jon Forrest
2018-05-15 15:38             ` Clem Cole
2018-05-15 15:10           ` [TUHS] Who used *ROFF? Dan Cross
2018-05-15 12:20   ` Doug McIlroy
2018-05-14 15:10 ` arnold
  -- strict thread matches above, loose matches on Subject: below --
2018-05-15 23:05 Doug McIlroy
2018-05-15 23:12 ` Noel Hunt
2018-05-25  7:01   ` aksr
2018-05-25  7:40     ` Dave Horsfall
2018-05-15 12:52 Doug McIlroy
2018-05-15 13:40 ` Clem Cole
2018-05-15 14:23   ` arnold
2018-05-15 15:56     ` Ralph Corderoy
2018-05-15 16:33       ` Clem Cole
2018-05-15 16:53         ` Warner Losh
2018-05-15 16:55       ` arnold
2018-05-15 23:45       ` Dave Horsfall
2018-05-15 23:48         ` Larry McVoy
2018-05-16 11:11           ` Dave Horsfall
2018-05-15 14:18 ` arnold
2018-05-14 17:13 Noel Chiappa
2018-05-14 21:31 ` Clem Cole
2018-05-14 15:58 Noel Chiappa
2018-05-14 16:54 ` Warner Losh
2018-05-13  5:55 Rudi Blom
2018-05-12 11:01 Noel Chiappa
2018-05-12 11:38 ` Clem cole
2018-05-12 18:56 ` Grant Taylor
2018-05-13 13:52 ` Nemo
2018-05-15  1:21 ` Dave Horsfall
2018-05-15  1:32   ` Lyndon Nerenberg
2018-05-15  2:06   ` Bakul Shah
2018-05-15  2:22     ` Jon Steinhart
2018-05-15  2:27       ` Lyndon Nerenberg
2018-05-15  2:45         ` Larry McVoy
2018-05-15  4:51           ` Dave Horsfall
2018-05-15 10:28         ` Jaap Akkerhuis
2018-05-16  0:43           ` Dave Horsfall
2018-05-15 20:49       ` Bakul Shah
2018-05-12  1:40 Nemo
2018-05-12  2:00 ` Lyndon Nerenberg
2018-05-12  2:11   ` Dave Horsfall
2018-05-12  2:17     ` Lyndon Nerenberg
2018-05-12  2:54       ` Dave Horsfall
2018-05-12  3:19         ` Dave Horsfall
2018-05-12  3:26           ` Lyndon Nerenberg
2018-05-17 15:28           ` Blake McBride
2018-05-12  4:30   ` Grant Taylor
2018-05-12  6:34     ` Dave Horsfall

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=6447802C-34AD-4F73-ACBC-8C14D9500306@ccc.com \
    --to=clemc@ccc.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).