From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: "Jacobson, Doug W [E CPE]" <dougj@iastate.edu>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>, "groff@gnu.org" <groff@gnu.org>
Subject: [TUHS] Re: Old troff files (1988-2007)
Date: Tue, 8 Oct 2024 05:49:33 -0500 [thread overview]
Message-ID: <20241008104933.snbk6wxt4rpaahfl@illithid> (raw)
In-Reply-To: <CH2PR04MB6742FBE550DCE1B8C52553D9AC7E2@CH2PR04MB6742.namprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
[dropped Clem and Leah from CC]
Hi Doug,
At 2024-10-08T10:33:35+0000, Jacobson, Doug W [E CPE] wrote:
> Using Groff (eqn+pic) + grap I was able to create a PDF of the book.
> It took about 8 hours
8-O
> part of which was figuring out the syntax differences.
Oh, wall clock time including human engagement. That sounds really
reasonable! I'm not sure I want to estimate how many hours I've put
into revising groff's own documentation. Or ncurses's.
Eight hours processing time on a modern machine (without inflooping)
would be shocking to me.
> He had divided the book up into a file for each page or two, so 100+
> files. I think he did that, so he did not waste paper since he had to
> print out the pages to see if they looked right, no display to view
> them.
No PostScript or PDF preview program? I can think of a few: mupdf,
evince, okular. Deri James (groff developer) can probably name a dozen.
> It was not perfect but is good enough for the publisher to review.
> The book is on filters (EE book) and is full of graphs, circuits, and
> equations. He used pic to draw the circuits, which was amazing. This
> was fun to take a forgotten manuscript written by a colleague and with
> luck maybe getting it published while he is still alive. If the
> publisher wants to publish it, I'm not sure how they will handle troff
> files :)
If you'd care to share it with me in my capacity as groff maintainer,
I'd be interested to use it for unofficial regression testing.
Alternatively, if you can't find an interested publisher, please
consider asking the author (I assume he's also the copyright holder) to
release it under a Creative Commons license so the whole world can
enjoy. Also, so I can selfishly enjoy the pleasure of pointing to a
sophisticated typeset work and saying, "look what groff can do!" ;-)
(Just in case people aren't impressed enough with K&R or W. Richard
Stevens.)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-08 10:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 21:42 [TUHS] " Jacobson, Doug W [E CPE] via TUHS
2024-10-04 21:50 ` [TUHS] " Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-10-04 21:52 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-04 22:10 ` Bakul Shah via TUHS
2024-10-04 23:01 ` Clem Cole
2024-10-04 23:16 ` Clem Cole
2024-10-05 0:14 ` G. Branden Robinson
2024-10-05 4:09 ` Peter Yardley
2024-10-05 13:14 ` Clem Cole
2024-10-05 22:22 ` G. Branden Robinson
[not found] ` <CAC20D2NgmzDxhQu5P5hjrZ3ciSv=KayiUg8GwsFRpu0wPasprw@mail.gmail.com>
2024-10-06 5:53 ` [TUHS] Why groff ms doesn't completely support historical documents G. Branden Robinson
2024-10-06 12:54 ` [TUHS] Re: Old troff files (1988-2007) Jaap Akkerhuis
2024-10-06 15:11 ` G. Branden Robinson
2024-10-06 16:21 ` Ron Natalie
2024-10-09 21:02 ` Ron Natalie
2024-10-07 14:50 ` Leah Neukirchen
2024-10-08 6:45 ` G. Branden Robinson
2024-10-08 10:33 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-08 10:49 ` G. Branden Robinson [this message]
2024-10-08 11:24 ` Jacobson, Doug W [E CPE] via TUHS
2024-10-16 21:40 ` Anton Shepelev
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=20241008104933.snbk6wxt4rpaahfl@illithid \
--to=g.branden.robinson@gmail.com \
--cc=dougj@iastate.edu \
--cc=groff@gnu.org \
--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).