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] Re: Original print of V7 manual? / My own version of troff
Date: Tue, 09 Jan 2024 17:18:30 +0000	[thread overview]
Message-ID: <Zc86g8c-4HH_VPOa1hRm9KY-41ZzzYnSgir_adjejDy6GrsCxHTb9qwocryL7PTLaPK-e4Feso6SOaaLhzn0UfNRQVX2sD596N1CM7uepjU=@protonmail.com> (raw)
In-Reply-To: <c9cfe3f4-7751-6e83-113e-734c99de818e@bitsavers.org>

On Tuesday, January 9th, 2024 at 8:27 AM, Al Kossow <aek@bitsavers.org> wrote:


> Tracing the origins of the typefaces used on the GSI/Wang typesetter is a fun rathole
> going back to Singer Graphic Systems and to Singer-Friden (ie Flexowriter) before that
> 

On the subject of troff origins, in a world where troff didn't exist, and one purchases a C/A/T, what was the general approach to actually using the thing?  Was there some sort of datasheet the vendor supplied that the end user would have to program a driver around, or was there any sort of example code or other materials provided to give folks a leg up on using their new, expensive instrument?  Did they have any "packaged bundles" for users of prominent systems such as 360/370 OSs or say one of the DEC OSs?

Similarly, were any vendor-or-locally-provided solutions used prior to the maturation of troff to the point it was used for the Fourth Edition manual typesetting?  Or was the C/A/T from day one of "production" use being driven pretty much exclusively by troff?  I admit my knowledge of this stuff is fuzzy, such as whether troff+C/A/T was the plan from the outset of acquiring the C/A/T or if there was ever a time where folks at research may have been cooking on a different approach to using the thing.

- Matt G.

  reply	other threads:[~2024-01-09 17:19 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 22:17 [TUHS] Original print of V7 manual? Mychaela Falconia
2024-01-05 23:19 ` [TUHS] " segaloco via TUHS
2024-01-06  0:12   ` Will Senn
2024-01-06  1:26   ` Mychaela Falconia
2024-01-06  5:08     ` segaloco via TUHS
2024-01-06  6:12       ` Mychaela Falconia
2024-01-06 15:06       ` Will Senn
2024-01-06  1:06 ` Al Kossow
2024-01-06  1:45   ` segaloco via TUHS
2024-01-06 14:42     ` amp1ron
2024-01-06  3:02   ` Mychaela Falconia
2024-01-06  3:22     ` G. Branden Robinson
2024-01-06  4:06       ` Jonathan Gray
2024-01-06  4:06       ` Mychaela Falconia
2024-01-06 18:33         ` Clem Cole
2024-01-06 21:04           ` Rich Salz
2024-01-06 21:38             ` Clem Cole
2024-01-10 16:32             ` Michael Parson
2024-02-10 19:43               ` Al Kossow
2024-01-07  2:17           ` Mychaela Falconia
2024-01-07  2:25             ` Al Kossow
2024-01-07  2:54             ` Phil Budne
2024-01-07  3:21               ` Mychaela Falconia
2024-01-07  3:55             ` Clem Cole
2024-01-10 16:53             ` Michael Parson
2024-01-10 17:45               ` Clem Cole
2024-01-07 10:54         ` Brian Walden
2024-01-07 12:12           ` arnold
2024-01-08  0:20           ` Mychaela Falconia
2024-01-07 21:59             ` [TUHS] My own version of troff Mychaela Falconia
2024-01-08  3:24               ` [TUHS] Re: Original print of V7 manual? / " G. Branden Robinson
2024-01-08  5:10                 ` Mychaela Falconia
2024-01-08  7:11                   ` G. Branden Robinson
2024-01-09  9:38                     ` Mychaela Falconia
2024-01-09 16:27                       ` Al Kossow
2024-01-09 17:18                         ` segaloco via TUHS [this message]
2024-01-09 18:05                           ` Phil Budne
2024-01-09 18:30                             ` Grant Taylor via TUHS
2024-01-09 20:29                           ` Al Kossow
2024-01-09 20:31                             ` Al Kossow
2024-01-09 22:07                           ` Clem Cole
     [not found]                   ` <CAGcdajdc5GfTOeP_Vw_AC0E6BdnrBLape1+GEd2JGDCg4n31eQ@mail.gmail.com>
2024-01-17 14:08                     ` G. Branden Robinson
2024-01-17 15:32                       ` Brad Spencer
2024-01-17 15:48                         ` Clem Cole
2024-01-17 16:25                           ` Rich Salz
2024-01-18  7:00                     ` Mychaela Falconia
     [not found]                       ` <CAGcdaje=RHbLNZv2Cy=xtuEMaYU7RXMtnom7gYuAMMju2xrHgw@mail.gmail.com>
2024-01-18  8:22                         ` Mychaela Falconia
2024-01-18 13:27                       ` G. Branden Robinson
     [not found]                     ` <ZalHs6DAuvRwXTuS@fluorine>
2024-01-19 16:52                       ` G. Branden Robinson
2024-01-06 14:52       ` [TUHS] Re: Original print of V7 manual? Will Senn
2024-01-06 16:52         ` Al Kossow
2024-01-06 16:54           ` Al Kossow
2024-01-06 18:28         ` G. Branden Robinson
2024-01-10 18:50 [TUHS] Original print of V7 manual? / My own version of troff tuhs
2024-01-10 22:04 ` [TUHS] " Diomidis Spinellis
2024-01-10 23:46   ` segaloco via TUHS
2024-01-11  2:20     ` Mychaela Falconia
2024-01-11 13:52 ` Sebastien F4GRX
2024-01-11 22:48 ` Dave Horsfall
2024-01-11 23:47   ` Greg 'groggy' Lehey

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='Zc86g8c-4HH_VPOa1hRm9KY-41ZzzYnSgir_adjejDy6GrsCxHTb9qwocryL7PTLaPK-e4Feso6SOaaLhzn0UfNRQVX2sD596N1CM7uepjU=@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).