From owner-freebsd-questions@FreeBSD.ORG Thu Nov 15 05:01:40 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BAFDDD3 for ; Thu, 15 Nov 2012 05:01:40 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id DC3848FC15 for ; Thu, 15 Nov 2012 05:01:39 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id qAF51XYP086686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Nov 2012 21:01:34 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id qAF51X4Y086685; Wed, 14 Nov 2012 21:01:33 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA07257; Wed, 14 Nov 12 20:48:47 PST Date: Wed, 14 Nov 2012 20:48:29 -0800 From: perryh@pluto.rain.com (Perry Hutchison) To: bonomi@mail.r-bonomi.com Subject: Re: well, try here first... Message-Id: <50a4d68d.qkjphs18bGRIYrhE%perryh@pluto.rain.com> References: <201211140658.qAE6w2tT090220@mail.r-bonomi.com> In-Reply-To: <201211140658.qAE6w2tT090220@mail.r-bonomi.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd@edvax.de, freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2012 05:01:40 -0000 Robert Bonomi wrote: > > Date: Wed, 14 Nov 2012 05:48:48 +0100 > > From: Polytropon > > Subject: Re: well, try here first... > > > > On Tue, 13 Nov 2012 20:20:51 -0700, Chad Leigh Shire.Net LLC wrote: > > > > > > To be fair, a lot of the same rules exist for English. The > > > comma is not optional or left to preferences in English, > > > either. There are definite rules and it brings structure. > > > > That matches what I've learned in school, but it doesn't match > > realitiy anymore. :-) > > > > A famous thing is "comma in lists": Unlike German, where "and" > > substitutes a comma, in English it seems to be valid to put a > > comma infront of "and": > > In 'classic' English (as taught in the 60s and earlier), a comma > was _required_ before a trailing 'and' in a list of 3 or more > items, and forbidden if there were only two items. By the time I got to high school (mid-60's), the comma before 'and' (or 'or') in a list of three or more was being taught as optional. My junior-in-college daughter tells me it is still being taught that way today. She and I have each come to the conclusion that it should _not_ be considered optional, because omitting it can sometimes cause the last two items in the list to appear as one item (at least on a first reading -- and one should not need to read things a second time to understand the punctuation). Last I heard, we have the Associated Press to thank for this travesty, their style manual having been revised in the late 1950's or early 1960's to say something along the lines of "don't use a comma in that situation unless it's necessary for clarity." I suppose it may have had something to do with saving a fraction of a second of Teletype time, and a minuscule amount of space in a newspaper column (which could occasionally lengthen/shorten a story by an entire line), every time such a construct turned up in a news story. Neither column space nor Teletype time was exactly inexpensive back then. > The accepted 'rules' changed about the time "new math" was foisted > on the world. The most visible ones involved comma placement, and > punctuation inside trailing quotes. > > The password is "frodo." > It is 5 characters long. > > The password is "frodo." > It is 6 characters long. > > BAH, HUMBUG!!! > > Make the first one: > The password is "frodo". > and all the ambiguity goes away. <*snarl*> I think the AP may have been behind this one too, although I don't see how the rationalization could have involved either space or transmission time. Meanwhile, a question mark or exclamation point in the same circumstances is supposed to be placed inside _or_ outside the closing quotation mark, depending on whether or not it is part of the material being quoted. IMO it makes more sense to apply that same rule to periods and commas also.