Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: segaloco <segaloco@protonmail.com>
Cc: Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: Original print of V7 manual? / My own version of troff
Date: Tue, 9 Jan 2024 17:07:40 -0500	[thread overview]
Message-ID: <CAC20D2PwTKKjAXd-tkfw=hK6V11k8+j=8n86EK0JvQi1veTU5w@mail.gmail.com> (raw)
In-Reply-To: <Zc86g8c-4HH_VPOa1hRm9KY-41ZzzYnSgir_adjejDy6GrsCxHTb9qwocryL7PTLaPK-e4Feso6SOaaLhzn0UfNRQVX2sD596N1CM7uepjU=@protonmail.com>

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

Not really UNIX -- so I'm BCC TUHS and moving to COFF

On Tue, Jan 9, 2024 at 12:19 PM segaloco via TUHS <tuhs@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).

ᐧ

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

       reply	other threads:[~2024-01-09 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240108032428.co3ozmlneoop6sa2@illithid>
     [not found] ` <20240108051049.7643537404E9@freecalypso.org>
     [not found]   ` <20240108071109.ykg42tw2gjeacs5f@illithid>
     [not found]     ` <20240109093851.2A29737401E3@freecalypso.org>
     [not found]       ` <c9cfe3f4-7751-6e83-113e-734c99de818e@bitsavers.org>
     [not found]         ` <Zc86g8c-4HH_VPOa1hRm9KY-41ZzzYnSgir_adjejDy6GrsCxHTb9qwocryL7PTLaPK-e4Feso6SOaaLhzn0UfNRQVX2sD596N1CM7uepjU=@protonmail.com>
2024-01-09 22:07           ` Clem Cole [this message]
2024-01-10  7:25             ` Lars Brinkhoff
2024-01-10 17:26               ` Clem Cole

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='CAC20D2PwTKKjAXd-tkfw=hK6V11k8+j=8n86EK0JvQi1veTU5w@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=coff@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).