From: Clem Cole <clemc@ccc.com>
To: Angelo Papenhoff <aap@papnet.eu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Reconstructed and newly set UNIX Manual
Date: Fri, 26 Oct 2018 16:41:13 -0400 [thread overview]
Message-ID: <CAC20D2MqYoGMKPQtCh3xtNpZQ_ftDv-0k22srNzrrJkyyUdTUA@mail.gmail.com> (raw)
In-Reply-To: <20181026194636.GA11870@indra.papnet.eu>
[-- Attachment #1: Type: text/plain, Size: 504 bytes --]
On Fri, Oct 26, 2018 at 3:55 PM Angelo Papenhoff <aap@papnet.eu> wrote:
>
> And most importantly: is the old troff really lost?
>
The question is how old? I thought we found a pre-ditroff (v6 binary) at
one point, but I don't think we have anything older than that.
> I would love to set the manual on the original systems
> at some point (and write a CAT -> ps converter, which should be fun).
>
I'm pretty sure this already exists. It was part of the Adobe 'transcript'
package back in the day.
[-- Attachment #2: Type: text/html, Size: 1178 bytes --]
next prev parent reply other threads:[~2018-10-26 20:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-26 19:46 Angelo Papenhoff
2018-10-26 19:57 ` Jim Capp
2018-10-26 20:41 ` Clem Cole [this message]
2018-10-26 21:05 ` Angelo Papenhoff
2018-10-26 21:58 ` Bakul Shah
2018-10-26 20:59 ` Warren Toomey
2018-10-27 17:15 ` Angelo Papenhoff
2018-10-27 17:41 ` Angelo Papenhoff
[not found] ` <20181026214308.GA20796@minnie.tuhs.org>
[not found] ` <20181026221153.GA19920@indra.papnet.eu>
2018-10-26 22:29 ` Angelo Papenhoff
2018-10-26 23:06 ` Warner Losh
2018-10-26 23:46 ` Larry McVoy
2018-10-28 22:57 ` Angelo Papenhoff
2018-10-29 0:15 ` Clem cole
2018-11-01 17:21 ` Angelo Papenhoff
2018-10-27 11:59 Doug McIlroy
2018-10-27 12:28 ` Angelo Papenhoff
2018-10-27 13:07 ` Milo Velimirovic
2018-10-27 13:56 ` Toby Thain
2018-10-27 15:19 ` Ralph Corderoy
2018-10-27 15:53 ` Clem Cole
2018-10-27 16:25 ` Larry McVoy
2018-10-27 19:45 ` Lars Brinkhoff
2018-10-27 14:18 Nelson H. F. Beebe
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=CAC20D2MqYoGMKPQtCh3xtNpZQ_ftDv-0k22srNzrrJkyyUdTUA@mail.gmail.com \
--to=clemc@ccc.com \
--cc=aap@papnet.eu \
--cc=tuhs@minnie.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).