Return-Path: 
 <forrest-dev-return-5300-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org
Received: (qmail 683 invoked by uid 500); 4 Apr 2003 09:00:30 -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 638 invoked from network); 4 Apr 2003 09:00:29 -0000
Received: from mail.vsa.de (HELO proxysrv.vsa.de) (62.180.233.67)
  by daedalus.apache.org with SMTP; 4 Apr 2003 09:00:29 -0000
Received: from 192.168.140.6 by proxysrv.vsa.de (InterScan E-Mail VirusWall
 NT); Fri, 04 Apr 2003 11:02:02 +0200
Received: by mailsrv.vsa.de with Internet Mail Service (5.5.2653.19)
	id <G35JKAZ0>; Fri, 4 Apr 2003 11:00:40 +0100
Message-ID: <0E92BDED93E8D611866800B0D0795D3A1F4F40@mailsrv.vsa.de>
From: "Schlierf, Stephan" <Stephan.Schlierf@VSA.de>
To: 'Forrest' <forrest-dev@xml.apache.org>
Subject: Problems with editing files in build/webapp (revisited)
Date: Fri, 4 Apr 2003 11:00:38 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

After some more trial and error testing I arrived at the conclusion that the
problem that images don't appear in the PDF-file doesn't seem to have
something to do with editing files in the build/webapp tree.
Killing the "forrest run" process, backcopying all files and doing a
"forrest site" show the same result.
As far as I can see it depends on the fact that images which are nested in a
table aren't displayed in the pdf-file.
So a
<table>
   <tr>
      <td><img src="images/foo.png" alt="It's a foo picture"/></td>
   </tr>
</table>
is well shown in the HTML-file but not in the generated PDF-file

Stephan

>Sorry, I forgot to mention it:
>Forrest CVS

>Killing the "forrest run" process and starting it again doesn't help.

> > On Fri, Apr 04, 2003 at 09:28:49AM +0100, Schlierf, Stephan wrote:
> > > Hi,
> > > I started forrest by "forrest run".
> > > Now if I add an image to a file in the build/webapp/content/xdocs tree
> > it is
> > > shown in the browser but does not appear in the respective PDF-file
> (not
> > the
> > > image, not even the text of the "alt"-attribute).
> > > The image is located in build/webapp/resources/images.
> > > Can someone give me a helping hand ?
> > 
> > Forrest 0.4 or CVS?  PDF images don't work in 0.4, but they should in
> > CVS.  A 0.4 workaround that _might_ work is to hardcode the filesystem
> > path
> > to the image in the XML file:
> > 
> >  <img src="/path/to/site/build/webapp/resources/images/foo.png"
> alt="It's
> >  a foo picture"/>
> > 
> > --Jeff
> > 
> > > TIA,
> > > Stephan
> > > BTW: I include the image by 
> > > <img src="images/foo.png" alt="It's a foo picture"/>
> > > I use the krysalis site skin
> > >