The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <ggm@algebras.org>
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: Fri, 12 Feb 2021 15:22:37 +1000	[thread overview]
Message-ID: <CAKr6gn2ePCx77qXT2_wLf07QxKcZNd_fF-HjMYSwZnb-45HBkg@mail.gmail.com> (raw)
In-Reply-To: <m1lAJzB-0036urC@more.local>

the transition from wet to dry was amazing. we had the wet, and it
worked but was fussy. I think it was some odd DPI like 120. Lowish
res. Jaggies on the fonts. I printed a poem Dave Barron wrote about
the birth of the ICL 2900 hundred in old english font, you can see the
jaggies on it. When it first comes out, it is shiny like its just been
given birth to (sorry) and some horrendous solvent I don't want to
think about evaporated, and it was done. Sort-of shiny surface. Not
very nice.

The first decent dry laser we got was a canon unit, which IIRC was in
that olivetti "we know how do do design" space-age orange shade. It
was a giant brick on its end, about the height of a bar-fridge, and it
was 200dpi I think, and we loved it. Insanely good to get things that
clean, and not have to slice a roll of paper. I mean, for the entire
time we've been talking about Xerox machines were coming down in size
although a campus printer at the bindery for PhDs is an assembly line
of giant car sized units, but even the small ones the engineers have a
black diver case of wierd tools, gizmos to reach behind the
thingamajig and tickle the whatsit with a hairy brush.. they are
seriously complex machines (or were). Getting one of these
russian-tanks in a jet-age orange italian designer bar-fridge was ..
cool.

But then.. we realised all the s/w tools we were using were designed
for US letter. Inches. Not A4 friendly. I mean, the BSD licence I've
referred to several times, It was printed on legal, it even had the
honest-to-god crimped red seal of the regents of the university of
california on it, we didn't have envelopes which fitted this stuff. We
didn't have ring binders with holes in the right places for the
printed manuals, and when we printed our own, if we didn't check and
check and check, the US-Legal / A4 thing went bananas. People hoarded
magic init sequences to make things have margins and page sizes which
worked for them. I still remember trying to co-erce 2up printing to
work nicely.

We were so desperate for decent output there was a market for a sort
of 'player piano' box which sat on an IBM golfball printer, and
hammered the keys for you. Daisy wheel was good, but you can't beat an
IBM selectric if you want to cut a roneostat for some agitprop (they
were the invention of the devil too. the ink goes everywhere)

Nowadays, a good photocopier from fuji has a 48MP camera with a giant
lens, there is none of this scanning nonsense, its one photo and done.
The smarts are in MIPS chips and do things like hide 'you leaked it'
codes in the printed output. I used one to copy my passport for a
re-issuance recently, I swear you could pass money from them (I am
told they have image recognition for money and won't print it. Damn
skynet. they're taking over already)

On Fri, Feb 12, 2021 at 7:59 AM Greg A. Woods <woods@robohack.ca> wrote:
>
> At Wed, 10 Feb 2021 17:05:57 -0500, Clem Cole <clemc@ccc.com> wrote:
> Subject: Re: [TUHS] troff was not so widely usable (was: The UNIX Command Language (1976))
> >
> > On Wed, Feb 10, 2021 at 3:49 PM Greg A. Woods <woods@robohack.ca> wrote:
> >
> > > I would like to try once again to dispell the apparent myth that troff
> > > was readily available to Unix users in wider circles.
> > >
> > Hard to call it a myth - it was quite available.  In fact, I never used a
> > single mainstream UNIX system from DEC, IBM, HP later Sun, Masscomp, Apollo
> > that did not have it, and many if not all small systems did also.
>
> I was much deeper in the trenches!  (and in Canada too)
>
> I'm talking about small old systems, usually at very small companies but
> sometimes at very small departments in larger companies.  Things like
> early Motorola 68k, NCR-Tower, Convergent, Plexus, Spectrix (plus Tandy
> and Altos and other Xenix-based ports).  Even with full licenses the
> available nroff/troff package was often not installed as all too often
> there wasn't enough spare disk space to install it.
>
> Also with newer AT&T Unix ports, i.e. Release 2 and newer, it depended
> very much on the vendor, and sometimes even the distributor, as to
> whether or not the Documenter's Workbench would be a separate purchase
> or not, but usually it was and most of the customers I worked with would
> never pay for software that they didn't have a pressing need for, even
> if it was just a few $100.
>
> > Yes, but after Tom Ferrin created vcat(1) in the late 1970s ('77 I think,
> > but I've forgotten).   Many people did have access to a plotter which cost
> > about $1k in the late 1970s,  or even later a 'wet' laser printer like the
> > Imagen which cost about $5K a few years later.
>
> I don't know if I've ever seen a Versatec plotter, though perhaps at a
> trade show.
>
> I seem to remember grad students at university getting typeset copy off
> some kind of "wet" process typesetter driven by troff -- maybe even a
> C/A/T, but that was so far out of reach of undergrads that it wasn't
> even funny -- we just had a dot-matrix line printer (for the Unix
> machine -- there were real line printers on the Multics machine).
>
> Later on most of the kinds of customers I worked with would have a
> daisy-wheel printer at best, or perhaps just a dot-matrix line printer.
> That is until the HP Laserjet came along, followed of course not much
> longer by the Apple LaserWriter.
>
> > No offense, but that's just not true. Line printers and nroff were used a
> > great deal to prep things, and often UNIX folks had access to a daisy shell
> > printer for higher quality nroff output, much less using the line printer.
>
> Yeah, sure, lots of us Unix fans used nroff, but I doubt I ever had any
> small-system customers who used it, or would even know how to use it,
> nor would they want to learn how to use it, especially if they already
> had paid for a "proper" word processor....
>
> > > People would install Wordstar long before they even thought about using
> > > nroff.
> > >
> > I did not know anyone that did that.   But I'll take your word for it.
> > Wordstar as I recall ran on 8-bit PCs.
>
> Sorry, probably it was WordPerfect or something work-alike.
>
> The most recent site I remember using such a word processor on Unix was
> on an NCR-Tower32, which by then would have been running a newer Unix
> System V, probably Release 2, though maybe I upgraded them to Release 3
> or whatever was current from NCR in the day, but I don't remember the
> details.  They printed to a laser, probably as PCL.  That would have
> been in the very early 1990s.
>
> > FWIW: my non-techie CMU course
> > professors used to let you turning papers printed off the line printer and
> > people used anything they had - which was Scribe on the 20s and nroff on
> > the Unix, boxes and I've forgotten the name of the program that ran on the
> > TSS, which the business majors like my roommate tended to use.
>
> I remember learning the old "roff" on a PDP-11/60 (which was by then
> running V7) and submitting course work hand-cut from 132-column fan-fold
> paper.  I also remember being disappointed when they "replaced" it with
> nroff (probably it had just been an old v6 binary) and I had to learn
> how to format everything all over again.  :-)
>
>
> > > but IF And Only IF you had a C compiler _and_
> > > the skill to install it.  That combination was still incredibly rare.
> >
> > Excuse me...   most end-users sites had them.
> >
> > It sounds like your early UNIX experiences were in a limited version, which
> > is a little sad and I can see that might color your thinking.
>
> There were a great number of small sites running various different ports
> of Unix -- many of which were purpose-built to run some application such
> as an accounting system or word processing system.
>
> Often the owners didn't even really know they were running Unix or some
> derivative.  If the compiler was an add-on they certainly didn't have
> it, even if it was a free add-on.
>
> I think Microsoft Xenix for example always had an add-on compiler
> (though perhaps some of its many sub-licensees would bundle it), and of
> course by the time AT&T Unix System V came out the compiler (i.e. SGS)
> and DWB were both add-ons that took up disk space and were usually added
> $$$ too.
>
> > Hmmm ...  you were complaining you need a C compiler for ditroff, yet groff
> > needs C++ IIRC.?
>
> Plain C for "psroff", but yes, indeed, C++ for groff.
>
> > My guess this observation is because HP was late to the Postscript world
> > and there while the eventual hpcat(1) was done for the vaxen and made it
> > the USENET, it was fairly late in time, and
>
> I don't think I ever heard of hpcat, and I can only find one reference
> to it online with google (in an old 1985 Los Alamos newsletter).
>
> > I'm not sure if anyone at HP or
> > anyone else ever wrote a ditroff backend for HP's PCL.
>
> Rick Richardson wrote Jetroff.  The second release became commercial
> software, but I briefly used the original 1.0 "shareware" release quite
> successfully:
>
>         https://www.tuhs.org/Usenet/comp.sources.misc/1988-September/thread.html
>
> > The key is that Apple Laserwriters were pretty cheap and since they already
> > did PS, most sites I knew just bought PS based ones and did not go HP until
> > later when PS was built-in.
>
> My best ever used equipment deal (where I paid actual $$$), was for an
> almost brand-new Apple LaserWriter 16/600 that had come off lease at a
> PC leasing agency in Toronto.  They didn't know heads or tails about any
> kind of Apple gear and didn't know how to get the Ethernet adapter for
> it.  I paid just $64.00.  It was still on its first toner cartridge.  I
> drove away like I'd robbed the place!  Before that I had a cranky old
> monster of a PS printer of some kind -- it has a 10MB 5.25" hard drive
> in it that I think contained the fonts.
>
> --
>                                         Greg A. Woods <gwoods@acm.org>
>
> Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
> Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

  reply	other threads:[~2021-02-12  5:23 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 [this message]
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
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=CAKr6gn2ePCx77qXT2_wLf07QxKcZNd_fF-HjMYSwZnb-45HBkg@mail.gmail.com \
    --to=ggm@algebras.org \
    --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).