From: Larry McVoy <lm@mcvoy.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Troff to ps
Date: Wed, 27 Jan 2021 17:59:03 -0800 [thread overview]
Message-ID: <20210128015903.GK4227@mcvoy.com> (raw)
In-Reply-To: <CAC20D2NCJEhfB5NgaigE8URTKuCqjUtr4nxtrnm4P9Fg3YQ2fA@mail.gmail.com>
I was just an engineer but what John said sort of is what I thought. There
was some money weirdness around anything above nroff/troff. I don't think
it was $5 but as I said, I was an engineer, nobody directly told me this
stuff.
On Wed, Jan 27, 2021 at 08:25:33PM -0500, Clem Cole wrote:
> Actually It was very cheap. $5 a copy if I remember correctly Masscomp
> and Stellar just ate the cost. The adobe transcript license was also
> nominal. In both cases we realized it was cheaper than trying to keep two
> separate streams and figure out which systems we shipped it too.
>
> On Wed, Jan 27, 2021 at 7:26 PM John Gilmore <gnu@toad.com> wrote:
>
> > Greg A. Woods <woods@robohack.ca> wrote:
> > > 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.
> >
> > As I recall, AT&T wanted about the same amount of money for ditroff as
> > for the entire UNIX release. So, of course no UNIX vendor was going to
> > double the royalty they paid to AT&T for every customer, for a small
> > improvement in a utility that most customers didn't even use (troff).
> >
> > John
> >
> > --
> Sent from a handheld expect more typos than usual
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2021-01-28 1:59 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
2021-01-28 0:19 ` John Gilmore
2021-01-28 1:25 ` Clem Cole
2021-01-28 1:59 ` Larry McVoy [this message]
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=20210128015903.GK4227@mcvoy.com \
--to=lm@mcvoy.com \
--cc=clemc@ccc.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).