The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Proliferation of book print styles
Date: Mon, 03 Jun 2024 10:53:20 +0100	[thread overview]
Message-ID: <20240603095320.6ED3B21E8C@orac.inputplus.co.uk> (raw)
In-Reply-To: <78afa540-b09a-5f62-2764-c17aa9f4aec3@bitsavers.org>

Hi Al,

> I was disappointed the world tolerates the fugly typography of web
> pages.  Hundreds of years of readability knowledge thrown out the
> window.

PDFs of books have declined too, and with that the book held in the
hand.  It's as if no aesthetic judging of each page's appearance has
occurred; whatever the program produces is correct.  Probably because
many books are about technologies with little lifespan; either it will
wane or version 2.0 will need a new book.  Books on topics with a longer
life are dragged down.

Full justification is still often used.  No breaks around the start/stop
parenthetical em dash causes the very long ‘word’ to start the next
line; the line before becomes 40% space.  Sentences which start ‘I’ end
a line.  Or page.  Sans serif used so that ‘I’ is as thin as can be and
the font, to my eyes, generally lacks flow.

When there's the choice, I skim the PDF and if it's good, go with that.
Otherwise, I pluck for the worse-looking EPUB, HTML under the covers,
because I can unpack it with bsdtar(1), tinker with the HTML and CSS to
fix the worst of the appearance, and then return it to foo.epub for
reading.

-- 
Cheers, Ralph.

  reply	other threads:[~2024-06-03  9:53 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 ` [TUHS] " Peter Yardley
2024-06-03 21:42   ` 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 [this message]
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=20240603095320.6ED3B21E8C@orac.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    --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).