From owner-cvs-doc@FreeBSD.ORG Tue Jan 5 18:19:09 2010 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 438811065679; Tue, 5 Jan 2010 18:19:09 +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 6E9028FC1C; Tue, 5 Jan 2010 18:19:08 +0000 (UTC) Received: from delta.allbsd.org (p3177-ipbf416funabasi.chiba.ocn.ne.jp [123.225.92.177]) (authenticated bits=128) by mail.allbsd.org (8.14.3/8.14.3) with ESMTP id o05IInxo047229; Wed, 6 Jan 2010 03:19:00 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id o05IIktH001126; Wed, 6 Jan 2010 03:18:48 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 06 Jan 2010 03:17:20 +0900 (JST) Message-Id: <20100106.031720.188809664.hrs@allbsd.org> To: rene@FreeBSD.org From: Hiroki Sato In-Reply-To: <4B437B44.9060308@freebsd.org> References: <4B425D7A.7030101@FreeBSD.org> <4B437B44.9060308@freebsd.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Jan__6_03_17_20_2010_719)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.95.3 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]); Wed, 06 Jan 2010 03:19:03 +0900 (JST) X-Spam-Status: No, score=-4.1 required=13.0 tests=AWL,BAYES_00, CONTENT_TYPE_PRESENT, SPF_SOFTFAIL, X_MAILER_PRESENT autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gatekeeper.allbsd.org Cc: dougb@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org, gavin@FreeBSD.org, gabor@FreeBSD.org, doc-committers@FreeBSD.org Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/porters-handbook book.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: Tue, 05 Jan 2010 18:19:09 -0000 ----Security_Multipart(Wed_Jan__6_03_17_20_2010_719)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Rene Ladan wrote in <4B437B44.9060308@freebsd.org>: re> On 04-01-2010 22:28, Doug Barton wrote: re> > Gavin Atkinson wrote: re> >> On Mon, 4 Jan 2010, Doug Barton wrote: re> >>> dougb 2010-01-04 20:38:15 UTC re> >>> re> >>> Modified files: re> >>> en_US.ISO8859-1/books/porters-handbook book.sgml re> >>> Log: re> >>> Actually having the $FreeBSD$ tag expanded in the example rc.d script re> >>> did not end up looking as cool as I thought it would, so switch to an re> >>> unexpanded example. re> >>> re> >>> Fix the text in the new paragraph to work better around the markup. re> >> re> >>> Unless there is a good reason to start the service re> >>> earlier all ports scripts should use re> >>> - REQUIRE: LOGIN. If the service re> >>> + REQUIRE: LOGIN If the service re> >>> runs as a particular user (other than root) this is mandatory. re> >> re> >> This is now grammatically incorrect. I actually think the original is re> >> better than any rewording I can come up with. re> > re> > Take a quick look at the page before it auto-updates. The old way the re> > period ends up all by itself in the text after the programlisting box, re> > so it looks like this: re> > re> > . If the service re> > re> This feels like working around some bug/shortcoming in the markup re> engine to me (?) The source text never knows the dimensions and font re> of the resulting output (computer screen/paper/pda/...). I guess the original version was intended to use an inline format, not a displayed block. If it is true, should be used instead of here. Or if a displayed block was preferred, the sentence should be fixed as Gabor suggested. DocBook specification claims "processing expectations" for each element, not only semantics of the markup. The structure like "This is foo. That is bar." is allowed in the spec but should be avoid because it leads to an odd output. -- Hiroki ----Security_Multipart(Wed_Jan__6_03_17_20_2010_719)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAktDgjAACgkQTyzT2CeTzy1spgCdFfYOvSJSb6NU/Bk+87ysKa3O psQAn0mRaTdcVGhksV96DZEeb8Vkreg5 =JDQC -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Jan__6_03_17_20_2010_719)----