Date: Wed, 10 Jan 2001 13:39:53 -0800 From: bmah@freebsd.org (Bruce A. Mah) To: Nik Clayton <nik@freebsd.org> Cc: "Bruce A. Mah" <bmah@freebsd.org>, doc@freebsd.org Subject: Re: Version specific documentation Message-ID: <200101102139.f0ALdsh06635@bmah-freebsd-0.cisco.com> In-Reply-To: <20010110161524.G93855@canyon.nothing-going-on.org> References: <20001221135340.B61525@canyon.nothing-going-on.org> <200012281823.eBSINeV06392@bmah-freebsd-0.cisco.com> <20010110161524.G93855@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_1191007459P Content-Type: text/plain; charset=us-ascii If memory serves me right, Nik Clayton wrote: > On Thu, Dec 28, 2000 at 10:23:40AM -0800, Bruce A. Mah wrote: > > A dumb DocBook newbie question: I can see where this gives much more > > flexibility than using marked sections. I'm still using marked sections > > for the DocBook-ified Release Notes I'm working on (which I'm going to > > start calling RELNOTESng just to be cute). Since there is no ordering > > on the types of machines we support, is there any point in my trying to > > hack up something similar for supporting multiple architectures, rather > > than using marked sections? > > How much overlap is there likely to be between different architectural > versions of the release notes? It's certainly possible. DocBook > already has an 'arch' attribute on most elements, so you could write > something like > > <para arch="i386 alpha">...</para> > > and the stylesheets could do something with it. Essentially, this would > be identical to the code I still have to write to support an osversionin > attribute. Errr. Does this mean that an arch= attribute is now supported but it doesn't handle multiple architectures? To answer your question I'd say that overlap is much more likely once we support more than 2 architectures. > > Dumb other question, returning to your original idea: So is the idea > > that one would edit freebsd.dsl to produce a document for different > > versions of FreeBSD, rather than having to edit the source document? > > Yes (and no. . .) > > > Any way of specifying this at build time? > > Yes (and no. . .) :-) > > Depends on the processor you're using. Jade doesn't support it, all it > lets you do is set previously unset values. However, OpenJade lets you > assign values on the command line. I just discovered OpenJade, thanks to your doc/ commit to make OpenJade generate the navigation menu for Acrobat. Do we have a preference for using jade vs. openjade? Thanks! Bruce. --==_Exmh_1191007459P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: Exmh version 2.2 06/23/2000 iD8DBQE6XNap2MoxcVugUsMRAmF1AKCwtiLjsbWwnysGyG1dv7zlTk+w2gCg+azn wOQSTjABLnGNZGQXhYh+cgg= =Mjne -----END PGP SIGNATURE----- --==_Exmh_1191007459P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101102139.f0ALdsh06635>