The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Fabio Scotoni <fabio@esse.ch>
To: Bakul Shah <bakul@bitblocks.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Paper discussing Unix boot process?
Date: Thu, 11 Apr 2019 06:52:08 +0200	[thread overview]
Message-ID: <7b575d14-270c-1d3a-7419-0329ffb42669@esse.ch> (raw)
In-Reply-To: <57C2E8D6-148C-487E-A6AE-B6E0E6EC337C@bitblocks.com>

On 4/11/19 1:19 AM, Bakul Shah wrote:
> On Apr 10, 2019, at 3:24 PM, Clem Cole <clemc@ccc.com> wrote:
>>
>> [...] is the Lions book including PS and PDF and in the original troff thankfully.
> 
> Sorry to disappoint you but it's the same LaTeX source.
> 
>> [Why someone would convert it to tex is a little beyond me].
> 
> 
> May be someone will be inspired enough to convert this to troff?
> 
> 

Not to be too negative, but converting it to troff would be somewhat of
an effort; however, the gains for that seem to be comparatively small.
It would be a change from one language to another, neither of which are
a 1:1 copy of the original.
Even if you had the original troff sources of the book,
groff, heirloom-troff and Plan9 ditroff probably all have line breaking
and character positioning algorithms that don't match the original troff
at the time.

If someone were to undertake this troff endeavor, aiming for a perfect
recreation would be the most beneficial (yet also most difficult) thing
to do.
I've never seen the original commentary, but I'll assume that it used a
homebrewed set of macros.
Thus, the first step would be to reverse engineer the troff macros used
to typeset the book.
Then the TeX sources would need to be converted to those troff macros;
this can possibly be automated entirely.
Then the matching version of troff would need to be used to typeset it
(likely via apout and V6 or V7 troff).
Finally, the C/A/T typesetter output would need to be converted to
PostScript or PDF (either Adobe's psroff or Chris Lewis's psroff from
comp.unix.sources can likely help with that; I got Lewis's psroff to
work a while ago, but it's pretty brittle).

  reply	other threads:[~2019-04-11  4:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 18:02 Pat Barron
2019-04-10 18:14 ` Erik E. Fair
2019-04-10 18:28   ` Clem Cole
2019-04-10 19:05     ` Bakul Shah
2019-04-10 22:24       ` Clem Cole
2019-04-10 22:53         ` Warren Toomey
2019-04-11  1:45           ` Greg 'groggy' Lehey
2019-04-10 23:19         ` Bakul Shah
2019-04-11  4:52           ` Fabio Scotoni [this message]
2019-04-11 13:48             ` Clem Cole
2019-04-11 14:54               ` Dan Cross
2019-04-11 15:36                 ` Clem Cole
2019-06-26  2:28             ` Peter Jeremy
2019-06-26  7:57               ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2019-04-17  5:35 Paul Ruizendaal
2019-04-17 18:26 ` Warner Losh
2019-04-16 12:52 Noel Chiappa
2019-04-13 18:35 Noel Chiappa
2019-04-11  1:06 Pat Barron
2019-04-11  1:27 ` Charles Anthony
2019-04-11  2:26 ` Erik E. Fair
2019-04-10 16:51 Pat Barron
2019-04-10 17:20 ` Erik E. Fair
2019-04-10 17:57 ` Dan Cross
2019-04-19 22:31 ` Chris Hanson

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=7b575d14-270c-1d3a-7419-0329ffb42669@esse.ch \
    --to=fabio@esse.ch \
    --cc=bakul@bitblocks.com \
    --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).