[imps] validator front end not talking to servlet
rancid.iodine at gmail.com
Fri Apr 19 02:07:59 PDT 2013
Nice, I had no idea about that option, or indeed the nature of
validator.nuvis-a-vis w3c, thanks very much.
Saying that, the --w3cbranding option doesn't come up if you do
python build/build.py --help ...
This doesn't mean the option doesn't work, but I had to download missing
.pngs to the checker/validator/site directory, and even then when you run
python build/build.py --w3cbranding --port=8888 --local run
you can't actually see the branding as you would on
Are all these issues maybe a case of us using an older version of
validator.nu possibly, or are there some other components I could download
that would make it all look like http://validator.w3.org/nu/ ?
On 18 April 2013 23:52, Michael[tm] Smith <mike at w3.org> wrote:
> "Michael[tm] Smith" <mike at w3.org>, 2013-04-19 07:34 +0900:
> > Rancid Iodine <rancid.iodine at gmail.com>, 2013-04-18 18:13 +0100:
> > > Michael once said to me to get rid of the legacy w3c validator
> > > (considering the validator.nu does a better job validating any
> version of
> > > HTML), but we're in a corporate "situation" here wherein I'm told they
> > > not accept any validator unless it has a "w3c" stamped on it's
> forehead ...
> > > which validator.nu does not have.
> > The W3C instance at http://validator.w3.org/nu/ does. Even the URL
> alone does.
> > http://validator.w3.org/nu/about.html makes it quite clear that it's an
> > official W3C product/service -- the "W3C Nu Markup Validator". I'm not
> > what more I could do to stamp "W3C" on it clearly.
> Note that if you want to run the service locally with the W3C branding, you
> just need to start it with the --w3cbranding option, like this:
> ./build/build.py --w3cbranding
> Michael[tm] Smith http://people.w3.org/mike
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Implementors