Re: RFC 2119 terms, ALL CAPS vs lower case
Tony Finch <dot@dotat.at> Thu, 17 May 2012 10:54 UTC
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 475A821F85E1 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 03:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.229
X-Spam-Level:
X-Spam-Status: No, score=-5.229 tagged_above=-999 required=5 tests=[AWL=-1.230, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YL1bSbMSTon5 for <ietf@ietfa.amsl.com>; Thu, 17 May 2012 03:54:08 -0700 (PDT)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB2921F85D9 for <ietf@ietf.org>; Thu, 17 May 2012 03:54:07 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:36584) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1SUyLO-000700-r2 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 17 May 2012 11:54:06 +0100
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1SUyLO-0002VF-Cu (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 17 May 2012 11:54:06 +0100
Date: Thu, 17 May 2012 11:54:06 +0100
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: RFC 2119 terms, ALL CAPS vs lower case
In-Reply-To: <20120516145655.GH26714@mail.yitter.info>
Message-ID: <alpine.LSU.2.00.1205171142220.32614@hermes-2.csi.cam.ac.uk>
References: <562A61B995B24BD854A4D154@[192.168.0.2]> <4FB3B6E0.2070506@dcrocker.net> <20120516145655.GH26714@mail.yitter.info>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="1870870024-1741023179-1337252046=:32614"
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2012 10:54:09 -0000
Andrew Sullivan <ajs@anvilwalrusden.com> wrote: > On Wed, May 16, 2012 at 07:17:04AM -0700, Dave Crocker wrote: > > Case does not define meaning in normal language, why should it here? > > That is false. Consider these two passages: > > The King asked the Queen, > and the Queen asked the dairy-maid … > > vs > > The king asked the queen, > and the queen asked the dairy-maid… I really can't tell any difference between the two. The capitalization here is just a conventional mark of respect (cf. God). Better examples: Polish / polish "I helped my uncle Jack off a horse" Catholic / catholic Conservative / conservative In the latter two cases you often get disambiguating circumlocutions (such as "conservative with a small c" in British political discussion) so even if you can use case to make a distinction in meaning, it's usually too subtle to rely on if you want to avoid "amusing" misinterpretations. Tony. -- f.anthony.n.finch <dot@dotat.at> http://dotat.at/ Humber, Thames: South or southwest 3 or 4, backing east 4 or 5 later. Slight or moderate. Mainly fair. Mainly good.
- RFC 2119 terms, ALL CAPS vs lower case Barry Leiba
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Scott Kitterman
- Re: RFC 2119 terms, ALL CAPS vs lower case Edward Lewis
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- RE: RFC 2119 terms, ALL CAPS vs lower case Adrian Farrel
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Andrew Sullivan
- Re: RFC 2119 terms, ALL CAPS vs lower case Simon Perreault
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Sam Hartman
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case Peter Saint-Andre
- Re: RFC 2119 terms, ALL CAPS vs lower case Mary Barnes
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Ole Jacobsen
- Re: RFC 2119 terms, ALL CAPS vs lower case Peter Saint-Andre
- RE: RFC 2119 terms, ALL CAPS vs lower case Adrian Farrel
- Re: RFC 2119 terms, ALL CAPS vs lower case Ole Jacobsen
- RE: RFC 2119 terms, ALL CAPS vs lower case John C Klensin
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- RE: RFC 2119 terms, ALL CAPS vs lower case Worley, Dale R (Dale)
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Cridland
- Re: [IETF] RE: RFC 2119 terms, ALL CAPS vs lower … Warren Kumari
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Dave Crocker
- Re: RFC 2119 terms, ALL CAPS vs lower case Jaap Akkerhuis
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Doug Barton
- Re: RFC 2119 terms, ALL CAPS vs lower case t.p.
- Re: RFC 2119 terms, ALL CAPS vs lower case Tony Finch
- Re: RFC 2119 terms, ALL CAPS vs lower case Tony Finch
- Re: RFC 2119 terms, ALL CAPS vs lower case Julian Reschke
- RE: RFC 2119 terms, ALL CAPS vs lower case Lee Howard
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case Marshall Eubanks
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Marshall Eubanks
- Re: RFC 2119 terms, ALL CAPS vs lower case Eric Rosen
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case ned+ietf
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Ralph Droms
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- Re: RFC 2119 terms, ALL CAPS vs lower case Carsten Bormann
- Re: RFC 2119 terms, ALL CAPS vs lower case Ofer Inbar
- Re: RFC 2119 terms, ALL CAPS vs lower case Eliot Lear
- Re: RFC 2119 terms, ALL CAPS vs lower case Randy Bush
- RE: RFC 2119 terms, ALL CAPS vs lower case Yaakov Stein
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Bill McQuillan
- Re: RFC 2119 terms, ALL CAPS vs lower case Stephen Farrell
- Re: RFC 2119 terms, ALL CAPS vs lower case Hector Santos
- Re: RFC 2119 terms, ALL CAPS vs lower case John C Klensin
- Re: RFC 2119 terms, ALL CAPS vs lower case Brian E Carpenter
- Re: RFC 2119 terms, ALL CAPS vs lower case Stephane Bortzmeyer
- Re: RFC 2119 terms, ALL CAPS vs lower case Marc Petit-Huguenin
- Re: RFC 2119 terms, ALL CAPS vs lower case Yoav Nir
- Re: RFC 2119 terms, ALL CAPS vs lower case Abdussalam Baryun