From: Sebastien F4GRX <f4grx@f4grx.net>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Original print of V7 manual? / My own version of troff
Date: Thu, 11 Jan 2024 14:52:09 +0100 [thread overview]
Message-ID: <3318dded-dc86-4403-b732-4f5d62cddbd4@f4grx.net> (raw)
In-Reply-To: <202401101850.40AIoixQ026700@cuzuco.com>
Hi,
Very interesting trivia, I didnt know, thanks!
Funnily, this scribe document has a joke about hyp-
henation.
Sebastien
Le 10/01/2024 à 19:50, tuhs@cuzuco.com a écrit :
> No idea what COFF is, but in the early 1980s, two non-troff options on
> the software side were -
>
> 1) TeX. From Donald Knuth, which means tau epsilon chi, pronounced tech
> not tex. The urban legend was upon seeing an inital copy of one of his
> books sometime in the 1970s, he yelled "blech!" and decided that if you
> wanted your documents to look right, you need to do be able to it
> yourself, and TeX rhymes with blech.
>
> 2) Scribe. From Brian Reid, of Carnegie-Mellon
> See http://www.columbia.edu/cu/computinghistory/scribe.pdf
>
> -Brian
>
> Clem Cole clemc at ccc.com wrtoe:
>> Not really UNIX -- so I'm BCC TUHS and moving to COFF
>>
>> On Tue, Jan 9, 2024 at 12:19b /PM segaloco via TUHS <tuhs at tuhs.org> wrote:
>>
>>> 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?
>>>
>> Basically, the phototypesetter part was turnkey with a built-in
>> minicomputer with a paper tape unit, later a micro and a floppy disk as a
>> cost reduction. The preparation for the typesetter was often done
>> independently, but often the vendor offered some system to prepare the PPT
>> or Floppy. Different typesetter vendors targeted different parts of the
>> market, from small local independent newspapers (such as the one my sister
>> and her husband owned and ran in North Andover MA for many years), to
>> systems that Globe or the Times might. Similarly, books and magazines
>> might have different systems (IIRC the APS-5 was originally targeted for
>> large book publishers). This was all referred to as the 'pre-press'
>> industry and there were lots of players in different parts.
>>
>> Large firms that produced documentation, such as DEC, AT&T *et al*., and
>> even some universities, might own their own gear, or they might send it out
>> to be set.
>>
>> The software varied greatly, depending on the target customer. For
>> instance, by the early 80s, the Boston Globe's input system was still
>> terrible - even though the computers had gotten better. I had a couple of
>> friends working there, and they used to b*tch about it. But big newspapers
>> (and I expect many other large publishers) were often heavy union shops on
>> the back end (layout and presses), so the editors just wanted to set strips
>> of "column wide" text as the layout was manual. I've forgotten the name of
>> the vendor of the typesetter they used, but it was one of the larger firms
>> -- IIRC, it had a DG Nova in it. My sister used CompuGraphic Gear, which
>> was based on 8085's. She had two custom editing stations and the
>> typesetter itself (it sucked). The whole system was under $35K in
>> late-1970s money - but targeted to small newspapers like hers. In the
>> mid-1908s, I got her a Masscomp at a reduced price and put 6 Wyse-75
>> terminals on it, so she could have her folks edit their stories with vi,
>> run spell, and some of the other UNIX tools. I then reverse-engineered the
>> floppy enough to split out the format she wanted for her stories -- she
>> used a manual layout scheme. She still has to use the custom stuff for
>> headlines and some other parts, but it was a load faster and more parallel
>> (for instance, we wrote an awk script to generate the School Lunch menus,
>> which they published each week).
>>
next prev parent reply other threads:[~2024-01-11 13:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 18:50 [TUHS] " 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 [this message]
2024-01-11 22:48 ` Dave Horsfall
2024-01-11 23:47 ` Greg 'groggy' Lehey
2024-01-11 23:59 ` [TUHS] Re: Subscribing to TUHS and COFF Warren Toomey via TUHS
-- strict thread matches above, loose matches on Subject: below --
2024-01-08 0:20 [TUHS] Re: Original print of V7 manual? 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
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
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=3318dded-dc86-4403-b732-4f5d62cddbd4@f4grx.net \
--to=f4grx@f4grx.net \
--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).