From: Will Senn <will.senn@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Proliferation of book print styles
Date: Sun, 2 Jun 2024 07:55:45 -0500 [thread overview]
Message-ID: <554ffdbc-dd5a-43d2-92aa-11d5d73ed715@gmail.com> (raw)
In-Reply-To: <CAKH6PiWhCYVj3FqCFRi-qoScx8x_sKZzdnC9GjNjDPna8AHtQw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
On 6/2/24 7:39 AM, Douglas McIlroy wrote:
>
> 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.)
>
Yup, that's what I was really meaning to ask and what I was hoping to
hear about.
> Moreover, WYSIWYG was out of sympathy with Unix philosophy, as it kept
> documents in a form difficult for other tools to process for
> unanticipated purposes, In this regard, I still regret that Luca
> Cardelli and Mark Manasse moved on from Bell Labs before they finished
> their dream of Blue, a WYSIWYG editor for markup documents, I don't
> know yet whether that blue-sky goal is achievable. (.docx may be seen
> as a ponderous latter-day attempt. Does anyone know whether it has
> fostered tool use?)
>
Interesting, I was wishing for something along those lines after using
TeX Studio for a while. A quick preview side by side is nice, but
wouldn't it be great to be able to work on the preview side of the pane
while the markup side changes (as minimally as possible) showing your
changes as you make them and being able to switch back and forth?
Personally, I prefer troff to tex, but just idea of markup and WYSIWYG
is enticing.
Will
[-- Attachment #2: Type: text/html, Size: 2947 bytes --]
next prev parent reply other threads:[~2024-06-02 12:55 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 [this message]
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=554ffdbc-dd5a-43d2-92aa-11d5d73ed715@gmail.com \
--to=will.senn@gmail.com \
--cc=douglas.mcilroy@dartmouth.edu \
--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).