- From: Michael Jackson <michael.jackson@bcs.org.uk> <michael.jackson@bcs.org.uk>
- Date: Sun, 20 Jan 2002 14:45:16 +0000 (GMT)
- To: Sascha Claus <SC_LE@gmx.de>
- cc: Liam Quinn <liam@htmlhelp.com>, www-validator@w3.org
On Fri, 18 Jan 2002, Sascha Claus wrote: > Michael Jackson wrote: > > > On Fri, 18 Jan 2002, Sascha Claus wrote: > >><http://www.columbia.edu/kermit/utf8.html> > >>Content-Type: text/html > >> > >><http://validator.w3.org/check?uri=http://validator.w3.org/> > >>Content-Type: text/html; charset=utf-8 > >> > >>Perhaps Lynx doesn't support <meta http-equiv="..">. > > > > Sorry, that went over my head. If you could be patient with > > my ignorance on such matters and perhaps attempt a little > > more helpful reply. TIA. -MJ. > > > The validator sends the encoding/charset as HTTP Header, the other site > doesn't. So Lynx gets no UTF-8 declaration from columbia.com. Perhaps > that's the reason for the difference. (Browsers don't need to support a > charset declaration via <meta>-tag.) Try > > lynx -dump -head http://www.columbia.edu/kermit/utf8.html > > and > > lynx -dump -head http://validator.w3.org/check?uri=http://validator.w3.org/ > > from the command line and have a look at the output. > Sascha, Thanks. I tried on Friday from several places but it was U/S: $ lynx -dump -head http://validator.w3.org/check?uri=http://validator.w3.org/ EISNER::JACKSON_1 13:47:43 LYNX CPU=00:00:00.22 PF=450 IO=984 MEM=327 EISNER::JACKSON_1 13:48:03 LYNX CPU=00:00:00.22 PF=450 IO=1367 MEM=327 EISNER::JACKSON_1 13:48:25 LYNX CPU=00:00:00.22 PF=450 IO=1814 MEM=327 lynx: Can't access startfile http://validator.w3.org/check?uri=http://validator. w3.org/ [ OK its working today and apologies in advance because I've naively asked a question ("why doesn't it work?") without being knowledgeable enough to understand the answer. -- By all means point me to stuff I should read to clue-up. ] So Columbia place a <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8"> declaration in the html head section for the page and have the server simply return a Content-Type: text/html Whereas, Validator places no form of charset declaration in the html head section for the page but instead has the server return with Content-Type: text/html; charset=utf-8 Presumably these are different ways of achieving the same thing. The problem for me is not understanding the relationship (if any) between what `lynx-dump -head` shows for Content- Type, and what is coded in the page's html head section. ...and therefore, why one would want to do it (it being I presume achieving the same thing) the way that Validator does it, rather than the way that Columbia does it even though `the Columbia way' works on old browsers. So I apologise in advance for coming back at you that I see the difference you were pointing out to me, but don't really understand the implications. Thanks for your continued patience :). Best regards, MJ.
Received on Sunday, 20 January 2002 09:35:14 UTC