Re: [Rfc-markdown] Prevent double space after initial?

Carsten Bormann <cabo@tzi.org> Mon, 01 November 2021 11:24 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5E33A1285 for <rfc-markdown@ietfa.amsl.com>; Mon, 1 Nov 2021 04:24:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pOdXMc7matoU for <rfc-markdown@ietfa.amsl.com>; Mon, 1 Nov 2021 04:24:07 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 429AE3A1244 for <rfc-markdown@ietf.org>; Mon, 1 Nov 2021 04:24:07 -0700 (PDT)
Received: from smtpclient.apple (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4HjVzQ2rMqz2xHx; Mon, 1 Nov 2021 12:24:02 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <f3837fda-12e3-3eff-93c2-40ac47751c2f@gmx.de>
Date: Mon, 01 Nov 2021 12:24:01 +0100
Cc: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C4B31A8-158B-43CD-840E-6DD8E4F07818@tzi.org>
References: <AF34BD0D-DCF2-4909-9801-2018DF67CCEA@eggert.org> <88A090FB-0B39-4C6F-9BFC-01C7FC358218@tzi.org> <f3837fda-12e3-3eff-93c2-40ac47751c2f@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/RGOXvU6lgk0rYEZYoeTqswUWh3o>
Subject: Re: [Rfc-markdown] Prevent double space after initial?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2021 11:24:12 -0000

On 1. Nov 2021, at 11:59, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> Putting workarounds into the XML source to address issues in the TXT
> output certainly is not a good idea.

Wrong mailing list.

Over in Rfc-interest I would note that we are slowly coming to terms with the fact that RFCXML needs to be able to generate multiple output formats.
(The dominant ideology during development of RFCXMLv3 was that HTML is replacing all other formats, so we don’t have to care.)

This means that we want the semantic information that is needed to generate these formats (or perform other processing, such as validating the code) to be available in the XML form.

Whether sentence detection is such semantic information can be debated.
I certainly learned that this was important when I started to use computers for text processing in the 1970s.
(I since have learned to suppress the reflex to keyboard \& after each non-period dot…)

The root cause for the specific problem that Lars had is of course our addiction to initials, which has other problems as well [1].

Back to the purpose of the mailing list:
Markdown was mostly designed to generate HTML, and since HTML by design can’t do anything useful with sentence detection, markdown has no support for it.
So support for anything that an author wants to do here is going to be an afterthought.

Grüße, Carsten

[1]: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/