From owner-freebsd-doc@FreeBSD.ORG Mon Dec 6 21:50:39 2004 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 3580316A4CE for ; Mon, 6 Dec 2004 21:50:39 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB89E43D41 for ; Mon, 6 Dec 2004 21:50:38 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 489D2B7; Mon, 6 Dec 2004 15:50:38 -0600 (CST) Date: Mon, 6 Dec 2004 15:50:38 -0600 From: Tillman Hodgson To: doc@freebsd.org Message-ID: <20041206215038.GM569@seekingfire.com> References: <20041205114254.GD23252@clan.nothing-going-on.org> <41B3617B.3080507@centtech.com> <20041206192017.GE72462@clan.nothing-going-on.org> <20041206212357.GE84191@freebsdmall.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041206212357.GE84191@freebsdmall.com> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: Re: Time for a Network Handbook? 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: Mon, 06 Dec 2004 21:50:39 -0000 On Mon, Dec 06, 2004 at 01:23:57PM -0800, Murray Stokely wrote: > One thing we should think about is using link entities to allow the > different chapters to be included in different books without breaking > the build due to broken references. Currently, the single-chapter > builds often fail because xrefs to other chapters can not be looked > up. If we replaced all xrefs to other chapters with entities like: > > &link.chapter.sect; > > Then we could define that entity depending on the presence of the -i > parameter entity for the given chapter file. If the chapter to be > linked to is included in the build (and it's -i entity defined), then > the is created. If it is not included in the build, then > descriptive text is used instead 'The Blah Chapter in the Handbook'. Fixing single-chapter builds would be great. Alternatively, Tillman could get faster hardware. But since I'd much rather collect old hardware[1] than new hardware, that's not likely ;-) > In this way, we could more easily move chapters around between books > without having to update all of the cross-chapter references. If it's done in a one-by-one fashion that would be important. > This would also allow us to easily maintain a full version of the > Handbook that includes all of the chapters, in addition to the split > off 'network handbook', 'admin handbook', etc. It's a stop-gap until > we get proper olink support, basically. I like that. -T 1. http://www.seekingfire.com/projects/e3hardware/ -- If enlightenment is not where you are standing, where will you look? - Zen saying