On Tuesday 02 October 2007 01:37:27 pm Andreas L Delmelle wrote: > On Oct 2, 2007, at 19:31, Steve Ebersole wrote: > > Hi Steve, > > > Attached is the simplified docbook and xslt. > > > > Thanks for taking a look. > > No problem, although... > > I've tried to run the XSLT-step separately, and received a couple of > warnings/errors, like: > > WARNING: javax.xml.transform.TransformerException: Making portrait > pages on A4 paper (210mmx297mm) > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: ERROR: xref > linking to tutorial has no generated link text. > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: Error: no ID for > constraint linkend: tutorial. > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: XLink to > nonexistent id: tutorial > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: ERROR: xref > linking to architecture has no generated link text. > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: Error: no ID for > constraint linkend: architecture. > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: XLink to > nonexistent id: architecture > Oct 2, 2007 7:59:18 PM org.apache.fop.cli.InputHandler warning > WARNING: javax.xml.transform.TransformerException: xi:include > encountered in book, but no template matches. > > Could this be a consequence of the simplification? The xlink warnings are (I assume) the link references in the master.xml; they reference linkends no longer in the document because I stripped out the needed XIncludes.
The other issue is a problem I believe. There is only one XInclude, which is needed as it is what contains all the table definitions. I assume it is a problem resolving the needed chapter on your system. Not sure why though. This should be a relative resolution. > Regardless of these errors, I end up with a valid FO document, but > running this through FOP afterwards, gives me an error: > > java.lang.IllegalStateException: > Flow 'xsl-region-body' does not map to the region-body in page-master > 'blank'. FOP presently does not support this. I would have to assume that this is caused by the issue with the XInclude. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
