DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10579>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10579 Problem in XSL Transformation ------- Additional Comments From [EMAIL PROTECTED] 2002-07-09 18:09 ------- Hm. The issue is escaping of the output, specifically of an attribute value. I don't think this is a bug per the specifications of XSLT or HTML, but I understand that it's a hassle. Arguably, the escaping shouldn't be a problem; any tool which is reading a file that claims to be HTML ***SHOULD*** understand that ' is simply another way of typing the ' character and do the right thing. But some browsers, especially older browsers, are unacceptably sloppy in that regard, and if you're trying to cater to one of those... I don't think there's any architected mechanism to suppress escaping of attribute content. We could scan the attribute's value for ' or " characters and try to pick the other one to enclose the value... but that would adversely effect performance. (Have you tried changing your ' character to "? Javascript should accept either, and picking the other might affect how we generate our output...) If all else fails: If you don't intend to use Xalan's SAX output directly, would be to output the whole element as raw text, with output escaping turned off. <xsl:text disable-output-escaping="yes"><a href=" javascript:show_calendar('dateJump.CpitDate');"></xsl:text> <img src="HTMLandImages/show-calendar.gif" width="24" height="22" border="0"/> <xsl:text disable-output-escaping="yes"><a></xsl:text>
