The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dds@aueb.gr (Diomidis Spinellis)
Subject: [TUHS] The Fourth Research Edition Unix Programmer's Manual
Date: Sun, 19 Nov 2017 14:43:23 +0200	[thread overview]
Message-ID: <d5e2a655-b969-7c7d-3747-6c4b2056b74c@aueb.gr> (raw)

I don't think we had the Fourth Research Edition Unix Programmer's 
Manual available in typeset form.  I played a bit with the troff manual 
pages on TUHS and managed to typeset it into PDF.  You can find the PDF 
document at https://dspinellis.github.io/unix-v4man/v4man.pdf.

I modernized the old shell scripts and corrected some minor markup 
glitches through commits that are recorded on a GitHub repository: 
https://github.com/dspinellis/unix-v4man.  The process was surprisingly 
smooth.  The scripts for generating the table of contents and the 
permuted index are based on the original ones.  The few problems I 
encountered in the troff source had to do with missing spaces after 
requests, the ^F hyphenation character causing groff to complain, a 
failure of groff to honor .li requests followed by a line starting with 
a ., and two uses of a lowercase letter for specifying a font.  I wrote 
from scratch a script to typeset everything into one volume.  I could 
not find a shell script for typesetting the whole manual in any of the 
Research Editions.  I assume the process of running the typesetter was 
so cumbersome, error prone, and time-consuming that it was manually 
performed on a page-by-page basis.  Correct me if I'm wrong here.

Diomidis Spinellis


             reply	other threads:[~2017-11-19 12:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 12:43 Diomidis Spinellis [this message]
2017-11-19 21:02 ` Dave Horsfall

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=d5e2a655-b969-7c7d-3747-6c4b2056b74c@aueb.gr \
    --to=dds@aueb.gr \
    /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).