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

Carsten Bormann <cabo@tzi.org> Mon, 01 November 2021 10:43 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 BEB6D3A1259 for <rfc-markdown@ietfa.amsl.com>; Mon, 1 Nov 2021 03:43:33 -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 wjYAfa160tRJ for <rfc-markdown@ietfa.amsl.com>; Mon, 1 Nov 2021 03:43:29 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.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 543723A1256 for <rfc-markdown@ietf.org>; Mon, 1 Nov 2021 03:43:29 -0700 (PDT)
Received: from [192.168.217.118] (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 4HjV4Z6j3Hz2xHT; Mon, 1 Nov 2021 11:43:26 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <AF34BD0D-DCF2-4909-9801-2018DF67CCEA@eggert.org>
Date: Mon, 01 Nov 2021 11:43:26 +0100
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 657456206.597551-f97031052bf7dd690f479f5a13a31f60
Content-Transfer-Encoding: quoted-printable
Message-Id: <88A090FB-0B39-4C6F-9BFC-01C7FC358218@tzi.org>
References: <AF34BD0D-DCF2-4909-9801-2018DF67CCEA@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/bDICeto0GCioRf5MDndanR2wi54>
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 10:43:34 -0000

On 2021-11-01, at 11:21, Lars Eggert <lars@eggert.org> wrote:
> 
> Signed PGP part
> Hi,
> 
> is there a way to prevent a double space being inserted in the ASCII rendering of an name containing an initial, e.g., make
> 
> 	W. Richard ("Rich") Stevens
> 
> render as above instead of
> 
> 	W.  Richard ("Rich") Stevens

(In the TXT, presumably — sentence spacing doesn’t survive HTML.)

If this is text you have input, you can replace the space after the dot with a non-breaking space (*).  
Can’t make an example for the input, because my mail composer swallows non-breaking spaces and replaces them with plain spaces, but the result looks like this:

With SP
   W.  Richard ("Rich") Stevens
With NBSP
   W. Richard ("Rich") Stevens

No, I don’t know why xml2rfc doesn’t apply the usual rules for keyboarding sentence ends for sentence spacing.
(Probably because enough people hate sentence spacing that any energy for a fix dissipated.)

Grüße, Carsten

(*) Depending on whether you want to keep allowing a line break here (which I would consider wrong, but tastes vary), you alternatively can insert a zero-width space U+200B right after the dot.  That actually survives Apple mail:

W. Richard ("Rich") Stevens
➔
W.​ Richard ("Rich") Stevens

Maybe I should insert these automatically after dots followed by exactly one single space(**)?  The RFC editor will hate me… :-)

(**) These otherwise don’t occur in the “new line for new sentence” keyboarding style.