From: Bakul Shah <bakul@bitblocks.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 14:58:40 -0700 [thread overview]
Message-ID: <20181026215847.4E549156E40C@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 26 Oct 2018 23:05:02 +0200." <20181026210502.GA86931@indra.papnet.eu>
On Fri, 26 Oct 2018 23:05:02 +0200 Angelo Papenhoff <aap@papnet.eu> wrote:
> On 26/10/18, Clem Cole wrote:
> > 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.
>
> Oh, that sounds good! I thought v7 troff was the first that's been
> preserved. Anyone know where to find it?
>
> > > 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.
pscat
> Hm, that sounds commercial. I'd prefer a free tool, besides, it should
> be fun to write it.
IIRC there used to be a program called thack that converted
CAT to ps. Supposedly it didn't work too well but may be a
start? Google search reveals some sources. See the one here
for example:
http://cd.textfiles.com/sourcecode/unix_c/postscrp/
No idea about the trustworthyness of this site but the program
compiles on freebsd with a few warnings.
next prev parent reply other threads:[~2018-10-26 22:26 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
2018-10-26 21:05 ` Angelo Papenhoff
2018-10-26 21:58 ` Bakul Shah [this message]
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=20181026215847.4E549156E40C@mail.bitblocks.com \
--to=bakul@bitblocks.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).