From owner-cvs-doc@FreeBSD.ORG Thu Oct 13 12:01:58 2011 Return-Path: Delivered-To: cvs-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56F351065689; Thu, 13 Oct 2011 12:01:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 163948FC19; Thu, 13 Oct 2011 12:01:58 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id BC05546B3C; Thu, 13 Oct 2011 08:01:57 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5AF008A02F; Thu, 13 Oct 2011 08:01:57 -0400 (EDT) From: John Baldwin To: Ulrich =?utf-8?q?Sp=C3=B6rlein?= Date: Thu, 13 Oct 2011 08:01:54 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <201110101729.p9AHTQg7030262@repoman.freebsd.org> <4E9598FD.2010801@FreeBSD.org> <20111012164101.GI26743@acme.spoerlein.net> In-Reply-To: <20111012164101.GI26743@acme.spoerlein.net> MIME-Version: 1.0 Message-Id: <201110130801.54886.jhb@freebsd.org> Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Thu, 13 Oct 2011 08:01:57 -0400 (EDT) Cc: Glen Barber , Niclas Zeising , doc-committers@freebsd.org, cvs-doc@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/bsdinstall chapter.sgml X-BeenThere: cvs-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the doc and www trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2011 12:01:58 -0000 On Wednesday, October 12, 2011 12:41:01 pm Ulrich Sp=C3=B6rlein wrote: > On Wed, 2011-10-12 at 09:41:17 -0400, Glen Barber wrote: > > On 10/12/11 9:37 AM, Niclas Zeising wrote: > > > On 10/12/11 15:31, Glen Barber wrote: > > >> On 10/12/11 9:27 AM, Ulrich Sp=C3=B6rlein wrote: > > >>> On Mon, 2011-10-10 at 17:29:26 +0000, Glen Barber wrote: > > >>>> gjb 2011-10-10 17:29:26 UTC > > >>>> > > >>>> FreeBSD doc repository > > >>>> > > >>>> Modified files: > > >>>> en_US.ISO8859-1/books/handbook/bsdinstall chapter.sgml > > >>>> Log: > > >>>> Use two spaces between end of sentence and beginning of sentenc= e. > > >>>> > > >>>> Revision Changes Path > > >>>> 1.9 +10 -10 =20 > > >>>> doc/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml > > >>> > > >>> Why oh why? Please stop doing that, it's pointless, annoying and wi= ll > > >>> get lost with paragraph reformatting eventually and is not signific= ant > > >>> in the generated output. > > >>> > > >> > > >> It follows the FDP standards as noted directly before Chapter 10.1 h= ere: > > >> > > >> http://www.freebsd.org/doc/en/books/fdp-primer/writing-style.html > > >> > > >=20 > > > From what I've come to understand it does not matter for the rendered > > > output.=20 > >=20 > > The only "significant" spaces in SGML/HTML output is " ". > >=20 > > > It makes the source (i.e. sgml file) more readable though. > >=20 > > In addition to being "proper" writing style. >=20 > Yes, the 20th century called and wants you to return your typewriter. >=20 > Please stop this double-spaced end of sentence madness. > http://www.slate.com/articles/technology/technology/2011/01/space_invader= s.html I don't know about you, but due to the significance of whitespace indentati= on in most of the stuff I work on (code, etc.), I almost exclusively use monospace fonts and not proportional space fonts (on the system console you have no choice in that matter, you are forced to use monospace). In that environment the double space does make sense (as the article you quoted notes). Part of the goal of a style guide is so that code (or documentation) uses a consistent style so that anyone in the group can easily work with it. Yes, it may not suit your personal style to conform to the group's agreed-upon guidelines, but it is better for the overall project if you do. I know that style(9) was not my preferred style when I first became a committer, but rather than fighting for something like a four-space indent I (mostly) conformed to the existing style instead (with a lot of help from bde). I think having a consistent style is important, and that with the volume of existing documentation that already uses double spaces, we should just stick with that. =2D-=20 John Baldwin