From: Jonathan Gray <jsg@jsg.id.au>
To: segaloco <segaloco@protonmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Berkeley Font Catalog
Date: Mon, 15 May 2023 10:58:41 +1000 [thread overview]
Message-ID: <ZGGDwUGaiQDUtVfs@largo.jsg.id.au> (raw)
In-Reply-To: <lUdwdyyegPN01reG6Pu4_Foacg5coHxEV5AVEEJ8St-2xmu1eFhx3Ux0AS-Nfy5XVZb1kTCeTn8WOhH1VfoRvruESdCGy4r9jZKZiFFEanY=@protonmail.com>
On Sun, May 14, 2023 at 06:17:03PM +0000, segaloco via TUHS wrote:
> 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?
The Berkeley Font Catalog appears in existing scans.
https://bitsavers.org/pdf/mtXinu/MT_XINU_Vol_0.pdf
pg 154
https://archive.org/details/bitsavers_mtXinuMTXI_21123781/page/n153/mode/2up
https://archive.org/details/h42_PCS_MUNIX_Programmers_Manual_Volume_2C/page/n107/mode/2up
https://archive.org/details/h42_PCS_MUNIX_Volume_III/page/n575/mode/2up
https://bitsavers.org/pdf/dec/vax/ultrix-32/3.0/AA-MF06A-TE_ULTRIX-32_3.0_Supplementary_Documents_Vol.1_General_User_1988.pdf
pg 520 6-27
https://archive.org/details/bitsavers_decvaxultrRIX323.0SupplementaryDocumentsVol.1Gener_33726499/page/n519/mode/2up
"A copy of volume 2C of the 4.1BSD or 4.2BSD manual includes the
Berkeley Font Catalog"
https://archive.org/details/login_sept92/page/n29/mode/2up
next prev parent reply other threads:[~2023-05-15 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 18:17 [TUHS] " segaloco via TUHS
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 [this message]
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=ZGGDwUGaiQDUtVfs@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=segaloco@protonmail.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).