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:Daniel Barclay (dan@fgm.com)
Date:Nov 13, 2006 10:14:30 am
List:org.w3.public-evangelist

Paul Arenson wrote: ...

CODE <meta content="text/html; charset=UTF-8" http-equiv="content-type">

but this page is not in utf-8 but in shift-jis

Either you have to save your page as utf-8 or to change the encoding information to <META HTTP-EQUIV="Content-Type" CONTENT="text/html;">

It is? I don't recall using that. hmmm. And when i save to desktop, changing to shift jis doesn't help, nor does looking at it on the web. Oh well....

Remember that <META HTTP-EQUIV="..." ...> elements are not supposed to be read by the browser when the browser retrieved the document from a server.

Such META elements are for the server to read and use to construct real HTTP header fields (if the server chooses that mechanism).

(When dereferencing a "file:..." URL, there is no explicit service, so browsers are probably allowed to read META elements, but they very well might not.)

Daniel