Clay Leeds wrote:That is correct. The fox: elements do not appear in the intermediate .fo file I generated with xalan.
That means it is not a FOP question, but an XSLT question instead. If you'll
send me some XML/XSLT snippets offline, I'll help if I can, but I can't do
that on this list.
I suspect you're correct that it was not a FOP question, but here's the solution to the problem:
I'd written the fox: extension information in an xsl-fo file that was included in another, and so the fox: portion wasn't called. Moving the fox: stuff to the file which calls (via xsl:include) the other file resolved the issue.
I have two versions of my XSL-FO file depending on output method:
xml_med7_default.fo (87,109 bytes)
- all markup to output beautiful documents with PRINT/AWT
- previously had fox: stuff in here, since that's where the fo:block id calls go
xml_med7_default_pdf.fo (6,390 bytes) - only page/region margins & extents markup - <xsl:include href="xml_med7_default.fo"/> - now includes the fox: stuff
FWIW, here's some background about why I have two files:
I've found that outputting xml_med7_default.fo to AWT (used by -print and -awt) gives me 20-40% larger region-before & region-after sections. As a result, when outputting to -pdf, my pages would have an extra margin of 1-2cm+... So I created a "xml_med7_default_pdf.fo", into which I <xsl:include href="xml_med7_default.fo"/>. the new file has only the region-before/-after/-body stuff.
I hope this is helpful to everyone... BTW, is the fox: portion a bug? ;-p
--
Clay Leeds - [EMAIL PROTECTED]
Web Developer - Medata, Inc. - http://www.medata.com
PGP Public Key: https://mail.medata.com/pgp/cleeds.asc
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
