12 messages in org.w3.public-evangelistRe: japanese encoding nightmare
FromSent OnAttachments
Paul ArensonNov 12, 2006 5:50 pm 
Karl DubostNov 13, 2006 5:21 am 
Paul ArensonNov 13, 2006 6:25 am 
Paul ArensonNov 13, 2006 6:58 am 
Daniel BarclayNov 13, 2006 10:14 am 
Mike SchinkelNov 13, 2006 3:10 pm 
David DorwardNov 13, 2006 3:17 pm 
Paul ArensonNov 13, 2006 6:06 pm 
Daniel BarclayNov 16, 2006 11:13 am 
Richard IshidaNov 23, 2006 2:15 am 
Tex TexinNov 23, 2006 9:03 am 
Paul ArensonDec 5, 2006 8:07 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: japanese encoding nightmareActions...
From:David Dorward (dav@dorward.me.uk)
Date:Nov 13, 2006 3:17:29 pm
List:org.w3.public-evangelist

On Mon, Nov 13, 2006 at 06:11:18PM -0500, Mike Schinkel wrote:

This http://www.w3.org/TR/html4/struct/global.html#adef-http-equiv says (emphasis mine): "HTTP servers *MAY* use the property name specified by the http-equiv attribute to create an [RFC822]-style header in the HTTP response." That would imply they might not, and if so the browser would have to handle, no?

No, just that the server should use some other means to determine the character encoding of the document (generally "use the configured value").

Anyway, just wanted to point this out (it is a shame the recommendation didn't say "MUST" instead of "MAY")

Ouch, every HTTPD an HTML parser? Ouch!

-- David Dorward http://dorward.me.uk