The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Ron Natalie" <ron@ronnatalie.com>
To: "The Unix Heritage Society mailing list" <tuhs@tuhs.org>
Subject: Re: [TUHS] troff was not so widely usable (was: The UNIX Command Language (1976))
Date: Thu, 11 Feb 2021 16:55:34 +0000	[thread overview]
Message-ID: <eme06a149c-6f05-48d9-841b-2c1c1ea1ccb6@alien> (raw)
In-Reply-To: <CAFH29tr=iNat7+YnBiso=sU6CYogiBaRrbpzpAmsuh_7geDnLg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

It's important to know the difference between a font and a typeface.    
A typeface isn't protectable.  That's the representation of the actual 
letters on the printed page (or screen in our case).     George was free 
to scan the output of the phototypesetter.

The font is the process to make these (in modern days small programs 
that generate the letters).  This is what can be protected by copyright.

The name can be protected by trademark as well.    HELVETICA is a 
trademark (now) of Mergenthaler Linotype.    Arial is a similar typeface 
but that name is owned by Monotype.

Straying a little from the topic, a real Linotype machine is a joy to 
behold.   They have one at the Baltimore Museum of Science and Industry 
that they still fire up weekly.   What it does is integrate a keyboard 
with the actual fonts (molds for molten lead) and casts a line of type 
(hence the name) at a time.   After it does so, the molds go back into 
sorted hoppers for further use.

To answer the other question about George Toth at JHU.   He was our 
documetnation guy and went off to work for Airinc or something.  I've 
not heard from him in a long time.    We continued to use his verset and 
a versatec for a while with straight troff.   I also hacked it to draw 
on the framebuffers in BRL's graphics labs.    Later more fonts became 
available from the Berkeley vcat/vtroff.   Ditroff allowed direct 
selection of mutliple fonts as opposed to having to hack on the 
"railmag" file (remember that guys?).

Standard troff voodoo, just put a power of two backslashes in front of 
it until it works and if you still have problems add a \c.

-Ron

[-- Attachment #2: Type: text/html, Size: 2932 bytes --]

  parent reply	other threads:[~2021-02-11 16:56 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  3:10 [TUHS] The UNIX Command Language (1976) Joachim via TUHS
2020-11-30  8:30 ` Thomas Paulsen
2020-11-30 13:36 ` Brantley Coile
2020-11-30 15:12   ` Tom Ivar Helbekkmo via TUHS
2020-11-30 15:52 ` Clem Cole
2020-11-30 16:25   ` Dan Cross
2020-11-30 16:38     ` Warner Losh
2020-11-30 16:41       ` Dan Cross
2020-11-30 16:37   ` Larry McVoy
2020-11-30 16:54     ` Clem Cole
2020-11-30 18:13       ` Theodore Y. Ts'o
2020-11-30 18:25       ` John Cowan
2020-11-30 18:37         ` Clem Cole
2020-11-30 20:11           ` arnold
2020-11-30 21:49             ` Will Senn
2020-12-01  2:55             ` Jon Steinhart
2020-11-30 18:46         ` Nemo Nusquam
2021-02-10 20:48       ` [TUHS] troff was not so widely usable (was: The UNIX Command Language (1976)) Greg A. Woods
2021-02-10 21:44         ` Larry McVoy
2021-02-10 22:05         ` Clem Cole
2021-02-11 21:58           ` Greg A. Woods
2021-02-12  5:22             ` George Michaelson
2021-02-12 22:13             ` Dave Horsfall
2021-02-12 22:18               ` Ron Natalie
2021-02-10 22:36         ` Jon Steinhart
2021-02-10 23:05           ` George Michaelson
2021-02-11  0:27             ` Ron Natalie
2021-02-11  0:36               ` Larry McVoy
2021-02-11  1:53               ` Clem Cole
2021-02-11  1:59                 ` Richard Salz
2021-02-11  2:04                   ` George Michaelson
2021-02-11  2:44                     ` Richard Salz
2021-02-11  3:02                       ` Steve Nickolas
2021-02-11  4:07                         ` Toby Thain
2021-02-11 16:55                       ` Ron Natalie [this message]
2021-02-11 20:27                         ` John Cowan
2021-02-11  2:30                 ` [TUHS] troff was not so widely usable Mary Ann Horton
2021-02-11  2:52                   ` Larry McVoy
2021-02-11  6:42                     ` Andrew Hume
2021-02-11  7:12                       ` Rob Pike
2021-02-11 13:06                         ` John Gilmore
2021-02-11 17:34                           ` Jon Forrest
2021-02-11 18:09                             ` John Cowan
2021-02-11 18:43                               ` Rich Morin
2020-12-01  3:59 ` [TUHS] The UNIX Command Language (1976) jason-tuhs
2020-12-01  4:03   ` Jon Steinhart
2020-12-01  9:27   ` Steve Nickolas
2020-12-01 15:09   ` Jim Capp
2020-12-01 15:35     ` Toby Thain
2020-12-01 15:38     ` arnold
2020-12-01 16:24       ` Warner Losh
2020-12-01 16:39         ` arnold
2020-12-01 20:13           ` Rob Pike
2020-12-02  7:08             ` arnold
2020-12-02  7:29               ` Rob Pike
2020-12-01 20:20           ` Steffen Nurpmeso
2020-12-01 20:39             ` Bakul Shah
2020-12-01 21:24               ` Dan Cross
2020-12-01 23:44                 ` John Cowan
2020-12-12 19:50           ` scj
2020-12-01 16:47         ` Larry McVoy
2020-12-01 20:13     ` Dave Horsfall
2020-12-01 20:49       ` John Cowan
2020-12-01 16:04 ` Tyler Adams

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=eme06a149c-6f05-48d9-841b-2c1c1ea1ccb6@alien \
    --to=ron@ronnatalie.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).