The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Peter Yardley <peter.martin.yardley@gmail.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Proliferation of book print styles
Date: Sun, 2 Jun 2024 12:44:59 +1000	[thread overview]
Message-ID: <4CED5BE6-75C1-4A4B-B730-AF2A79150426@gmail.com> (raw)
In-Reply-To: <e61c16e2-906e-4ca3-812a-a47612b8deaa@gmail.com>

Hi,

My early days were spent in the electronics industry. I can remember receiving 3 pallets of data books from National Semiconductor. This happened every year. The Internet and the availability of on line documentation put a stop to that. It was a revolution.

> On 2 Jun 2024, at 12:31 PM, Will Senn <will.senn@gmail.com> wrote:
> 
> Today, as I was digging more into nroff/troff and such, and bemoaning the lack of brevity of modern text. I got to thinking about the old days and what might have gone wrong with book production that got us where we are today.
> 
> First, I wanna ask, tongue in cheek, sort of... As the inventors and early pioneers in the area of moving from typesetters to print on demand... do you feel a bit like the Manhattan project - did you maybe put too much power into the hands of folks who probably shouldn't have that power?
> 
> But seriously, I know the period of time where we went from hot metal typesetting to the digital era was an eyeblink in history but do y'all recall how it went down? Were you surprised when folks settled on word processors in favor of markup? Do you think we've progressed in the area of ease of creating documentation and printing it making it viewable and accurate since 1980?
> 
> I didn't specifically mention unix, but unix history is forever bound to the evolution of documents and printing, so I figure it's fair game for TUHS and isn't yet COFF :).
> 
> Later,
> 
> Will

Peter Yardley
peter.martin.yardley@gmail.com


  reply	other threads:[~2024-06-02  2:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  2:31 [TUHS] " Will Senn
2024-06-02  2:44 ` Peter Yardley [this message]
2024-06-03 21:42   ` [TUHS] " James Frew
2024-06-04  5:49     ` Dave Horsfall
2024-06-04 22:54       ` Dave Horsfall
2024-06-07  7:58         ` Peter Yardley
2024-06-02  4:03 ` Kevin Bowling
2024-06-02  8:08   ` Marc Rochkind
2024-06-02 13:50     ` Will Senn
2024-06-02 21:21     ` Kevin Bowling
2024-06-02 13:13   ` Will Senn
2024-06-02 12:39 ` Douglas McIlroy
2024-06-02 12:45   ` arnold
2024-06-02 12:55   ` Will Senn
2024-06-02 14:31   ` Al Kossow
2024-06-03  9:53     ` Ralph Corderoy
2024-06-04  4:26       ` Dave Horsfall
2024-06-02 14:48   ` Stuff Received
2024-06-02 17:44     ` Ralph Corderoy
2024-06-02 15:21   ` Michael Kjörling
2024-06-02 20:22     ` Åke Nordin
2024-06-04 13:22   ` Marc Donner
2024-06-04 14:15     ` Larry McVoy
2024-06-04 14:48     ` Ralph Corderoy
2024-06-04 14:53     ` Warner Losh
2024-06-04 15:29       ` Grant Taylor via TUHS
2024-06-05  0:13       ` Alexis
2024-06-07  7:32       ` arnold
2024-06-04 21:46     ` Adam Thornton

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=4CED5BE6-75C1-4A4B-B730-AF2A79150426@gmail.com \
    --to=peter.martin.yardley@gmail.com \
    --cc=tuhs@tuhs.org \
    --cc=will.senn@gmail.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).