Re: [xml2rfc] Word enforcing 1 space between sentences

Robert Moskowitz <rgm@htt-consult.com> Thu, 30 April 2020 20:07 UTC

Return-Path: <rgm@htt-consult.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 33DEF3A1254 for <xml2rfc@ietfa.amsl.com>; Thu, 30 Apr 2020 13:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 KYz2EkzwkuQz for <xml2rfc@ietfa.amsl.com>; Thu, 30 Apr 2020 13:07:19 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 803A33A124F for <xml2rfc@ietf.org>; Thu, 30 Apr 2020 13:07:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id B7A526212C; Thu, 30 Apr 2020 16:07:17 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id fO-V3qpYwQNq; Thu, 30 Apr 2020 16:07:12 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id BEA156211C; Thu, 30 Apr 2020 16:07:12 -0400 (EDT)
To: Nico Williams <nico@cryptonector.com>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <555f5ab1-a3a0-7710-0581-4d13bb641325@htt-consult.com> <20200430195655.GF18021@localhost>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <480d6039-59e3-a802-43ac-9089244ac7f6@htt-consult.com>
Date: Thu, 30 Apr 2020 16:07:08 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <20200430195655.GF18021@localhost>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/1qLky8gU11saWXWA4IVloVMt_rk>
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 20:07:21 -0000


On 4/30/20 3:56 PM, Nico Williams wrote:
> 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.

I had my typing class in '64 (9th grade US) on a Royal manual 
typewriter.  You had to type at 40WPM after corrections to pass.  I 
still have my typing style guide with lots of things not done today.  2 
spaces after a sentence is a small one!  My  wife and I occasionally 
argue (she came through the program 4 years later and they had already 
changed business letter layouts).

I use to write for Network Computing Magazine (back in the mid-90s).  My 
editor and I reached an agreement that I typed as I learned and she 
changed it to the Mag's style guide.  Made for a much better 
interaction.  Of course I was the acronym king of the writers and she 
had a struggle figuring out which to expand and which to leave to the 
readers as I had a 500w budget and typically hit it on the head.

So in large measure I care little what they are teaching today and what 
styles are being enforced.  I will write as I do and if some editor 
enforces a style guide, have at it.

Have a good day!