From owner-freebsd-doc  Tue Dec 21 12:54:13 1999
Delivered-To: freebsd-doc@freebsd.org
Received: from cnri.reston.va.us (ns.CNRI.Reston.VA.US [132.151.1.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9EBA815090
	for <doc@freebsd.org>; Tue, 21 Dec 1999 12:54:04 -0800 (PST)
	(envelope-from fdrake@weyr.cnri.reston.va.us)
Received: from weyr.cnri.reston.va.us (weyr [132.151.1.174])
	by cnri.reston.va.us (8.9.1a/8.9.1) with ESMTP id PAA15190;
	Tue, 21 Dec 1999 15:52:57 -0500 (EST)
Received: (from fdrake@localhost)
	by weyr.cnri.reston.va.us (8.9.1b+Sun/8.9.1) id PAA26401;
	Tue, 21 Dec 1999 15:53:34 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14431.59598.635029.702475@weyr.cnri.reston.va.us>
Date: Tue, 21 Dec 1999 15:53:34 -0500 (EST)
To: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl>
Cc: docbook@lists.oasis-open.org, bortzmeyer@debian.org,
	doc@freebsd.org, sgml-tools@via.ecp.fr, dssslist@mulberrytech.com,
	oswg-discuss@oswg.org
Subject: Re: DOCBOOK: Including OS Version information on DocBook elements
In-Reply-To: <19991221195425.C50448@daemon.ninth-circle.org>
References: <19991221122224.B75275@catkin.nothing-going-on.org>
	<14431.46583.222301.132344@weyr.cnri.reston.va.us>
	<19991221195425.C50448@daemon.ninth-circle.org>
X-Mailer: VM 6.75 under 21.1 (patch 6) "Big Bend" XEmacs Lucid
From: "Fred L. Drake, Jr." <fdrake@acm.org>
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Jeroen Ruigrok/Asmodai writes:
 > Did I sound confused enough? ;)

  Wow!  ;-)

 > How will we make sure the version get their relevant info to make those
 > decisions about what to include or not?
 >
 > Nik's solution involved a Makefile system with scripts.  With the above
 > I reckon you want to integrate it into DSSSL or relevant tools?

  I don't think my suggestion had anything at all to do with tools.
Whether someone wants to do the DSSSL/XSL footwork to implement this
sort of versioning or use a Python script is entirely up to them.  The
notion of "current version" and version ranges just seems much more
general than only interesting for operating systems.  If I build a
large piece of software (say, a programming language), I might want to 
be able to maintain the documentation for multiple versions.  Some
text may apply to version <= X, and other text to version > X, but
other changes are simply to fix typos or other errors, and are not
version specific in any way.  If I can then regenerate the formatted
documentation for, say, the last three versions, that would certainly
be useful for users who aren't upgrading for whatever reason.


  -Fred

--
Fred L. Drake, Jr.	  <fdrake at acm.org>
Corporation for National Research Initiatives


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message