<a href="javascript:include('toc41837.htm?i=1','TOC');">
Notice the happy apostrophes. However, when I use a variable
$href containing a query string instead of @href. $href being
similar to:
/support?p=Compare&c=Compare/help/6.2/toc41837.htm
I get this:
<a
href="javascript:include('/support?p=Compare&c=Compar
e/help/6.2/toc41837.htm?i=1','TOC');">
I theory ' and ' should be 100% equivalent, so either output is
correct. It wouldn't surprise me, however, to learn that within a javascript
"URI" a browser might treat them differently. Javascript URIs violate pretty
well every standard that's been written.
If this URI isn't equivalent to the one using a literal "'" then I would
advise taking it up with your product vendor. At least, that's what I would
recommend if the product vendor were anyone other than Microsoft.
I've tried to 'disable-output-escaping' in the xsl:text
elements but it doesn't make any difference. Can anyone say
what is going on?
disable-output-escaping won't make any difference - it is defined to have no
effect on attributes.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--