Date: Mon, 6 Dec 2004 17:22:24 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Tillman Hodgson <tillman@seekingfire.com> Cc: doc@FreeBSD.org Subject: Re: Time for a Network Handbook? Message-ID: <20041206172224.03a916cb@localhost> In-Reply-To: <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> <20041206215038.GM569@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 6 Dec 2004 15:50:38 -0600 Tillman Hodgson <tillman@seekingfire.com> wrote: > 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 <xref> 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. I'm working on it. -- Tom Rhodes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041206172224.03a916cb>