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-20 13:08 ------- >The xsl:output method="text" is supposed to apply only when the result tree >is serialized. Hmmm. Grey area... The spec says: "An XSLT processor may output the result tree as a sequence of bytes, although it is not required to be able to do so (see [17 Conformance]). The xsl:output element allows stylesheet authors to specify how they wish the result tree to be output. If an XSLT processor outputs the result tree, it should do so as specified by the xsl:output element; however, it is not required to do so." It isn't clear whether the second half of that statement is conditionalized by the first half -- that is, whether it's really intended that xsl:output apply only to output as a sequence of bytes. I would argue strongly that it it is, in fact, USEFUL to be able to generate the equivalent of text-mode output for an in-memory transforamtion, and that the better answer here is to change your stylesheet to not assert text mode when that isn't what you want. So I'm inclined to reject as invalid unless someone can get the XSLT Working Group to confirm that, yea verily, output mode is not intended to affect in-memory output. (If TrAX disagrees with the WG, that's another kettle of worms, of course.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
