Hi Joe, I disagree -- this is a bug, and I've stated this many times before. See: http://www.w3.org/TR/html401/appendix/notes.html#h-B.2.2 I think, historically, HTTP servers expected an un-escaped &, so tools which generate HTML have tried to accomodate this. But it _is_ a bug. Newer HTTP servers should do the right thing. Dave Joseph Kesselman <[EMAIL PROTECTED] To: [EMAIL PROTECTED] com> cc: (bcc: David N Bertoni/Cambridge/IBM) Subject: Re: Bug or Feature: unescaping & in href attribute while in HTML 01/22/2003 01:20 output method PM Please respond to xalan-dev I believe that's correct operation. Xalan-J produces the same result. When generating HTML output, attributes known to represent URIs are escaped AS PER HTML'S CONVENTION FOR URIS, which is not the same as XML escaping. Remember, HTML is not yet XML-based; it's SGML-based, and SGML allows some things that XML doesn't. ______________________________________ Joe Kesselman / IBM Research
Re: Bug or Feature: unescaping & in href attribute while in HTML outputmethod
David N Bertoni/Cambridge/IBM Wed, 22 Jan 2003 13:29:38 -0800
- Bug or Feature: unescaping & in href... Robert Schiele
- Re: Bug or Feature: unescaping &... Joseph Kesselman
- Re: Bug or Feature: unescaping &... David N Bertoni/Cambridge/IBM
- Re: Bug or Feature: unescaping &... David N Bertoni/Cambridge/IBM
