DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=30197>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30197 <xsl:output method="text" affects result tree construction ------- Additional Comments From [EMAIL PROTECTED] 2004-07-21 13:22 ------- Doing the override via the API strikes me as a FAR better idea -- preserve flexibility, while allowing folks who want your behavior to get it. Debate in progress on the XSL User's Mailing List. I posted my arguments in more detail there. The key point, for me, is that outputting to an XML API should yield the same result as outputting to XML then parsing back into that API -- and outputting to the XPI and then serializing should yield the same result as outputting direct to XML. There are some limitations on how close we can come, but I think that Really Is what the customers are going to want and expect as our default mode of operation. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
