The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Greg A. Woods" <woods@robohack.ca>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Troff to ps
Date: Tue, 26 Jan 2021 21:24:30 -0800	[thread overview]
Message-ID: <m1l4dJe-0036xBC@more.local> (raw)
In-Reply-To: <CAC20D2N9vMnuA9sYK2Bn_sbPySa3bpGfh93JGiQH1_iZn62P9g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2561 bytes --]

[[ sorry for the late reply -- I'm still catching up from a rather
tumultuous summer, fall, and first part of winter ]]

At Sun, 26 Jul 2020 14:03:49 -0400, Clem Cole <clemc@ccc.com> wrote:
Subject: Re: [TUHS] Troff to ps
>
> I wonder if it used troff or ditroff and then what it used for the ps
> engine (probably Ghostscript) and if ditroff, from where the font metric
> tables came?

The "psroff" Arnold referred to was written by Chris Lewis and
translated the C/A/T codes from the original v7 troff into PostScript.

It has nothing to do with the "psroff" that was in the tpscript or
Transcript PostScript add-on packages for ditroff, though it was sort of
created in parallel with what was happening with ditroff, aka DWB,
i.e. the Documenter's Workbench.

Psroff is/was kind of like "thack" and orthogonal to "cat2desk".

Once upon a time there were FAQs published regularly on Usenet where one
could learn all these kinds of things, e.g. the FAQ for comp.text.

Psroff was still very necessary at the time because there were a
plethora of "unix" vendors who were still basically using very early
System V, Xenix, or even 7th Edition licenses, and so there was no hope
of thier users ever getting something so modern and cool as ditroff.

And there was no Groff (though it appeared shortly thereafter).

On example of such a vendor was Spectrix, for whom Chris worked for at
the time he initially created psroff.  Spectrix was using Xenix, and I
think even upgraded as far as Xenix V, but it and its customers were far
too cheap for, and more or less going out of business by the time of,
ditroff et al.

Psroff 2.0 was released when I was working with Chris at Elegant
Communications.  We were still doing a bit of minor support for the few
remaining Spectrix customers, and had a Spectrix machine to do it with,
but by then it was pretty old and crusty and not of much interest.  I
seem to remember we didn't even keep it powered up for most of the time.

As I recall even some of the bigger vendors such as Sun and IBM didn't
offer ditroff in their base OS, but they did offer old troff.  Those
were the days of insane AT&T licensing and all the games competitors
played around it.

For what it's worth, back at that time I had a 3B2 at home and I was
running much a more modern version of Unix, complete with ditroff, than
anything we had at work at ECI at the time.

--
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

[-- Attachment #2: OpenPGP Digital Signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2021-01-27  5:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2020-07-26 23:37 Norman Wilson
2020-07-27 15:08 ` Jaap Akkerhuis
2020-07-28 11:33 Doug McIlroy

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=m1l4dJe-0036xBC@more.local \
    --to=woods@robohack.ca \
    --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).