Re: Nu HTML Checker and ampersands

"Michael[tm] Smith" <[email protected]> Wed, 15 Jul 2015 21:40:35 +0900

Newsgroups	gmane.org.w3c.validator
Message-ID	<[email protected]>

"Michael[tm] Smith" <[email protected]>, 2015-07-15 14:40 +0900:
> Archived-At: <http://www.w3.org/mid/[email protected]>
> Rich Webster <[email protected]>, 2015-07-14 14:44 -0400:
> > Archived-At: <http://www.w3.org/mid/CAL2Gn_0EQsRntC8NwqVpkDPPHu2iPSKpXmy6OT0mDq+81V5pgQ@mail.gmail.com>
> > 
> > Thank you for the service. The Nu HTML Checker takes my copied and pasted
> > source, with ampersands coded as &amp;, and changes them to plain &s when
> > it does the validation test.
> 
> Thanks for the report. I doesn’t do that if you use the form at
> https://validator.w3.org/nu/ directly. So please consider doing that instead.
> 
> I see that it does change the ampersands if you instead use the form at
> https://validator.w3.org/ So that’s a bug that I need to fix.

I’ve now fixed it be taking a different approach to way the document gets
passed on to https://validator.w3.org/nu/ This approach should ensure that
the content of the document doesn’t get altered at all before it’s sent on.

If you find any other problems with it, let me know.

  —Mike

> But the right way to never run into it is to never use
> https://validator.w3.org/ but to instead always just use
> https://validator.w3.org/nu/

-- 
Michael[tm] Smith https://people.w3.org/mike

signature.asc (application/pgp-signature, 819 B)