- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 06 Feb 2009 18:35:22 +0000
- To: www-validator-cvs@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6534 Austin Guthals <aguthals@shoom.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #2 from Austin Guthals <aguthals@shoom.com> 2009-02-06 18:35:22 --- I read the FAQ. The Faq is not correct either. <a href="foo.cgi?chapter=1§ion=2©=3&lang=en">Test</a> is perfectly valid because © will not get translated to the copyright sign in the browsers url. You only need to encode ampersands if they will be displayed in the content of your page. Here is how it would work <a href="foo.cgi?chapter=1§ion=2©=3&lang=en">foo.cgi?chapter=1&section=2&copy=3&lang=en</a> Here the characters that will be painted in the content of the page must be encoded, however the url does not need to be encoded. If I am mistaken, please give me an example of this link <a href="foo.cgi?chapter=1§ion=2©=3&lang=en">foo.cgi?chapter=1&section=2&copy=3&lang=en</a> that validates with your checker and that works with a web server that is expecting '&' to delimit named parameters. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 6 February 2009 18:35:31 UTC