On 12/07/2010 11:43 AM, Georg Datterl wrote: > I'm not quite sure WHO exactly complains. The original xslt (with > <) works fine if I use it to transform the xml file. It generates > a fo-file which I can then transform into a pdf. The corrected xslt > works fine, if I don't use more complex transformations. It stops > working when I use variables.
Ah... I’ve got it now. This is why use of disable-output-escaping is so strongly discouraged... When you use XSLT to transform your XML and serialize it to disk, the d-o-e is applied and you get a valid FO. However, when you feed XML and XSLT to FOP, your transformation result is never serialized. The d-o-e directive is never applied, and a poorly-formed XML data structure is passed to FOP, resulting in your error. You will need to rewrite your transformation to avoid use of d-o-e. It is an unfortunate hack that really shouldn’t have been included in XSLT; it is never necessary, and while it enables some quick hacks that would be more complicated otherwise, it also is prone to mysterious breakage like your case. ~Chris -- Chris Maden, text nerd <URL: http://crism.maden.org/ > MISSING: land of free, home of brave. Last seen 10 September 2001. Reward offered. GnuPG Fingerprint: C6E4 E2A9 C9F8 71AC 9724 CAA3 19F8 6677 0077 C319 --------------------------------------------------------------------- To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
