Return-Path: 
 <forrest-dev-return-3850-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 67891 invoked by uid 500); 26 Nov 2002 14:11:59 -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 67881 invoked from network); 26 Nov 2002 14:11:58 -0000
Received: from smtp3.ihug.com.au (203.109.250.76)
  by daedalus.apache.org with SMTP; 26 Nov 2002 14:11:58 -0000
Received: from p685-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.142.177]
	by smtp3.ihug.com.au with esmtp (Exim 3.22 #1 (Debian))
	id 18GgRS-0002ui-00; Wed, 27 Nov 2002 01:11:59 +1100
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 18GgXl-00033n-00
	for <forrest-dev@xml.apache.org>; Wed, 27 Nov 2002 01:18:29 +1100
Date: Wed, 27 Nov 2002 01:18:28 +1100
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Stylebook goodness (Re: Getting off of Stylebook)
Message-ID: <20021126141828.GF3722@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <01d301c294e2$810f79b0$0a00a8c0@boo>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01d301c294e2$810f79b0$0a00a8c0@boo>
User-Agent: Mutt/1.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Mon, Nov 25, 2002 at 04:26:46PM -0800, Ted Leung wrote:
...
> I would love to see some other projects move from Stylebook to Forrest.
> One thing that would really help those of us in the other projects
> would be a set of stylesheets that we could use to convert our
> stylebook documentation into Forrest documentation.  Is there a plan to
> do something like that?

It looks like Stylebook has some nice features that Forrest lacks:

1) The 'book.xml' can be specified, allowing various sites to be
generated from a single set of sources.  Eg, xalan-jlocal.xml and
xalan-jsite.xml generate slightly different sites, one for local use, one
for the website.

2) From Xalan's xdocs/sources/xalan-jlocal.xml:

<book title="Xalan XSL Transformer User's Guide" copyright="2002 The Apache Software Foundation">
  <resources source="sbk:/sources/xalan/resources.xml"/>
  ...
</book>

And then xalan/resources.xml contains links to 'resources':

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE resources [
  <!ENTITY % externalEntity SYSTEM "../entities.ent">
  %externalEntity;
  ...
  ]>

<resources>
  <resource id="xslt4j-current" 
    title="&xslt4j-current;" 
    location="http://xml.apache.org/xalan-j"/>
  <resource id="ApacheLicense" 
            title="The Apache Software License, Version 1.1" 
            location="http://xml.apache.org/dist/LICENSE.txt"/>
  <resource id="bugzilla"
            title="Bugzilla (the Apache bug database)"
            location="http://nagoya.apache.org/bugzilla"/>
  ...

  <human-resource id="sboag"
    name="Scott Boag"
    mailto="scott_boag@us.ibm.com"/>
  ...
</resources>


Then XML files can have stuff like:

All known &xslt4j; bugs are listed in <resource-ref idref="bugzilla"/>.

That expands to:

All known Xalan-Java bugs are listed in <a
href="http://nagoya.apache.org/bugzilla">Bugzilla (the Apache bug
database)</a>.


Pretty neat :)  Seems like Forrest has some way to go before equalling
Stylesbook functionality.


--Jeff

> Thanks,
> 
> Ted