On 18/01/2011 08:27, Karl Stubsjoen wrote:
Saxon collapses the lines following each<fo:inline>
saxon (nor presumably MvpXslTransform) process the xsl-fo at all, so the
important question, if you think ther is a difference between then, is
what does the xsl-fo that is generated look like.
If the xsl-fo generated is different then we can look to differences
between the XSLT processors, but if it is the same, the difference is in
the way the xsl-fo processor is handling its input (with a microsoft xml
parser losing white space being a prime suspect).
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--