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

Dave Rice <dave@dericed.com> Sat, 31 August 2019 23:02 UTC

Return-Path: <dave@dericed.com>
X-Original-To: cellar@ietfa.amsl.com
Delivered-To: cellar@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B916512013A; Sat, 31 Aug 2019 16:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level:
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no 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 KXSNi6RH0bAK; Sat, 31 Aug 2019 16:02:18 -0700 (PDT)
Received: from server172-3.web-hosting.com (server172-3.web-hosting.com [68.65.122.111]) (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 0CDD61200FB; Sat, 31 Aug 2019 16:02:17 -0700 (PDT)
Received: from cpe-104-162-94-162.nyc.res.rr.com ([104.162.94.162]:39645 helo=[10.0.1.3]) by server172.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <dave@dericed.com>) id 1i4CNm-002sAI-RY; Sat, 31 Aug 2019 19:02:15 -0400
From: Dave Rice <dave@dericed.com>
Message-Id: <1671C432-1E43-41C4-99FC-B927887BBE12@dericed.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7E2F97F0-FC05-4443-9685-862EB0B80BB8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Sat, 31 Aug 2019 19:02:08 -0400
In-Reply-To: <6FF73116-59F3-453E-B001-171AF369A7E9@tzi.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, 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>
To: Carsten Bormann <cabo@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> <6FF73116-59F3-453E-B001-171AF369A7E9@tzi.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-OutGoing-Spam-Status: No, score=-2.9
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server172.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dericed.com
X-Get-Message-Sender-Via: server172.web-hosting.com: authenticated_id: dave@dericed.com
X-Authenticated-Sender: server172.web-hosting.com: dave@dericed.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/cellar/ktZLO4MgEgsljQWz2cya2UUBQ6M>
Subject: Re: [Cellar] [Tools-discuss] non-ascii characters (fwd) Dave Rice: non-ascii characters
X-BeenThere: cellar@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Codec Encoding for LossLess Archiving and Realtime transmission <cellar.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cellar>, <mailto:cellar-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cellar/>
List-Post: <mailto:cellar@ietf.org>
List-Help: <mailto:cellar-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cellar>, <mailto:cellar-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Aug 2019 23:02:20 -0000

Hi all,

> On Aug 30, 2019, at 4:00 AM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> 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. Ω).

Thanks very much for this discussion, based on this and also running idnits, I’ve created this pull request for the FFV1 draft, https://github.com/FFmpeg/FFV1/pull/158/files <https://github.com/FFmpeg/FFV1/pull/158/files>. Related to this discussion the pull request changes the unicode minus sign to an ascii hyphen and uses a "ceil(a)" and "floor(a)" function rather than using "⌈a⌉" and "⌊a⌋”. After this PR, it passes idnits with no errors, warnings, or comments.

Thanks much,
Dave Rice