-Original Message-
From: Rauh, Michael [mailto:[EMAIL PROTECTED]
Running the FO docs produced by Saxon through FOP standalone
worked, as long as the files were ISO-8859-1 encoded. That
aroused suspicion that there's a wrong encoding somewhere in the
chain. I'll try to track this
Rauh, Michael wrote:
I'm running XSLT transformations from within Java and put the result DOM into
FOP's AWTRenderer. ... That's all working fine with Xalan (from the JDK) and
jd.xslt. But with Saxon 6.5.3 and Saxon 7.8, FOP throws NullPointerExceptions.
Here's the ouput when using Saxon-6.5.3:
-Original Message-
From: Rauh, Michael [mailto:[EMAIL PROTECTED]
are there known problems with the interoperability of specific
XSLT processors and FOP?
Phew! What a question... I've certainly thought lots of times about using
Saxon with FOP instead of Xalan, but haven't really
