Re: [Tools-discuss] [Cellar] non-ascii characters (fwd) Dave Rice: non-ascii characters

Carsten Bormann <cabo@tzi.org> Fri, 30 August 2019 08:00 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C12D6120113; Fri, 30 Aug 2019 01:00:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level:
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 Jpq7WfqmzGSq; Fri, 30 Aug 2019 01:00:11 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CA0712001A; Fri, 30 Aug 2019 01:00:11 -0700 (PDT)
Received: from [192.168.217.110] (p548DCCB9.dip0.t-ipconnect.de [84.141.204.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46KX2d3Gg8zywt; Fri, 30 Aug 2019 10:00:09 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0ce8e099-0344-dacc-06b2-898fb63c75e5@gmx.de>
Date: Fri, 30 Aug 2019 10:00:09 +0200
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Tom Pusateri <pusateri=40bangj.com@dmarc.ietf.org>, cellar@ietf.org, Henrik Levkowetz <henrik@levkowetz.com>, tools-discuss <tools-discuss@ietf.org>
X-Mao-Original-Outgoing-Id: 588844807.490808-5087a3644267b470c833424d0152cb06
Content-Transfer-Encoding: quoted-printable
Message-Id: <6FF73116-59F3-453E-B001-171AF369A7E9@tzi.org>
References: <31591.1566930552@localhost> <c9f67a76-c0ae-6d3e-2bad-47dfdda85df6@levkowetz.com> <16112.1566934510@localhost> <5E85BF29-021D-4235-BD68-893F5729D5E6@bangj.com> <AB46FC1D-1FC9-4F3B-8DB9-0FF0E93A91CE@tzi.org> <4fa5f1ff-71f8-5303-e285-0e1f10e458c2@gmx.de> <76BBD514-2BB6-4291-B80F-4C72B17E43B4@tzi.org> <0ce8e099-0344-dacc-06b2-898fb63c75e5@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/8oM4g0Ls_xj9Ut4K37XLZnMLyjY>
Subject: Re: [Tools-discuss] [Cellar] non-ascii characters (fwd) Dave Rice: non-ascii characters
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Aug 2019 08:00:14 -0000

On Aug 30, 2019, at 09:39, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
>> I’m not aware of an opportunity for that (well, maybe except for the choice between en-dashes and em-dashes for the punctuation mark in the form of a horizontal line used to indicate a pause, to delimit an inserted sentence or phrase, or to indicate a deliberately omitted word).    But given that this is the IETF, I’m sure we’ll find one :-)
> 
> AFAIR, there are also different opinions about whether there should be
> whitespace around it.

Right.

Traditional German: em-dash with whitespace
“Modern” German: en-dash with whitespace
Traditional US English: em-dash without whitespace, or sometimes with (AP style, i.e., news)
Traditional UK English: it’s complicated
Today’s English: hodgepodge
Laypeople: essentially, use dashes only where Microsoft Word turns a hyphen into a dash automatically, and that involves typing spaces, or so

(And, of course, there are range and versus dashes as well, which are always en-dashes, but might incomprehensibly have whitespace in English.)

I don’t have my CMOS with me, or I would cite chapter and verse.
But the important observation is that this is a well-known editorial style issue to which a copy-editor should have an answer.

More generally speaking, the fact that Unicode has more characters does not mean we need to spend a lot of time deciding which character to use.  I think we are also old enough to no longer fall into Unicode traps (e.g., Ω vs. Ω).

Grüße, Carsten