Return-Path: 
 <forrest-dev-return-5027-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 82761 invoked by uid 500); 8 Mar 2003 03:40:47 -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 82752 invoked from network); 8 Mar 2003 03:40:47 -0000
Received: from grunt21.ihug.com.au (203.109.249.141)
  by daedalus.apache.org with SMTP; 8 Mar 2003 03:40:47 -0000
Received: from p116-apx1.syd.ihug.com.au (expresso.localdomain)
 [203.173.140.116]
	by grunt21.ihug.com.au with esmtp (Exim 3.35 #1 (Debian))
	id 18rVCh-0004zH-00; Sat, 08 Mar 2003 14:40:56 +1100
Received: from jeff by expresso.localdomain with local (Exim 3.35 #1 (Debian))
	id 18rVEl-0001nH-00
	for <forrest-dev@xml.apache.org>; Sat, 08 Mar 2003 14:43:03 +1100
Date: Sat, 8 Mar 2003 14:43:03 +1100
From: Jeff Turner <jefft@apache.org>
To: forrest-dev@xml.apache.org
Subject: Re: Not processing links
Message-ID: <20030308034303.GB5467@expresso.localdomain>
Mail-Followup-To: forrest-dev@xml.apache.org
References: <3E690870.3080402@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E690870.3080402@apache.org>
User-Agent: Mutt/1.4i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, Mar 07, 2003 at 04:00:32PM -0500, Berin Loritsch wrote:
> How do I get Forrest not to try to process a link?

The solution is a bit hacky:

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

See avalon-site for an example.

> If I want to reference API docs that are relative to where I am,
> how do I put that in my book.xml or site.xml?
> 
> I have tried this:
> 
> <external label="API Docs" href="api/"/>
> 
> But that causes a problem looking for the site.xml (using book.xml
> for this one).
> 
> The only way it renders properly is if I do an absolute path to
> where it will end up on the web site:
> 
> <menu-item label="API Docs"
>   href="http://avalon.apache.org/excalibur/component/api/"/>
> 
> That doesn't help when a user wants to browse the docs offline.
> 
> Is this where we would *need* a site.xml, or are there still
> problems?

No, this problem exists with both book.xml and site.xml 

It breaks because the Cocoon CLI translates api/ to api/index.html.  The
pipeline happens to look for api/site.xml next, hence the error message. 

--Jeff