Re: Nu Validator--garbled quotes?

...and just after sending this I realize the problem, I forgot to specify UTF-8 in my decoding of the string. But now I have a different question:

Why are oxford quotes (i.e. winword characters) used for the W3C validator's response contents? Is this deliberate? They are very non-portable (and the bane of many developers), I am wondering if I could file an issue to have them taken out.

Kean Erickson
Software Developer
OmniUpdate
805.484.9400, ext. 261
omniupdate.com<http://www.omniupdate.com>
________________________________
From: Kean Erickson
Sent: Wednesday, June 26, 2019 5:21 PM
To: www-validator@w3.org
Subject: Nu Validator--garbled quotes?

Hi there,

I have a question about the Nu Validator's JSON output. I am using the newest version's docker image like so:

docker run -it --rm -p 8888:8888 validator/validator:latest

..and am sending a POST to the http checker with ..?out=json using content-type "text/html;charset=utf-8" and accepting "application/json;charset=utf-8"

It works properly but the content I am getting (see attached) back seems garbled, the quotes are encoded weirdly. The results themselves don't matter, I am wondering about all of the "“a�" entries appearing in place of quotes and other entities. Please let me know if I'm doing something wrong with the content-type? I tried setting content-type to application/json but the response demanded an XML-based content-type even though I am requesting JSON.

Thank you for your time,
Kean Erickson
Software Developer
OmniUpdate
805.484.9400, ext. 261
omniupdate.com<http://www.omniupdate.com>