From: Jonathan Gray <jsg@jsg.id.au>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Update CSTR tarball
Date: Mon, 28 Aug 2023 11:01:56 +1000 [thread overview]
Message-ID: <ZOvyBI4gPbsNbdM4@largo.jsg.id.au> (raw)
In-Reply-To: <CAKH6PiWeyyMsK1HQEnnOz8L2QXTX=9W9htEHzA9iy6QJDZrvRw@mail.gmail.com>
On Sun, Aug 27, 2023 at 04:23:30PM -0400, Douglas McIlroy wrote:
> Here's the status of source for CSTRs by me. All extant source is troff -ms.
> Which ones might be wanted?
>
> 14 Synthetic speech
> Source does not exist; scanned pages are available.
41 An Algorithm for Differential File Comparison
source for the reconstructed version of this may also exist?
>
> 139 Unix reader
> Source exists for front matter including combined table of contents,
> but not for pages copied from Unix manuals.
>
> 155 Trilogy on ellipses
> Source exists.
> Figures for the first paper are in Ideal, together with troff intermediate.
>
> 163 IX
> Source exists.
>
> On Sun, Aug 27, 2023 at 2:04 PM <arnold@skeeve.com> wrote:
> >
> > Hello All.
> >
> > Nelson Beebe has added PDF files for all the .ps files that didn't
> > have them, and I did a little bit more cleaning up of the CSTRs
> > I made available late last week. The new file is at
> >
> > https://www.skeeve.com/combined-cstr-2.tar.gz
> >
> > Warren will eventually add them to the archive, at which point I will
> > probably take down my copies.
> >
> > Nelson and I request of the CSTR authors who are on the TUHS list if
> > they are willing to make source code for their CSTRs available? That
> > would certainly help in the preservation effort.
> >
> > Thanks,
> >
> > Arnold
>
next prev parent reply other threads:[~2023-08-28 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 18:03 [TUHS] " arnold
2023-08-27 20:23 ` [TUHS] " Douglas McIlroy
2023-08-27 20:50 ` arnold
2023-08-28 1:01 ` Jonathan Gray [this message]
2023-08-27 21:49 ` Warren Toomey via TUHS
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=ZOvyBI4gPbsNbdM4@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=douglas.mcilroy@dartmouth.edu \
--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).