Date: Thu, 13 Oct 2011 06:11:05 +0900 (JST) From: Hiroki Sato <hrs@FreeBSD.org> To: uqs@spoerlein.net, bcr@FreeBSD.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 Message-ID: <20111013.061105.428603913885751921.hrs@allbsd.org> In-Reply-To: <4E95CA78.6040503@FreeBSD.org> References: <4E9598FD.2010801@FreeBSD.org> <20111012164101.GI26743@acme.spoerlein.net> <4E95CA78.6040503@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
----Security_Multipart(Thu_Oct_13_06_11_05_2011_513)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Benedict Reuschling <bcr@FreeBSD.org> 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)----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111013.061105.428603913885751921.hrs>