From: Jaap Akkerhuis <jaapna@xs4all.nl>
To: Norman Wilson <norman@oclsc.org>
Cc: TUHS <tuhs@tuhs.org>
Subject: Re: [TUHS] Troff to ps
Date: Mon, 27 Jul 2020 17:08:54 +0200 [thread overview]
Message-ID: <E1E60E56-2A0E-4D19-80A4-F3BF4DD0BBEE@xs4all.nl> (raw)
In-Reply-To: <20200727113023.D44494422C@lignose.oclsc.org>
[-- Attachment #1: Type: text/plain, Size: 1341 bytes --]
> On Jul 27, 2020, at 1:37, Norman Wilson <norman@oclsc.org> wrote:
>
> 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.
But that was before postscript, that was for the new typesetter.
> 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.
First there was the Canon (LP 10 I believe) and postscript came later.
SoftQuad licensed the DWB quite early in the process.
> 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.
There was quite some communication between Peter Nilson (npn, known
for picasso) and bwk. I myself ended up working on the last DWB
(3.4.1).
jaap
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2020-07-27 15:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 23:37 Norman Wilson
2020-07-27 15:08 ` Jaap Akkerhuis [this message]
-- 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=E1E60E56-2A0E-4D19-80A4-F3BF4DD0BBEE@xs4all.nl \
--to=jaapna@xs4all.nl \
--cc=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).