Michael J. Hudson wrote:
> Well, the usual answer of "you should never need an unescaped ampersand"
> has never seem to work for me.  I've been told this before, but I don't
> see when this eventual conversion was suppose to happen

I'm saying it's not wrong to have & in your HTML. In fact, it's more
correct to have it there than not. The HTML user agent is supposed to
treat & as the ampersand character.

When clicked, this anchor:

<a href="http://www.skew.org/printenv?foo=bar&amp;baz=maz">click</a>

should send the user to:
http://www.skew.org/printenv?foo=bar&baz=maz

*not* to:
http://www.skew.org/printenv?foo=bar&amp;baz=maz

I could write the anchor entirely as character references if I wanted:

<a href="&#x68;&#x74;&#x74;&#x71;&#x3A;&#x2F;&#x2F;&#x77;&#x77;&#x77; etc.

Also, what I've read indicates that WML is in fact an XML-based language
and thus I do not see what you are gaining by using the HTML output
method.


   - Mike
____________________________________________________________________
Mike J. Brown, software engineer at         My XML/XSL resources:
webb.net in Denver, Colorado, USA           http://www.skew.org/xml/


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