- From: Daniel Lamberti <daniellamberti@gmail.com>
- Date: Mon, 3 Jan 2022 12:40:22 -0300
- To: "Jukka K. Korpela" <jukkakk@gmail.com>
- Cc: W3C WWW Validator <www-validator@w3.org>
- Message-ID: <CAP5Big+6BKpPnSWTpZ3L+F-yBx96=yYPUy-P-uizz6_vF33RFQ@mail.gmail.com>
Hi Jukka Thank you for your reply and assistance. You are right regarding lang es (Spanish), I will quickly change that parameter in all my web site pages. I don´t have any idea how to tell my server service to make sure they are sending a Content type header either. I asume that there is something that I cannot do from my side. I contacted my server support and explain this situation but they told me that it is a "code mistake", of course it is not, they should go back to university and review some concepts ... hehehe. Actually, the only warning messages I got from W3C validator is about content type (no recogninzing utf-8), anything else. By the way, I wrote another page (on Virtual Studio Code) almost empty, just with the regular doctype and meta tags (body and so on), just to check what could happen. I got same warnings messages so, it is pretty clear for me that the issue comes from my server service, for some reason they are not including the content type header. I will contact them again and will try to figure out how can we solve it. I do want to have all my web site pages validated by W3C. thank you! Daniel On Mon, Jan 3, 2022 at 9:13 AM Jukka K. Korpela <jukkakk@gmail.com> wrote: > Daniel Lamberti (daniellamberti@gmail.com) wrote: > >> >> >> ---------- Forwarded message --------- >> From: Daniel Lamberti <daniellamberti@gmail.com> >> Date: Sat, Jan 1, 2022 at 2:27 PM >> Subject: issue with encoding >> To: <www-validator@w3.org> >> > > It looks like you sent the message January 1st but somehow it did not get > through. Anyway, in the list archives > https://lists.w3.org/Archives/Public/www-validator/2022Jan/ > that message is not present, but this one is. > > >> No matter what I try I always get same result, for some reason W3C >> validator does not recognize utf-8 encoding, and point out all the time >> that the document is under windows-1252 encoding. >> I save the index.html with and without BOM, I tried to save the >> document on a text editor making sure that is utf-8 encoding, but never get >> success. >> I tried just tu save another .html file, completely empty (just with >> regular head, body with a h1 "hello") and I got same result. >> > > The validator gives priority to the encoding declared in HTTP headers, > over <meta> tags. And the response headers for > > >> www.daniellamberti.com >> > > include > > Content-Type: text/html; charset=ISO-8859-1 > > as you can see e.g. using https://websniffer.cc/ or > https://www.rexswain.com/httpview.html . The latter also shows (when > using “Hex” for “Display option”) that there is no BOM at the start. > > I have no idea what you might need to do with the server to make it send a > Content-Type header specifying charset=utf-8 (or no charset at all). > > By the way, the <html> tag declares lang=en, even though the content is > Spanish. It should be lang=es. The strange thing here is that if I remember > correctly, the validator used to run a heuristic check of the actual text > content against the lang declaration and report suspected mismatches. In > this case, I would very much expect any reasonable heuristics to detect and > report the problem-. > > Yucca, https://jkorpela.fi > >
Received on Monday, 3 January 2022 15:41:49 UTC