The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] Troff to ps
Date: Sun, 26 Jul 2020 09:56:22 -0500	[thread overview]
Message-ID: <f90685ec-29fa-d7b6-5b4d-a71aaf19476b@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1650 bytes --]

All,

So... I've moved on from v7 to 2.11bsd - shucks, vi and tar and co. just 
work there and everything else seems to be similar enough for what I'm 
interested in anyway. So yay, I won't be pestering y'all about vi 
anymore :). One the other hand, now I'm interested in printing the docs.

2.11bsd comes with docs in, of all places, /usr/doc. In there are 
makefiles for making the docs - ok, make nroff will make ascii docs, and 
troff will make troff? docs using Ossana's 'original' troff. So, after 
adding -t to it so it didn't complain about 'typesetter busy', I got no 
errors. I mounted a tape, tar'ed my .out file and untar'ed it on my 
macbook (did it for the nroff and troff output). Then I hit the first 
snag, groff -Tps -ms troff.out > whatever.ps resulted in cannot adjust 
line and cannot break line errors and groff -Tps -ms nroff.out > 
whatever.ps resulted in a bunch of double vision. I seem to recall doing 
this in v6 and it working ok (at least for nroff).

My questions:
1. Is there a troff to postcript conversion utility present in a stock 
2.11 system (or even patch level 4xx system)?
2. Is there a way to build postscript directly on the system?
3. Is there an alternative modern way to get to ps or pdf output from 
the nroff/troff that 2.11 has?

I'm still digging into the nroff stuff as that may be just minor diffs 
between ancient nroff macros and "modern" macros or even just errors 
(.sp -2 rather than .sp or .sp -1, .in -2 instead of .in +2), etc. 
Although, the files display ok in 2.11bsd using nroff -ms nroff.out...

Thanks,

Will

-- 
GPG Fingerprint: 68F4 B3BD 1730 555A 4462  7D45 3EAA 5B6D A982 BAAF


[-- Attachment #2: Type: text/html, Size: 2288 bytes --]

             reply	other threads:[~2020-07-26 14:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-26 14:56 Will Senn [this message]
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
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=f90685ec-29fa-d7b6-5b4d-a71aaf19476b@gmail.com \
    --to=will.senn@gmail.com \
    --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).