Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 12851 invoked by uid 500); 4 Jun 2003 10:55:04 -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 12836 invoked from network); 4 Jun 2003 10:55:03 -0000 Received: from mail.vsa.de (HELO proxysrv.vsa.de) (62.180.233.67) by daedalus.apache.org with SMTP; 4 Jun 2003 10:55:03 -0000 Received: from 192.168.140.6 by proxysrv.vsa.de (InterScan E-Mail VirusWall NT); Wed, 04 Jun 2003 12:53:50 +0200 Received: by mailsrv.vsa.de with Internet Mail Service (5.5.2653.19) id ; Wed, 4 Jun 2003 12:53:31 +0100 Message-ID: <3D6B395115784A4FA9E91824855282C7251DCC@mailsrv.vsa.de> From: "Schlierf, Stephan" To: 'Forrest' Subject: Whole-site pdf Date: Wed, 4 Jun 2003 12:53:30 +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 Hello, a few days ago Jeff mentioned in an email that he developed a way to merge several files into one pdf-file. As far as I remember this topic was discussed here already in the past. Now my question is: How is this planned to work ? Does it generate a pdf-file for the whole site or just for the files that are linked to the current (visible) file ? For me, I'd prefer the last mentioned behaviour; I think it allows more flexibility in controlling the process. And, last but not least, when will it be available ? Stephan