The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] Troff to ps
Date: Sun, 26 Jul 2020 19:37:17 -0400 (EDT)	[thread overview]
Message-ID: <20200727113023.D44494422C@lignose.oclsc.org> (raw)

Nemu Nusquam:

  When was dpost born?

=====

CSTR 97, A Typesetter-Independent TROFF by Brian W Kernighan
was issued in 1981 and revised the next year.  So that's the
earliest possible date.

I vaguely remember the existence of Postscript support in
general, including at least one Apple Laserwriter kicking
around somewhere, starting at some point during my time at
1127 in the latter 1980s.  There was even a Postscript
display engine that ran on 5620 terminals under mux, though
it wasn't normally used for troff previewing because the
troff-specific proofer was faster (mainly, I think, it
didn't send nearly as much data down the serial line to
the terminal).

My personal snapshot of V10, and the TUHS archive copy,
include dpost; see src/cmd/postscript/dpost.  Everything
in the postscript directory came from USG, who had
packaged everything troff into a separately-licensed
Documenter's Workbench package.  That may have made us
exclude it from the officially-distributed V8 tape and
V9 snapshots.  In any case, the only V9 snapshot I know
of offhand (which is in Warren's archive) has no dpost.

Both my copy of V10 and the TUHS copy show dpost's
source files with dates in 1991, but it was certainly
there earlier if I used it in New Jersey (I left in
mid-1990).  Dpost is documented in man8/postscript.8;
my copy of that file is dated October 1989.

Digging around in documents available on the web,
I found a bundle of DWB 2.0 docs:

http://www.bitsavers.org/pdf/att/unix/Documentors_Workbench_1989/UNIX_System_V_Documentors_Workbench_Reference_Manual_1989.pdf

It's a scanned-image PDF so I can't search it by
machine, but it includes such things as listings of
the source-code directory and manifests of various
binary distributions, and dpost doesn't appear anywhere
I can see.  As the URL implies, the docs seem to
be dated 1989.  So maybe dpost wasn't part of the
product until DWB 3.0; but maybe we in Research got
an early copy of the postscript stuff (I think bwk
was in regular communication with the USG-troff
folks), perhaps in 1989.

I confess I've lost track of the original question
that spawned this thread, but if it is whether
dpost is easily back-ported to PDP-11 UNIX, I don't
think that's likely without a good bit of work.
It would very likely require a post-1980-type C
compiler, since it was written in the late 1980s.
It might or might not fit on a PDP-11; I don't
remember whether USG's system still officially
ran there by the late 1980s.

Norman Wilson
Toronto ON

             reply	other threads:[~2020-07-27 11:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 23:37 Norman Wilson [this message]
2020-07-27 15:08 ` Jaap Akkerhuis
  -- strict thread matches above, loose matches on Subject: below --
2020-07-28 11:33 Doug McIlroy
2020-07-26 14:56 Will Senn
2020-07-26 15:31 ` arnold
2020-07-26 15:35   ` arnold
2020-07-26 16:15     ` Clem Cole
2020-07-26 17:11       ` arnold
2020-07-26 18:03         ` Clem Cole
2021-01-27  5:24           ` Greg A. Woods
2021-01-28  0:19             ` John Gilmore
2021-01-28  1:25               ` Clem Cole
2021-01-28  1:59                 ` Larry McVoy
2021-01-28  3:19                 ` John Gilmore
2021-01-28 12:58                 ` Clem Cole
2020-07-26 19:05   ` Nemo Nusquam
2020-07-26 22:39     ` Noel Hunt
2020-07-27  5:31     ` arnold
2020-07-27  9:19       ` Jaap Akkerhuis
2020-07-27 11:07         ` Brad Spencer
2020-07-27 15:58   ` Will Senn
2020-07-26 15:33 ` Clem Cole
2020-07-27 15:53   ` Will Senn
2020-07-26 18:09 ` Al Kossow

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=20200727113023.D44494422C@lignose.oclsc.org \
    --to=norman@oclsc.org \
    --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).