From: Larry McVoy <lm@mcvoy.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>,
?????? <nabijaczleweli@nabijaczleweli.xyz>,
linux-man@vger.kernel.org, tuhs@tuhs.org
Subject: Re: [TUHS] Re: Unix V10 Volume 2 PDFs
Date: Wed, 12 Feb 2025 17:45:22 -0800 [thread overview]
Message-ID: <20250213014522.GF31438@mcvoy.com> (raw)
In-Reply-To: <20250213012107.urh4ndk4tnnzm3wx@illithid>
On Wed, Feb 12, 2025 at 07:21:07PM -0600, G. Branden Robinson wrote:
> > Doesn't groff(1) handle the Unix sources?
>
> Assuming the full source of a document is available, and no part of its
> toolchain requires software that is unavailable (like Van Wyk's "ideal"
> preprocessor) then if groff cannot satisfactorily render a document
> produced by the Bell Labs CSRC, then I'd consider that presumptively a
> bug in groff.
In my experience, groff has handled decades old troff source and done
a great job. I'd not be surprised if there was something that didn't
work, but the vast majority of the stuff I've tried has worked just
fine.
--lm
next prev parent reply other threads:[~2025-02-13 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 23:59 Unix V10 Volume 2 PDFs Alejandro Colomar
2025-02-13 1:21 ` G. Branden Robinson
2025-02-13 1:45 ` Larry McVoy [this message]
2025-02-13 9:49 ` Alejandro Colomar
2025-02-13 15:03 ` Alejandro Colomar
2025-02-13 2:12 ` наб
2025-02-13 9:40 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2025-02-13 1:52 [TUHS] " Norman Wilson
2025-02-13 14:53 ` Dan Cross
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=20250213014522.GF31438@mcvoy.com \
--to=lm@mcvoy.com \
--cc=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--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