From: arnold@skeeve.com
To: will.senn@gmail.com, tuhs@minnie.tuhs.org, arnold@skeeve.com
Subject: Re: [TUHS] Troff to ps
Date: Sun, 26 Jul 2020 09:35:57 -0600 [thread overview]
Message-ID: <202007261535.06QFZvLg027250@freefriends.org> (raw)
In-Reply-To: <202007261531.06QFVqZb027062@freefriends.org>
Some web searching turns up something called 'psroff' from the late 80s
or so that will convert C/A/T to postscript. Google 'psroff source' and
you should find something you can use.
Arnold
arnold@skeeve.com wrote:
> Will Senn <will.senn@gmail.com> wrote:
>
> > My questions:
> > 1. Is there a troff to postcript conversion utility present in a stock
> > 2.11 system (or even patch level 4xx system)?
>
> Troff from that era was designed to drive the C/A/T phototypesetter.
> There were tools that converted from C/A/T to postscript but they
> were mostly commercial IIRC.
>
> > 2. Is there a way to build postscript directly on the system?
>
> Likely not.
>
> > 3. Is there an alternative modern way to get to ps or pdf output from
> > the nroff/troff that 2.11 has?
>
> I would recommend tar-ing up the doc and macros, moving them to Linux
> or other modern system, and using groff -C to create postscript/pdf.
> That really will be the fastest way.
>
> Arnold
next prev parent reply other threads:[~2020-07-26 15:38 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 [this message]
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
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=202007261535.06QFZvLg027250@freefriends.org \
--to=arnold@skeeve.com \
--cc=tuhs@minnie.tuhs.org \
--cc=will.senn@gmail.com \
/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).