forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Portier" <...@outerthought.org>
Subject RE: Impossible to integrate PDF documents in forrest site?
Date Mon, 26 Aug 2002 11:26:34 GMT


> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
>
>
> Jeff Turner wrote:
> > On Sat, Aug 24, 2002 at 12:22:02PM +0200, Nicola Ken
> Barozzi wrote:
> > ...
> >
> >>>>>The output of Forrest will never show the internal
> >>>>>extension, it's only
> >>>>>a hint to the pipelines about the content of the file.
> >>>>
> >>But it can still remain as a semantical piece of
> info, now that I think
> >>of it.
> >
> >
> > I think that's the key; whether the 'pipeline' in
> > 'filename.pipeline.extension' is an attribute of the
> file, or of the
> > sitemap. Does it describe the file, or does it
> describe what Cocoon
> > should do with the file? The latter seems to be
> breaking IoC, as the file
> > author has to know details of the sitemap.
>

As stated before: it is about the URL (and thus the generated
file) not about the source file.
So, I think it will echo what cocoon _did_ with the file :-)


> Does putting a file in a dir tell Cocoon what to do
> with that file?
>
> No, it tells Cocoon *something* about the file, but not *what*.
>
> If I put .gif at the end of images, I'm not telling
> Cocoon what to do
> with them, but what they are.
> Cocoon can delete them, enlarge them, process them, or
> simply display them.
>
> As you see Cocoon has the control.
>


Mime
View raw message