From owner-freebsd-doc@FreeBSD.ORG Fri Sep 12 03:33:36 2003 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4042E16A4BF for ; Fri, 12 Sep 2003 03:33:36 -0700 (PDT) Received: from arthur.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3493443FE9 for ; Fri, 12 Sep 2003 03:33:35 -0700 (PDT) (envelope-from simon@arthur.nitro.dk) Received: by arthur.nitro.dk (Postfix, from userid 1000) id 1856710BFAA; Fri, 12 Sep 2003 12:33:33 +0200 (CEST) Date: Fri, 12 Sep 2003 12:33:33 +0200 From: "Simon L. Nielsen" To: Ceri Davies , Christian Brueffer , freebsd-doc@freebsd.org Message-ID: <20030912103331.GA388@FreeBSD.org> References: <200309120920.h8C9KGZ8091585@freefall.freebsd.org> <20030912093107.GH635@unixpages.org> <20030912093846.GK76802@submonkey.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline In-Reply-To: <20030912093846.GK76802@submonkey.net> User-Agent: Mutt/1.5.4i Subject: Re: docs/56729: [patch] artciles/pr-guidelines: explain meaning of MFC X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 10:33:36 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2003.09.12 10:38:46 +0100, Ceri Davies wrote: > On Fri, Sep 12, 2003 at 11:31:08AM +0200, Christian Brueffer wrote: > > On Fri, Sep 12, 2003 at 02:20:16AM -0700, Ceri Davies wrote: > > > > > > > This is already covered in the FAQ. I think if anything, a link = should > > > > suffice. > > > =20 > > > I agree that it doesn't need to be duplicated in that article (else = we'd be > > > pretty much doing it in every article). > > > =20 > > > Perhaps we should have a FreeBSD glossary, where all relevant acrony= ms and > > > terms are explained. This could then be easily included at the end = of > > > printed works, etc. I'd be prepared to make a start on it, but I'd = need > > > help for sure. > >=20 > > Good idea, I'd also like to see something like this. I'm not very fami= liar > > with the docbook infrastructure, what would be the best way to implemen= t it? >=20 > I'm not sure yet. Doubtless there is already a method for doing it, but > I'll need to check what the relevant elements, etc. are when I get home. I also think this is a good idea. As for doing it, I would look at how the bookinfo.legalnotice entity is defined. Basically : The file doc/en_US.ISO8859-1/share/sgml/bookinfo.ent contains : And then doc/en_US.ISO8859-1/share/sgml/legalnotice.sgml is the actual text which is just included using "&bookinfo.legalnotice;". I think it would be fairly simple to do something like this for a glossary. --=20 Simon L. Nielsen FreeBSD Documentation Team --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/YaD7h9pcDSc1mlERAnMlAJ9+tOX5wA6OF7t0cG2JTlpAsB9k9gCcCIAI BznYjfwTBg4ZtIzUw9K821w= =dpUM -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5--