Date: Tue, 20 Jul 2004 14:32:11 +0000 From: Murray Stokely <murray@FreeBSD.org> To: Marc Fonvieille <blackend@freebsd.org> Cc: doc@freebsd.org Subject: Re: Creating an Admin Handbook Message-ID: <20040720143211.GC17260@hub.freebsd.org> In-Reply-To: <20040720140759.GA69951@abigail.blackend.org> References: <20040719100354.GA90972@hub.freebsd.org> <20040720103432.GA64597@clan.nothing-going-on.org> <20040720104501.GB5405@hub.freebsd.org> <20040720124337.GA8096@electra.cse.Buffalo.EDU> <20040720140759.GA69951@abigail.blackend.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 20, 2004 at 04:07:59PM +0200, Marc Fonvieille wrote: > For the moment > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ > gives an "overview" of Handbook sections/chapters, if after the split(s) > the Handbook keeps a similar ToC it will be fine, otherwise we will > loose a part of the Handbook strengths. > > Well this is "my personal opinion", and of course I see some advantages > in the split, it's why I did not say "No" to the split. I say "Ok but be > careful" :) It would be nice to have a shared table of contents for the online version with : Volume I : User Handbook * Chapter 1 : Introduction * Chapter 2 : Installation ... * Appendix D Volume II : Admin Handbook * Chapter 1 ... We could create something like this with a Perl script during the web build pretty easily. Eventually we would want to do this with olinks and <books> in a single <set> element. - Murray
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040720143211.GC17260>