From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 21 Dec 2001 21:05:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 21 Dec 2001 21:05:15 -0500 Received: from svr3.applink.net ([206.50.88.3]:2322 "EHLO svr3.applink.net") by vger.kernel.org with ESMTP id ; Fri, 21 Dec 2001 21:05:05 -0500 Message-Id: <200112220204.fBM24rSr022372@svr3.applink.net> Content-Type: text/plain; charset=US-ASCII From: Timothy Covell Reply-To: timothy.covell@ashavan.org To: World Domination Now! , Chris Ricker Subject: Re: Configure.help editorial policy Date: Fri, 21 Dec 2001 20:01:10 -0600 X-Mailer: KMail [version 1.3.2] In-Reply-To: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Friday 21 December 2001 14:24, Chris Ricker wrote: > On Fri, 21 Dec 2001, Timothy Covell wrote: > > On Friday 21 December 2001 13:12, David Weinehall wrote: > > [snip] > > > > > Whatever the choice ends up being, KB is always incorrect, unless you > > > intend to specify some strange formula where the number of bytes (B) > > > combined with the temperature in Kelvin (K) has anything to do with > > > things. > > > > > > > > > > > > /David Weinehall > > > > The way the metric prefixes work is that multiplicative prefixes are > > capitalized and divisional prefixes are in lower case. > > Nonsense. Some of what you're calling multiplicative prefixes (as if they > weren't *all* multiplicative ;-) are capitalized, and others are not. kilo > (10^3) is k, hecto (10^2) is h, and deca (10^1) is da, for example. See > for the > official guidelines (page 23 if you read English, and page 28 if you read > French). Dude, I don't know why you are being so pedantic on this. You pointed to the stupid exceptions instead of the norm. 100% of the negative power prefixes ARE lower case, and all of the positive power prefixes ARE UPPERCASE except those three stupid exceptions which you cited. Here, SI is being stupid. Uppercase is a GOOD IDEA (TM). And, NIST should fix this because the point of standards is to create logical consistancy so that people don't get into these stupid discussions. Finally, I'm an American, so that means if someone tells me to do something stupid, I tell them where they can shove it. > > More relevant to the whole Configure.help discussion, if you want to > pedantic, official SI guidelines also state on the same page that: > > "These SI prefixes refer strictly to powers of 10. They should not be used > to indicate powers of 2 (for example, one kilobit represents 1000 bits and > not 1024 bits)." And I already agreed to this, as have most of the others. > > later, > chris > -- timothy.covell@ashavan.org.