The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Berkeley Font Catalog
Date: Sun, 14 May 2023 18:17:03 +0000	[thread overview]
Message-ID: <lUdwdyyegPN01reG6Pu4_Foacg5coHxEV5AVEEJ8St-2xmu1eFhx3Ux0AS-Nfy5XVZb1kTCeTn8WOhH1VfoRvruESdCGy4r9jZKZiFFEanY=@protonmail.com> (raw)

Hello, I've just today secured purchase of an original 4BSD manual and papers set and a copy of what I believe is the V6 papers set as well.  Of note amongst the tabs I could read from the pictures of the Berkeley binder was a section of fonts that I don't think I've seen before named the Berkeley Font Catalog.  I did a bit of searching around and didn't find anything matching that on first inspection re: scanned and source-available BSD doc collections.  Anyone got the scoop on this?

Either way, once these arrive in the mail in I'll try and see what the delta might be between these and the current sources in V6 and 4BSD stuff on the archive.  They're from the collection of an emeritus professor on the east coast, and I'm not sure if they represent unmodified docs shipped from Bell and Berkeley or have local modifications. In any case, his son said they'll be going through more material soon and are liable to turn up more UNIX stuff, so I'll keep folks posted if I come into possession of anything else particularly spiffy.

- Matt G.

             reply	other threads:[~2023-05-14 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-14 18:17 segaloco via TUHS [this message]
2023-05-14 19:11 ` [TUHS] " Clem Cole
2023-05-14 19:16   ` Clem Cole
2023-05-14 19:42     ` Rich Salz
2023-05-14 20:05       ` Lars Brinkhoff
2023-05-18 21:51   ` Mary Ann Horton
2023-05-15  0:58 ` Jonathan Gray
2023-05-18  2:31 ` segaloco via TUHS

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='lUdwdyyegPN01reG6Pu4_Foacg5coHxEV5AVEEJ8St-2xmu1eFhx3Ux0AS-Nfy5XVZb1kTCeTn8WOhH1VfoRvruESdCGy4r9jZKZiFFEanY=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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).