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

Nico Williams <nico@cryptonector.com> Sun, 28 February 2021 18:00 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 719353A1A09 for <xml2rfc@ietfa.amsl.com>; Sun, 28 Feb 2021 10:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.2
X-Spam-Level:
X-Spam-Status: No, score=-0.2 tagged_above=-999 required=5 tests=[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 x8cpUGyBPPMh for <xml2rfc@ietfa.amsl.com>; Sun, 28 Feb 2021 10:00:24 -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 D491A3A1A08 for <xml2rfc@ietf.org>; Sun, 28 Feb 2021 10:00:23 -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 E86C1921500; Sun, 28 Feb 2021 18:00:21 +0000 (UTC)
Received: from pdx1-sub0-mail-a68.g.dreamhost.com (100-96-17-38.trex.outbound.svc.cluster.local [100.96.17.38]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 34AF3921113; Sun, 28 Feb 2021 18:00:08 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a68.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.96.17.38 (trex/6.0.2); Sun, 28 Feb 2021 18:00:21 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Belong-Vacuous: 67c07fb71740ef67_1614535208582_2392085483
X-MC-Loop-Signature: 1614535208581:3702742047
X-MC-Ingress-Time: 1614535208581
Received: from pdx1-sub0-mail-a68.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a68.g.dreamhost.com (Postfix) with ESMTP id 996D77E4B2; Sun, 28 Feb 2021 10:00:03 -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=LBm16lukkpk0qt DfaPlvbOX/dpg=; b=K+RHS2ff6x3QRo7GJCYmBbfjQZ/EBnIV14Hi3MHySoIYiA TIBkJk2KEKdrb+aqOpWAw3MpDLupmJIsMmBCyo6DJe9QEx3DNelYAgQHgUU/jqG/ n+Yunyr4zbY+1b1m1miz//9D8w9cb6fYqY/hi1OjqqeeUdAnwipYaoQGIDPjU=
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-a68.g.dreamhost.com (Postfix) with ESMTPSA id 528B17E4AF; Sun, 28 Feb 2021 10:00:01 -0800 (PST)
Date: Sun, 28 Feb 2021 11:59:59 -0600
X-DH-BACKEND: pdx1-sub0-mail-a68
From: Nico Williams <nico@cryptonector.com>
To: John R Levine <johnl@taugh.com>
Cc: xml2rfc@ietf.org
Message-ID: <20210228175959.GF30153@localhost>
References: <20210227191644.165F76F105E2@ary.qy> <28B528D6-7CBA-4735-A5EE-C7061D1C1D0C@tzi.org> <3dc1abe5-24bf-3b12-7b58-d06c7cde428e@taugh.com> <BBA9B16E-5B06-419D-9ABE-BFB7E69B54C9@tzi.org> <6603926-561f-c9b8-2612-2afb9847b71@taugh.com> <20210228173825.GE30153@localhost> <14ad2b3e-852a-28b1-27ae-5e25ec7823bc@taugh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <14ad2b3e-852a-28b1-27ae-5e25ec7823bc@taugh.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/fK6EI6o_zSWc-8YSegTEJQ_fvxg>
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: Sun, 28 Feb 2021 18:00:26 -0000

On Sun, Feb 28, 2021 at 12:54:45PM -0500, John R Levine wrote:
> > Provided it doesn't also lose alternative Unicode whitespace characters,
> > using &emsp; is an option.  In a pinch we could have an element to mark
> > the end of a sentence (<s/>).
> 
> At the end of every sentence?  That's, uh, quite a stretch.  Are we sure
> this problem is worth that much effort by every author?

If some such markup were only needed when the sentence-ending-period
heuristic would fail, then its usage would be very rare.  Maybe
non-breaking spacing could be used for that?