From: Bakul Shah <bakul@bitblocks.com>
To: Peter Jeremy <peter@rulingia.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Paper discussing Unix boot process?
Date: Wed, 26 Jun 2019 00:57:49 -0700 [thread overview]
Message-ID: <BAD10B6B-D2CC-40AC-8F06-F3CE7A4E22C9@bitblocks.com> (raw)
In-Reply-To: <20190626022824.GA86961@server.rulingia.com>
On Jun 25, 2019, at 7:28 PM, Peter Jeremy <peter@rulingia.com> wrote:
>
> [Resurrecting an old thread to provide some input from Dave Horsfall]
> On 2019-Apr-11 06:52:08 +0200, Fabio Scotoni <fabio@esse.ch> wrote:
>> 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.
>>>
>>> May be someone will be inspired enough to convert this to troff?
Er... I wasn't entirely serious but if I were doing this, I'd start
with detexing the source and then manually adding in -ms macros.
The detexed source is about 14 lines and surprisingly readable. Almost.
This should be a piece of cake for one of you nroff wizards!
> ...
>> 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).
>
> On 2019-Jun-26 11:34:31 +1000, Dave Horsfall <dave@horsfall.org> wrote:
>> 'Twas NROFF on the CSU's LA120 (I should know; I ran the Unix section),
>> with draft versions on a Duckwriter which I helped proof-read. Don't know
>> whether custom macros were used; quite likely, as he was that sort of
>> bloke. After all, he was a Comp Sci lecturer (one of mine!) and if you
>> find yourself writing the same lines over and over again...
>>
>> Going by that snippet of the thread (too much to follow, as I'm still
>> figuring out from which lists I've been bounced) it would be a heroic
>> effort to reverse-engineer it, and quite likely not worth the trouble.
>>
>> The original source would've been at Elec Eng, but long gone by now.
>>
>> As for TROFF, well, I'm not aware that UNSW has a C/A/T :-)
>>
>> Oh, the LA120 had a single-use nylon ribbon, I think, not fabric, hence
>> the somewhat high quality (I no longer have my Lions books to check; lost
>> after several house moves).
>
> --
> Peter Jeremy
next prev parent reply other threads:[~2019-06-26 7: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
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 [this message]
-- 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=BAD10B6B-D2CC-40AC-8F06-F3CE7A4E22C9@bitblocks.com \
--to=bakul@bitblocks.com \
--cc=peter@rulingia.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).