From: Stuff Received <stuff@riddermarkfarm.ca>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Proliferation of book print styles
Date: Sun, 2 Jun 2024 10:48:28 -0400 [thread overview]
Message-ID: <a9078fbf-c5cd-eb24-d301-98296404fc19@riddermarkfarm.ca> (raw)
In-Reply-To: <CAKH6PiWhCYVj3FqCFRi-qoScx8x_sKZzdnC9GjNjDPna8AHtQw@mail.gmail.com>
On 2024-06-02 08:39, Douglas McIlroy wrote (in part):
> Perhaps the question you meant to ask was whether we were surprised when
> WYSIWYG took over word-processing for the masses. No, we weren't, but we
> weren't attracted to it either, because it sacrificed markup's potential
> for expressing the logical structure of documents and thus fostering
> portability of text among distinct physical forms, e.g. man pages on
> terminals and in book form or technical papers as TMs and as journal
> articles. WYSIWYG was also unsuitable for typesetting math. (Microsoft
> Word clumsily diverts to a separate markup pane for math.)
I liken suffering through WYSIWYG for math to searching through drawers
of movable type pieces for the desired piece.
Some time ago, I read a nice article titled "What you see is all you
get" but I cannot find the link (and Google fails me miserably). Found
this, though: What has WSYIWYG done for us:
https://web.archive.org/web/20050207015413/http://www.ideography.co.uk/library/seybold/WYSIWYG.html
S.
next prev parent reply other threads:[~2024-06-02 14:48 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
2024-06-04 4:26 ` Dave Horsfall
2024-06-02 14:48 ` Stuff Received [this message]
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=a9078fbf-c5cd-eb24-d301-98296404fc19@riddermarkfarm.ca \
--to=stuff@riddermarkfarm.ca \
--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).