I think that you've missed the point - the ampersand is required to seperate
out the parameters - not as part of the value of a parameter.  You'd use %26
if you wanted to pass through an ampersand as a value, but not for
delimiting the parameters.

e.g.

/pub.asp?meal=roast&pub=dog%20%26%20duck

would be used to pass through parameters meal and pub with values "roast"
and "dog & duck"

> -----Original Message-----
> From: Thomas B. Passin [mailto:tpassin@xxxxxxxxxxxx]
> Sent: Friday, April 20, 2001 3:18 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re:  Ampersand for URLs
> 
> 
> No matte what various browsers may or may not accept, using sgml/xml
> entities like "&" in a url does not conform with the rfc. 
>  The rfc wants
> you to use the %xx syntax. like "%20" for a space.  So one 
> approach would be
> to use xslt's translation feature to substitute "%26" for "&" 
> in the text of
> the url.
> 
> Another would be to output the url inside an <xsl:value-of> 
> element with
> disable-output-escaping='yes'.
> 
> Cheerss,
> 
> Tom P
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list