I may be on to something... In my XSLT, I have a few lines like these:
<xsl:text disable-output-escaping="yes"><fo:page-sequence master-reference="myPages"></xsl:text> <xsl:text disable-output-escaping="yes"><fo:flow flow-name="xsl-region-body"></xsl:text> Then later <xsl:text disable-output-escaping="yes"></fo:flow></xsl:text> <xsl:text disable-output-escaping="yes"></fo:page-sequence></xsl:text> If I transform the XML and XSLT using Coldfusion, I get a valid FO document that can be converted into PDF using FOP and the command line. I suspect that the processing of the XML/XSLT by FOP is different? Since I'm outputting these tags using xsl:text rather than having the tags present in the XSLT file, that's probably why it's not finding it and I'm getting an error? Dan PS: since I'm opening and closing these tags in different templates, I had no choice to use xsl:text. I may have to review my XSLT in order to have these tags present rather than having to output them using xsl:text. > -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > Sent: March 17, 2008 4:11 AM > To: [email protected] > Subject: Re: fo:simple-page-master is missing child elements > > > On 14.03.2008 18:40:16 Fournier,Danny [NCR] wrote: > > > > > -----Original Message----- > > > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > > > Sent: March 4, 2008 8:19 AM > > > To: [email protected] > > > Subject: Re: fo:simple-page-master is missing child elements > > > > > > I can only repeat myself: Is the error message here > really the only > > > message in FOP's output? > > > > > > To isolate the problem further you can just generate the > FO file in > > > your application and stream that to a file. Then run that FO file > > > through FOP from the command-line. If it works that way, you > > > probably have a namespace problem in your code (which > should show up > > > as error message in FOP's log output). > > > > > > I finally got to doing this. I exported the FO and ran it > against FOP > > using the command line. > > > > I got my PDF even though I had some warnings about content overflow > > (these will be painfull to fix IMO). > > They are usually not as painful to fix as you think. > > > Can you explain how this namespace problem works/could be fixed ? > > Not in one paragraph. For one, I don't know anything about > ColdFusion so I have no clue how the XML output from > ColdFusion is integrated with FOP. > Usually, this happens when the XML parser is not > namespace-enabled or if SAX events are produced in > non-namespace-aware fashion: > > Right: > contentHandler.startElement("http://www.w3.org/1999/XSL/Format > ", "fo:root", "root", atts); > > Wrong: > contentHandler.startElement(null, "fo:root", "root", atts); > > It's difficult from here to tell you what you have to do, > especially with so little information. > > Jeremias Maerki > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
