Re: [xml2rfc] assuming that period (.) ends a sentence is sometimes wrong

Nico Williams <nico@cryptonector.com> Sat, 27 February 2021 18:01 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 347E43A113F for <xml2rfc@ietfa.amsl.com>; Sat, 27 Feb 2021 10:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
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 Xlr1Oggqhn46 for <xml2rfc@ietfa.amsl.com>; Sat, 27 Feb 2021 10:01:16 -0800 (PST)
Received: from eastern.birch.relay.mailchannels.net (eastern.birch.relay.mailchannels.net [23.83.209.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E931B3A114B for <xml2rfc@ietf.org>; Sat, 27 Feb 2021 10:01:07 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 351019221CF; Sat, 27 Feb 2021 18:01:07 +0000 (UTC)
Received: from pdx1-sub0-mail-a59.g.dreamhost.com (100-96-18-39.trex.outbound.svc.cluster.local [100.96.18.39]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id BE4F9921DCD; Sat, 27 Feb 2021 18:01:06 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a59.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.18.39 (trex/6.0.2); Sat, 27 Feb 2021 18:01:07 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Bored-Harbor: 4b4b72442088534e_1614448867007_3932413419
X-MC-Loop-Signature: 1614448867007:4224222699
X-MC-Ingress-Time: 1614448867007
Received: from pdx1-sub0-mail-a59.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a59.g.dreamhost.com (Postfix) with ESMTP id 79DFC7EFC7; Sat, 27 Feb 2021 10:01:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=BRTF8H6hhqc7Jw RsjUH9fNZtUXU=; b=YAFWQZwFpToJq0/60bb3bd66SX+RWVedhwN4BcqFVErg4Z QZcaj/vJbQrj65CEsNn8lOK8F34oTuQz8c2JhURtMjE/PzjJxXFv4l6jkzgSL5cZ PhZs9yI7YPN8ObhccVKzAN3NNZdtYXS4akRjyCPNwiu1TbokBIIf1Vmbi2Of4=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a59.g.dreamhost.com (Postfix) with ESMTPSA id 01E8C7EFD5; Sat, 27 Feb 2021 10:01:04 -0800 (PST)
Date: Sat, 27 Feb 2021 12:01:02 -0600
X-DH-BACKEND: pdx1-sub0-mail-a59
From: Nico Williams <nico@cryptonector.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: xml2rfc@ietf.org
Message-ID: <20210227180101.GC30153@localhost>
References: <87wnuucjra.fsf@fifthhorseman.net> <20210227160926.GA30153@localhost> <3494e8d8-e9bd-6c38-61f3-0c31d066a61f@gmx.de> <20210227173003.GB30153@localhost> <11d84e59-6dd9-ade8-7b07-afb34fae27e5@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <11d84e59-6dd9-ade8-7b07-afb34fae27e5@gmx.de>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/PYI4SajZJJeA_0aVjDJmDRLREoY>
Subject: Re: [xml2rfc] assuming that period (.) ends a sentence is sometimes wrong
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Feb 2021 18:01:17 -0000

On Sat, Feb 27, 2021 at 06:40:53PM +0100, Julian Reschke wrote:
> Am 27.02.2021 um 18:30 schrieb Nico Williams:
> > Is that XML or xml2rfc forcing that?
> 
> People rely on whitespace being insignificant inside <t> and similar
> elements. For instance, for indentation.

But what makes whitespace in <t> insignificant?  If it's xml2rfc, then
that can be changed.

> > > The third answer is: stop trying to. Optimizing the plain text output
> > > format really really is not important.
> > 
> > Not acceptable.
> 
> I just opened a random ancient RFC I'm familiar with (2068), and it
> hasn't two spaces after a sentence ending. At least not consistently.

So?

> So exactly when became this a "requirement"? And who determines what
> "acceptable" for plain text output?

It's very much a thing in typography to follow sentence-ending periods
with a wide space precisely to distinguish from non-sentence-ending
periods.

Nico
--