Return-Path: 
 <forrest-dev-return-3952-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 54673 invoked by uid 500); 3 Dec 2002 09:45:45 -0000
Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:forrest-dev-help@xml.apache.org>
list-unsubscribe: <mailto:forrest-dev-unsubscribe@xml.apache.org>
list-post: <mailto:forrest-dev@xml.apache.org>
Reply-To: forrest-dev@xml.apache.org
Delivered-To: mailing list forrest-dev@xml.apache.org
Received: (qmail 54641 invoked from network); 3 Dec 2002 09:45:44 -0000
Received: from smtp3.ihug.com.au (203.109.250.76)
  by daedalus.apache.org with SMTP; 3 Dec 2002 09:45:44 -0000
Received: from p733-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.142.225]
	by smtp3.ihug.com.au with esmtp (Exim 3.22 #1 (Debian))
	id 18J9co-0007Xj-00; Tue, 03 Dec 2002 20:45:55 +1100
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 18J9Ig-0002ab-00
	for <forrest-dev@xml.apache.org>; Tue, 03 Dec 2002 20:25:06 +1100
Date: Tue, 3 Dec 2002 20:24:46 +1100
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: Getting off of Stylebook
Message-ID: <20021203092446.GA3501@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <01d301c294e2$810f79b0$0a00a8c0@boo>
 <200211261141.31283.peter@realityforge.org> <3DE32207.1000607@apache.org>
 <037101c295ac$30a70180$0a00a8c0@boo>
 <20021127011329.GA464@expresso.localdomain>
 <026001c29a54$33d9fe50$0a00a8c0@boo>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <026001c29a54$33d9fe50$0a00a8c0@boo>
User-Agent: Mutt/1.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Mon, Dec 02, 2002 at 02:43:15PM -0800, Ted Leung wrote:
[snip <link idref="..."> errors]
> > > It looks to me like the forrest dtd's don't support some referencing
> > > features that Stylebook has.
> >
> > Yes :/  Forrest is quite far behind Stylebook.  Link idrefs would have to
> > be converted to page refs with #anchors.
> 
> Is this something that will be added?

Eventually, but I don't know how.  This "link to another node" problem is
related to our Problem #1, linking to externally generated stuff like
Javadocs.  Ideally, the solution should be general enough to solve both
probs.

> > > Also, does Forrest have doctypes corresponding to Xerces' releases.dtd,
> > > settings.dtd and book.dtd?
> >
> > Forrest has a book DTD, slightly less fancy than the Stylebook one.
> 
> Again the issue seems to be links
> 
> > status.xml is quite similar to releases.xml, but we don't have a DTD for
> > it.  status.xml gets rendered to
> > http://xml.apache.org/forrest/changes.html
> 
> It looks like there's a DTD for changes -- could we add an optional
> description element as a child of a release element?  That way you can
> have release specific notes before the list of all the actions, so
> people don't have to go looking at all the little changes.

Sounds good. How would this relate to real release notes?

Forrest currently does not have a DTD for status.xml, and is privately
(not pushed on users) experimenting with using status.xml to record
'issues', to better emulate a traditional Apache STATUS file.

> > settings.dtd looks quite Xerces-specific, but adding project-specific DTDs
> +
> > stylesheets is fairly easy in Forrest.
> 
> Can you point me to the right documentation to read for how to do this?

The "Adding new content type" section of "Using Forrest":

http://xml.apache.org/forrest/your-project.html#N10189

I also posted a ready-to-run example of a project using a custom doc type
and stylesheet:

http://marc.theaimsgroup.com/?l=forrest-dev&m=103786870103314&w=2


--Jeff