From owner-freebsd-doc Wed Mar 20 7:48:32 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mired.org (dsl-64-192-6-133.telocity.com [64.192.6.133]) by hub.freebsd.org (Postfix) with SMTP id 8523237B405 for ; Wed, 20 Mar 2002 07:48:21 -0800 (PST) Received: (qmail 5942 invoked by uid 100); 20 Mar 2002 15:48:20 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15512.44867.930654.886921@guru.mired.org> Date: Wed, 20 Mar 2002 09:48:19 -0600 To: Tom Rhodes Cc: swear@blarg.net, freebsd-doc@FreeBSD.ORG Subject: Re: docs/36042: [PATCH] There's not a good description of shared builds in the handbook In-Reply-To: <20020320000727.284a00c1.darklogik@pittgoth.com> References: <200203192120.g2JLK3o17280@freefall.freebsd.org> <15512.3992.905972.279159@guru.mired.org> <20020320000727.284a00c1.darklogik@pittgoth.com> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.49 (Python 2.2 on freebsd4) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In <20020320000727.284a00c1.darklogik@pittgoth.com>, Tom Rhodes typed: > On Tue, 19 Mar 2002 22:27:04 -0600 > Mike Meyer wrote: > > > In , Gary W. Swearingen typed: > > > Mike Meyer writes: > > > > In <20020319100000.A57951@sumuk.de>, Martin Heinen typed: > > > > > Please put two spaces at the end of sentences. > > You're saying he wants the raw text formatted the way he would like to > > read it. Personally, I disagree with you and prefer one space after a > > period, even in fixed pitch text. That's why I wrote it that way. > To be honest, in high school and college english I have always been > taught to use two spaces at the end of any typed sentance, so I > think its a set standard. I'm open to hearing any educated > arguments on this though, not that it would make my life easier, but > at least i'd have an argument to mr I-know-it-all teacher hehe... Speaking of following standards, rfc 2822 says that lines in email messages "SHOULD" be at most 78 characters long. Yours were ~160. I for one would appreciate that standard being followed. Here's the story as I recall it. I've probably got some of it wrong. In the beginning, all fonts had variable width characters, and typesetters used an n-space after words, and an m-space after sentences. When fonts with fixed-width characters were introduced - via typewriters - *some* of the users decided that the m-space after a sentence deserved two spaces. Others kept right on using a single m-space after sentences, even though they were the same width as the n-spaces after words. As you can see, this distinction only matters if you're setting something in fixed width fonts, and even then there isn't universal agreement about it. Bringhurst, in "The Elements of typographic style", calls the double-space practice an "abomination", or words to that effect. As far as I'm concerned, when it comes to typography, that's the bible - which I suppose makes Bringhurst God. Now, if this is something we do to make life easier for programs, that I can understand. In which case, I'd very much like to have -- be turned into m-dashes and - into n-dashes, so we can do away with —. I'm even willing to do the work, if someone can point out what code is interpreting '. ' to mean something different than '. '. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message