Rakesh Patel wrote:
XML Spy process it exactly as you are saying - transform into a file and run FOP.bat on this file.<HTBodyText> <fo:block>example text</fo:block> Please read our <fo:basic-link external-destination="http://www.someplace.com/risk_warnings.html">Risks Warnings</fo:basic-link> document </HTBodyText>
and the XSL file:
<fo:block text-align="left" start-indent="5mm" space-before="2mm" font-size="12px" color="#000000" font-family="Arial, Helvetica, sans" font-weight="normal"> <xsl:value-of select="HTBodyText" disable-output-escaping="yes"/> </fo:block>
The embedded directives are only processed by FOP when I do this:
1. Run the xslt saving the output to a file 2. Pass the file to FOP for processing.
However, if I do it all together, either by using XMLSpy or in my servlet, the output ALL comes out as text.
By it's nature disable-output-escaping assumes that result of the transformation is serialized and reparsed again, that's why it doesn't work in FOP as in any SAX streaming environment.
Remember gold rule of xslt - don't use d-o-e unless you are generating non-XML. Why do you need it?
-- Oleg Tkachenko eXperanto team Multiconn Technologies, Israel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]