Re: [xml2rfc] Word enforcing 1 space between sentences

Nico Williams <nico@cryptonector.com> Thu, 30 April 2020 19:57 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 E2E393A1214 for <xml2rfc@ietfa.amsl.com>; Thu, 30 Apr 2020 12:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_BL=0.001, RCVD_IN_MSPIKE_L3=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 JzENvywKF-Dd for <xml2rfc@ietfa.amsl.com>; Thu, 30 Apr 2020 12:57:03 -0700 (PDT)
Received: from fossa.birch.relay.mailchannels.net (fossa.birch.relay.mailchannels.net [23.83.209.62]) (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 931BE3A1212 for <xml2rfc@ietf.org>; Thu, 30 Apr 2020 12:57:03 -0700 (PDT)
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 BEF2F921ADD; Thu, 30 Apr 2020 19:57:02 +0000 (UTC)
Received: from pdx1-sub0-mail-a9.g.dreamhost.com (100-96-23-11.trex.outbound.svc.cluster.local [100.96.23.11]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 4F729921992; Thu, 30 Apr 2020 19:57:02 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a9.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.6); Thu, 30 Apr 2020 19:57:02 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Arch-Illegal: 307bffdc3bb6b877_1588276622586_2041652538
X-MC-Loop-Signature: 1588276622586:1188805750
X-MC-Ingress-Time: 1588276622586
Received: from pdx1-sub0-mail-a9.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a9.g.dreamhost.com (Postfix) with ESMTP id 048B87F004; Thu, 30 Apr 2020 12:57:02 -0700 (PDT)
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:content-transfer-encoding; s= cryptonector.com; bh=Utl4Z4dpw6qd3UUErG+KEBFn2ng=; b=CWiq7yOhbL/ JL9IhCauf7z28Gp7eq8wtfq6rhbQIi9MSLO10/ayMu0B/LmU8BDZ+gq9ZsU2iFIQ C8YCzkVwLPXP9GXBcl8eERMrywdaGODV7V+VU3mJ+Yd/Gh3WM1tw6N8720DDxKUZ C0WoLoDvsXqJNiRYaL5TRH1vWk2Nxol0=
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-a9.g.dreamhost.com (Postfix) with ESMTPSA id 8F18A7F001; Thu, 30 Apr 2020 12:56:59 -0700 (PDT)
Date: Thu, 30 Apr 2020 14:56:56 -0500
X-DH-BACKEND: pdx1-sub0-mail-a9
From: Nico Williams <nico@cryptonector.com>
To: Robert Moskowitz <rgm@htt-consult.com>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
Message-ID: <20200430195655.GF18021@localhost>
References: <555f5ab1-a3a0-7710-0581-4d13bb641325@htt-consult.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <555f5ab1-a3a0-7710-0581-4d13bb641325@htt-consult.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: 0
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrieehgddugeduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjfgesthekredttderudenucfhrhhomheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqeenucggtffrrghtthgvrhhnpeevleelleetuedtteeiledtueethfetffehteevudevvedthfevfffhtddttdehleenucfkphepvdegrddvkedruddtkedrudekfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehlohgtrghlhhhoshhtpdhinhgvthepvdegrddvkedruddtkedrudekfedprhgvthhurhhnqdhprghthheppfhitghoucghihhllhhirghmshcuoehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmqedpmhgrihhlfhhrohhmpehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhmpdhnrhgtphhtthhopehnihgtohestghrhihpthhonhgvtghtohhrrdgtohhm
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/u0vqMFBsKMuxy_WyqNZfjgDNjqk>
Subject: Re: [xml2rfc] Word enforcing 1 space between sentences
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: Thu, 30 Apr 2020 19:57:06 -0000

On Tue, Apr 28, 2020 at 03:12:10PM -0400, Robert Moskowitz wrote:
> I recently saw a fluff piece about MS Word now enforcing 1 space between
> sentences.  If you put in 2 you get the terrible squiggly line (which you
> can always turn off with a right-click, ignore all).
> 
> The argument for single space is the font handles inter-sentence spacing
> just fine as mono-spacing went out with the typewriter....

This debate is a recurring one.  Opinions vary.

IMO:

 - Two spaces after sentence-ending periods function as markup that
   distinguishes from non-sentence-ending periods and avoids the need
   for either explicit markup or sentence-ending heuristics.

   Editors should let me type two spaces to end sentences because that's
   a damned common thing to do.  They can turn it into something else, I
   don't care, as long as the intended purpose is served.

 - Rendering such '.  ' as . and a wider space is perfectly fine and
   desirable.

> I wonder what it does if your font IS mono-space?

I hope you get two spaces after the sentence-ending period.  Anything
else would be a bug.

Anyways, prepare for this to turn into a bit of a flame war, or for it
to end with a reference to past ones.

Nico
--