From: Dan Plassche <boomer3200@gmail.com>
To: Kevin Bowling <kevin.bowling@kev009.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Documenter's Workbench versions
Date: Wed, 9 Mar 2022 20:10:59 -0500 [thread overview]
Message-ID: <CAM4k_MCd8-XubW2QD6vGNzodREvgaX8kV9sHyKJNwddBw1q-3A@mail.gmail.com> (raw)
In-Reply-To: <CAK7dMtCE3Ybn34OyW=CM_2a7whDjhEkMGQ6L2LgaC76aMXRRrg@mail.gmail.com>
On Sun, Mar 6, 2022 at 6:02 PM Kevin Bowling <kevin.bowling@kev009.com> wrote:
>
> I see a copy of 2.0 for 3B2 (i.e.
> https://archives.loomcom.com/3b2/software/Documenters_Workbench/)
>
> From there things get a little less clear, it seems like we jump to
> 3.2 with SysVR3.2?
>
> Then there is a 3.3 version https://github.com/n-t-roff/DWB3.3
>
> Can anyone firm this lineage up a bit; and is 4.x an SGI thing or what
> (I extracted the image, the relnotes inside might as well not exist).
>
> Regards,
> Kevin
I'd be interested to pin down the timeline and the major feature changes
for DWB in relation to the other troff variants as well. Below is a
summary of my understanding from looking at the changelogs and spot
checking the various codebases. Any additions or corrections would be
appreciated.
1979 v7 C/A/T troff released (rewritten from assembler into C)
1980-81 v7 C/A/T troff pulled into System III internally at Bell Labs
seemingly without major changes and released in 1982
1982 public domain typesetter independent troff (ditroff or titroff) was
the last free release as a standalone set of files on request
1983 SVR1 bundled C/A/T troff from 1981
1984 SVR2 containing DWB 2.0 incorporating ditroff (no postscript
output yet though)
1987 SVR3 unbundled all troff versions and offered DWB 2+ as
an add-on package
1988 postscript output added to DWB 2+
1989 SVR4 bundled DWB 2+ (Solaris and Unixware) with changes
through mid-1988
198907 DWB 3.0 changed font tables to ascii from old binary format
199004 DWB 3.1 retired nroff for monolithic troff binary with -a flag
for simplified ascii output (for example, tables are not formatted
for true hardcopy output in ascii format)
I think sqtroff from Softquad was primarily sold from 1987-88 and the
main enhancement was more detailed error tracing with an improved
ditroff output language including early laserjet and postscript support.
I've only seen mentions of sqtroff 2.x releases in that timeframe.
I've been looking for the Softquad documentation and software
without much luck; apparently James Clark had a copy of the
Technical Reference manual (ISBN 0-88910-326-7) that he
used to write groff.
Best,
Dan Plassche
next prev parent reply other threads:[~2022-03-10 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 1:02 Kevin Bowling
2022-03-07 2:42 ` Larry McVoy
2022-03-07 13:28 ` Jaap Akkerhuis
2022-03-07 16:55 ` Kevin Bowling
2022-03-10 17:21 ` ozan yigit
2022-03-07 20:57 ` Kevin Bowling
2022-03-09 22:30 ` Andrew Diller
2022-03-10 0:44 ` Kevin Bowling
2022-03-10 2:17 ` Andrew Diller
2022-03-10 1:10 ` Dan Plassche [this message]
2022-03-14 0:17 ` Dan Plassche
2022-03-13 5:24 ` Warren Toomey
2022-03-09 2:06 Douglas McIlroy
2022-03-09 9:41 ` Jaap Akkerhuis
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=CAM4k_MCd8-XubW2QD6vGNzodREvgaX8kV9sHyKJNwddBw1q-3A@mail.gmail.com \
--to=boomer3200@gmail.com \
--cc=kevin.bowling@kev009.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).