Laurent Bihanic wrote:
> FOP does not display any error message but the generated PDF file is 2
> KB shorter than when generated from the same FO document read from a
> file and Acrobat Reader complains that "the file is damaged and could
> not be repaired".
>
I found the problem in the appl
Hi again,
J.Pietschmann wrote:
> I suggest to check your SAX stream first whether all elements are
> properly closed. Try to feed it as a SAXSource to an identity XSL
> transformation (use TransformerFactory.newInstance().newTransformer()).
> The serialized file will be always well-formed (the tr
Hi,
J.Pietschmann wrote:
> I suggest to check your SAX stream first whether all elements are
> properly closed. Try to feed it as a SAXSource to an identity XSL
> transformation (use TransformerFactory.newInstance().newTransformer()).
> The serialized file will be always well-formed (the transfor
Hi David,
David B. Bitton wrote:
> my code uses the following:
>
> transformer.transform( new DOMSource( doc ), new SAXResult(
> _driver.getContentHandler() ));
>
> and it works great. Lemme know if you'd like to see the rest. :)
>
My code is exactly the same:
transformer.transform(new
ssage -
From: "J.Pietschmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 26, 2002 4:16 PM
Subject: Re: Problems with SAX pipeline
> Laurent Bihanic wrote:
> > This application uses a SAX pipeline to apply an XSLT transformation
> > (XM
Laurent Bihanic wrote:
> This application uses a SAX pipeline to apply an XSLT transformation
> (XML -> XSL-FO) and feed it into FOP's Driver directly through its
> ContentHandler.
>
> FOP does not display any error message but the generated PDF file is 2
> KB shorter than when generated from
Hi,
I'm in the process of migrating an application from FOP 0.17 to 0.20.3. This
application uses a SAX pipeline to apply an XSLT transformation (XML ->
XSL-FO) and feed it into FOP's Driver directly through its ContentHandler.
FOP does not display any error message but the generated PDF file
