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: Sun, 13 Mar 2022 20:17:15 -0400 (EDT) [thread overview]
Message-ID: <97175b9e-32ea-f29-ebdd-bab065b72e3f@.local> (raw)
In-Reply-To: <CAM4k_MCd8-XubW2QD6vGNzodREvgaX8kV9sHyKJNwddBw1q-3A@mail.gmail.com>
Following-up with a correction and some details about user-facing
changes in Documenter's Workbench.
>
> 1984 SVR2 containing DWB 2.0 incorporating ditroff (no postscript
> output yet though)
My mistake. I was glancing at a late copy of the 3B2 SVR2 source with
DWB 2.0 and should have written 1.0 here.
DWB 1.0 was released in 1984 at the same time as SVR2. Changes from v7
troff are the inclusion of ditroff as troff, C/A/T troff as otroff, the
mm macros, pic, and sroff. The sroff command provided a faster
simplified interpreter for line printer output.
> 1987 SVR3 unbundled all troff versions and offered DWB 2+ as
> an add-on package
DWB 2.0 was released in 1986. This verison added grap and the mptx
indexing macros while removing otroff and sroff. Elan eroff for DOS and
sqtroff were based on DWB 2.
DWB 2+ was generally available after 1987 as an optional binary add-on
package at added cost.
SVR4 troff included the postscript output formatter added to the
codebase in mid-1988 (tracked in Research UNIX v9), but not grap.
> 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)
199202 DWB 3.2 was released with mpm macros for automatic vertical page
justification, 8-bit clean i/o, and picasso visual line drawing
interface using the OPEN LOOK toolkit
199207 DWB 3.3 contained a new version of tbl and the mpm macro package
to customize postscript color and page formats
199311 DWB 3.4 with new spell check, dwb command to guess processor
pipeline, postscript file layout tools, and X11 viewers (xhbt for
eqn/pic/tbl figures and dwbman for hypertext navigation of manpages)
I hope this is a helpful summary. I've been working on a more detailed
timeline tracking the versions shipped by different UNIX vendors.
Also testing C/A/T troff to postscript converters (Adobe transcript,
Chris Lewis' psroff, and jetroff) to approximate older output in
comparison to the excellent heirloom doctools.
Thanks,
Dan Plassche
next prev parent reply other threads:[~2022-03-14 0:27 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
2022-03-14 0:17 ` Dan Plassche [this message]
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=97175b9e-32ea-f29-ebdd-bab065b72e3f@.local \
--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).