Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 47849 invoked by uid 500); 22 Aug 2002 15:30:48 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 47836 invoked from network); 22 Aug 2002 15:30:47 -0000 Received: from otsrv1.iic.rug.ac.be (157.193.121.51) by daedalus.apache.org with SMTP; 22 Aug 2002 15:30:47 -0000 Received: from ROSINANTE ([192.168.123.101]) by otsrv1.iic.rug.ac.be (8.11.6/8.11.6) with SMTP id g7MFUnO18429; Thu, 22 Aug 2002 17:30:49 +0200 From: "Marc Portier" To: , Subject: RE: Impossible to integrate PDF documents in forrest site? Date: Thu, 22 Aug 2002 17:30:48 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <3D64F2E8.9060903@apache.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: > -----Original Message----- > From: Nicola Ken Barozzi [mailto:nicolaken@apache.org] > Sent: donderdag 22 augustus 2002 16:19 > To: forrest-dev@xml.apache.org > Subject: Re: Impossible to integrate PDF documents in > forrest site? > > > > Nicola Ken Barozzi wrote: > > > > > myfile.pipeline.extension > > > > I like it. > > Expanding a bit on this: > > We can dictate that every file in the contents can > have a double extension. there was even mentioning of more then two at the moment the idea got me going .... Next to that I don't see why there would be no room for something like testresult.metric.svg.jpg? Looking at it from this angle the multiple parts of the new extension become like a route or a trail describing how to get from *.metric.xml to jpg via svg. (Supposing there could be more then one route) > The output of Forrest will never show the internal > extension, it's only > a hint to the pipelines about the content of the file. > jap. > We can also decide that it's lacking it, a default > pipeline will be used. > > ie: > > generate.xdoc.pdf (means that I want a pdf from a > xdoc pipeline) > generate.pdf (means that I want a pdf from the > default pipeline) > > Both will generate > > generate.pdf > not really: there will be a different file on your HD, pretty much like the *.dtdx.html files from the DTD examples to date. see http://outerthought.net/forrest/document-v11.dtdx.html > And all links will be > > > I'm missing something... how do you see it cocoon decide between more then one now? My proposal would be to have 3 different links (thus 3 different files on HD) But maybe I just gave you the idea to get all out of it? > > The only argument *against* this is that if I have > > generate.xdoc.pdf > generate.myformat.pdf > generate.pdf > > what will be the result from Cocoon? > I think we're talking about slightly different things... please explain... The multi-dot file extensions feels a bit odd to me as well, but I don't see how we could go without. (of course we could use just dashes or something: generate-xdoc.pdf but then '-' become reserved inside filenames) Maybe it is just one of those things one needs to get working with? > We loose the 1-1 mapping between input and output, I think the only 1-1 we need to borrow is the 'finding & addressing' part of the URI. > lest we put up a > system to check for it. > > -- > Nicola Ken Barozzi nicolaken@apache.org > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > ------------------------------------------------------- > -------------- > -marc=