From owner-cvs-doc@FreeBSD.ORG Wed Oct 12 21:11:55 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 B2F5E106567F; Wed, 12 Oct 2011 21:11:55 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper-int.allbsd.org [IPv6:2001:2f0:104:e002::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8428FC17; Wed, 12 Oct 2011 21:11:54 +0000 (UTC) Received: from alph.allbsd.org (p1143-ipbf704funabasi.chiba.ocn.ne.jp [122.25.220.143]) (authenticated bits=128) by mail.allbsd.org (8.14.4/8.14.4) with ESMTP id p9CLBKt1070785; Thu, 13 Oct 2011 06:11:30 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.allbsd.org (8.14.4/8.14.4) with ESMTP id p9CLBHFd006157; Thu, 13 Oct 2011 06:11:20 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Thu, 13 Oct 2011 06:11:05 +0900 (JST) Message-Id: <20111013.061105.428603913885751921.hrs@allbsd.org> To: uqs@spoerlein.net, bcr@FreeBSD.org From: Hiroki Sato In-Reply-To: <4E95CA78.6040503@FreeBSD.org> References: <4E9598FD.2010801@FreeBSD.org> <20111012164101.GI26743@acme.spoerlein.net> <4E95CA78.6040503@FreeBSD.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.3.51 on Emacs 23.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Thu_Oct_13_06_11_05_2011_513)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.allbsd.org [133.31.130.32]); Thu, 13 Oct 2011 06:11:36 +0900 (JST) X-Spam-Status: No, score=-100.8 required=13.0 tests=BAYES_00, CONTENT_TYPE_PRESENT,RCVD_IN_PBL,RCVD_IN_RP_RNBL,SPF_SOFTFAIL, USER_IN_WHITELIST autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on gatekeeper.allbsd.org Cc: niclas.zeising@gmail.com, cvs-doc@FreeBSD.org, doceng@FreeBSD.org, cvs-all@FreeBSD.org, gjb@FreeBSD.org, doc-committers@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: Wed, 12 Oct 2011 21:11:55 -0000 ----Security_Multipart(Thu_Oct_13_06_11_05_2011_513)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Benedict Reuschling wrote in <4E95CA78.6040503@FreeBSD.org>: bc> I propose that once we decide to use just one single space in the bc> future, that new documents which are added to the doc tree should use bc> this new convention, but old documents should not be changed. This bc> reduces the amount of work for translators immensely. PRs that are being bc> filed with sweeping doc patches to correct this in old documents should bc> also be closed with a reference to the policy. bc> bc> Your thoughts on this? While I have personally used the double-spacing for a long time, in my understanding, innovations in publishing made the double-spacing obsolete and most of English style guides currently opt for the single-spacing for published work. I do not remember the reason why this rule is included in our FDP Primer, but I think it is for readability when editing a source file with monospaced fonts. It is not for the rendered result obviously as many already pointed out it. Thus, whether keeping the double-spacing policy or not is a matter of our preference. We need consistency on that, however. I have no strong (objective) opinion on sticking to the current policy, but the fact that we already have a lot of sentences with the double-spacing are tempting me into not changing it. I think neither converting the existing documents to single-spaced nor adopting a policy of "single-spaced for new docs, keeping old documents double-spaced" sounds a reasonable option to us. -- Hiroki ----Security_Multipart(Thu_Oct_13_06_11_05_2011_513)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEABECAAYFAk6WAmkACgkQTyzT2CeTzy1YSwCfWE5NfQai10pWJaFctZLkp8eZ 1ScAoIthHLkIGxba3XiTY8UbY4l5sRhy =2JFS -----END PGP SIGNATURE----- ----Security_Multipart(Thu_Oct_13_06_11_05_2011_513)----