The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Angelo Papenhoff <aap@papnet.eu>
To: segaloco via TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Fifth Edition Manual Restoration
Date: Wed, 8 Mar 2023 17:30:43 +0100	[thread overview]
Message-ID: <ZAi4M3cnw8xHx7ko@indra.papnet.eu> (raw)
In-Reply-To: <jzhve1rJqxoPKhUjt_Qwl0egxMPuZrgoeNMIu5cXXEgJuSgGzvVG8M62rlVUQcefjuwY5XivmWGKesNUHg-iAe7Rt4TnRRMG-jnfzuLVmgA=@protonmail.com>

Something I'd like is to recreate the original troff output exactly. I
used troff from plan 9 (so same lineage as original troff) but something
causes the output to not look exactly like the original. I don't
remember what it is exactly but you can easily check by comparing my
pdfs with the scan. Line lengths, page length, something like that.

I don't know if this is just a troff setting or if troff had changed
enough to cause this difference. Unfortunately the original troff is
lost so no way to compare. v7 (or PWB?) is the earliest version of troff
that's still around. And even then one would need CAT emulation, which I
haven't bothered with yet.

Cheers,
Angelo


On 08/03/23, segaloco wrote:
> Ouch....well I'm glad I shared then, I had no idea someone had already done this....well good to know, I guess I can move on to the CB and MERT manuals then.
> 
> - Matt G.
> 
> ------- Original Message -------
> On Wednesday, March 8th, 2023 at 2:02 AM, Angelo Papenhoff <aap@papnet.eu> wrote:
> 
> 
> > I've done this a couple of years ago:
> > http://squoze.net/UNIX
> > 
> > Cheers,
> > Angelo
> > 
> > On 08/03/23, segaloco via TUHS wrote:
> > 
> > > So I decided to keep the momentum and have just finished the first pass of a Fifth Edition manual restoration based on the same process I used for 3B20 4.1:
> > > 
> > > https://gitlab.com/segaloco/v5man
> > > 
> > > There were a few pages missing from the extant PDF scan, at least as far as pages that were in both V4 and V6 sources, so those are handled by seeing how V5 source of the few programs compares to V6. I'll note which pages required this in a second pass.
> > > 
> > > I've set my sights on V1 and V2 next, using V3's extant roff sources as a starting point, so more to come.
> > > 
> > > - Matt G.

  reply	other threads:[~2023-03-08 16:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  7:26 [TUHS] " segaloco via TUHS
2023-03-08 10:02 ` [TUHS] " Angelo Papenhoff
2023-03-08 16:02   ` segaloco via TUHS
2023-03-08 16:30     ` Angelo Papenhoff [this message]
2023-03-08 20:55       ` josh
2023-03-08 22:21         ` segaloco via TUHS
2023-03-08 23:09       ` David Arnold
2023-03-09  6:59         ` arnold
2023-03-09 14:24         ` Clem Cole
2023-03-09 20:48           ` Rob Pike
2023-03-09 21:04             ` Dave Horsfall
2023-03-09 22:32             ` Rich Salz
2023-03-09 23:51             ` Jeremy C. Reed
2023-03-10  1:58               ` Rob Pike
2023-03-10  6:33               ` Jonathan Gray
2023-03-10  7:50             ` Jonathan Gray
2023-03-10 13:11               ` Clem Cole

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=ZAi4M3cnw8xHx7ko@indra.papnet.eu \
    --to=aap@papnet.eu \
    --cc=tuhs@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).