Re: [TUHS] Re: Original print of V7 manual? / My own version of troff

[John Gardner]

>
> If you don't have my scan of CSTR #54 (1976) […] let me know and I'll send
> it along.

I have a copy named CSTR_54_1976.pdf with a SHA256 checksum of
71d8592991635966cc86a184d7a5b07163298a53c2a900fa0e9bf1a3eabeeb7d. Is this
it?

It's decent-enough quality, but I wanted to check to make sure there wasn't
a higher-resolution copy I could be working off. So, no complaints. How
urgently are the C/A/T typefaces needed?

Too bad Unix V7 didn't have Perl, since this is basically a text
> transformation problem.

It *does* have awk(1) and sed(1), IIRC, which I can get by with for most
text-wrangling tasks. :)

Let me know in private mail where you got stuck.  Maybe I can help.

I'll probably need you to review any shims I write for any C89+ stdio(3)
functions that don't exist in V7's C compiler (which is surprisingly
limited)…

Thanks!
— John



On Thu, 18 Jan 2024 at 01:08, G. Branden Robinson <
g.branden.robinson@gmail.com> wrote:

> Hi John,
>
> At 2024-01-18T00:43:41+1100, John Gardner wrote:
> > I'm a professional graphic designer with access to commercial typeface
> > authoring software. Send me the highest-quality and most comprehensive
> > scans of a C/A/T-printed document, and I'll get to work.
>
> If you don't have my scan of CSTR #54 (1976), which helpfully dumps all
> of the glyphs in the faces used by the Bell Labs CSRC C/A/T-4, let me
> know and I'll send it along.  I won't vouch for its high quality but it
> should be comprehensive with respect to coverage.
>
> > Thanks for reminding me, Branden. :) I've yet to get V7 Unix working
> > with the latest release of SimH,
>
> Let me know in private mail where you got stuck.  Maybe I can help.
>
> > I'm still up for this, assuming you've not already started.
>
> No, I haven't--perhaps because I am an Ada fanboy, the prospect of
> coding in pre-standard C and its mission to turn anything that can be
> lexically analyzed into _some_ sequence of machine instructions has not
> stoked my excitement.
>
> (Which isn't to say that one _can't_ write safe code using K&R C; my
> fear is that having to remember all of the things the compiler won't do
> for you would overwhelm the task at hand.  Too bad Unix V7 didn't have
> Perl, since this is basically a text transformation problem.)
>
> Regards,
> Branden
>