The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Åke Nordin" <ake.nordin@netia.se>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Proliferation of book print styles
Date: Sun, 2 Jun 2024 22:22:39 +0200	[thread overview]
Message-ID: <cd4c9846-83f5-43a1-99ec-27712f760559@netia.se> (raw)
In-Reply-To: <80313ef5-2617-4150-8869-7c09c35e20aa@home.arpa>

On 2024-06-02 17:21, Michael Kjörling wrote:

> On 2 Jun 2024 08:39 -0400, from douglas.mcilroy@dartmouth.edu (Douglas McIlroy):
>> 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?)
> Does Markdown count?
>
> Especially when combined with LaTeX support for typesetting math, it's
> probably quite good enough for most peoples' needs outside of niche
> applications; and there are WYSIWYG editors (not just text editors
> with a preview, but actual WYSIWYG editors) which use Markdown as the
> storage format.
>
> Of course, what Markdown very specifically does _not_ even try to do
> is provide any strong presentation guarantees.

I haven't really participated in any real publishing endeavors
since the times of waxed sheets and scalpels, so I have precious
little firsthand experience with e.g. markdown, but I've read
quite the severe critique of its shortcomings. A prime example
is https://undeadly.org/cgi?action=article&sid=20170304230520 by
Ingo Schwarze, the main developer of mandoc together with Kristaps
Dzonsons.

This makes me believe that any WYSIWYG editor using markdown as
its storage format really uses some quite strict subset of it,
combined with its own incompatible extensions.

MfG,

-- 
Åke Nordin <ake.nordin@netia.se>, resident Net/Lunix/telecom geek.
Netia Data AB, Stockholm SWEDEN *46#7O466OI99#


  reply	other threads:[~2024-06-02 20:23 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
2024-06-02 17:44     ` Ralph Corderoy
2024-06-02 15:21   ` Michael Kjörling
2024-06-02 20:22     ` Åke Nordin [this message]
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=cd4c9846-83f5-43a1-99ec-27712f760559@netia.se \
    --to=ake.nordin@netia.se \
    --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).