> -Original Message-
> From: Glen Mazza [mailto:[EMAIL PROTECTED]
>
> Keep in mind, for FOP's xml+xsl->fo->pdf, we don't
> output an intermediate fo file. So there may be *no*
> redirected files to keep track of.
>
Yah... wonder where these redirected parts would end up in this case...
t
--- "Andreas L. Delmelle" <[EMAIL PROTECTED]>
wrote:
>
> The XSLT extension functions actually are meant to
> redirect certain parts of
> the transformation result to other files.
Yes, our properties.xsl used to do that for the 250 or
so autogenerated property class files.
> In the case such a
Glen Mazza wrote:
Interesting question...I would think the extension
functionality allows only multiple output *files*
only, correct?
It depends. The extensions write to a file or more
generally to an URL. However, both Saxon and Xalan
have more or less undocumented hooks for getting
SAX events or
> -Original Message-
> From: Glen Mazza [mailto:[EMAIL PROTECTED]
> --- "Andreas L. Delmelle" <[EMAIL PROTECTED]>
> wrote:
> > Started having strange ideas on the possibility of a
> > scenario like
> >
> > 1 XML + 1 XSLT => n FOs => n PDFs
> >
> > XSLT processors support extension functions
--- "Andreas L. Delmelle" <[EMAIL PROTECTED]>
wrote:
>
> Hi all,
>
> Started having strange ideas on the possibility of a
> scenario like
>
> 1 XML + 1 XSLT => n FOs => n PDFs
>
> XSLT processors support extension functions for the
> output to multiple FOs,
> but in what way could (or does) FOP
Hi all,
Started having strange ideas on the possibility of a scenario like
1 XML + 1 XSLT => n FOs => n PDFs
XSLT processors support extension functions for the output to multiple FOs,
but in what way could (or does) FOP support the multiple PDF rendering? How
would one go about such a task (i.
