I am validating with W3C and I am using:
Quote:
|
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
..and it's all cool. It wont validate with the trailing back slash of course, so I removed it.
However, every time I try to tidy a page, which I do after editing, every time, to make sure that there aren't any rogue <div>'s it takes away the
http-equiv="Content-Type" part :(
I am using the Tidy Tool that comes with 1stPage
The tidy tool is pretty popular, as far as I know. It was written by Dave Raggett of W3C, but it has a copyright of 1999. Maybe in 1999
http-equiv="Content-Type" wasn't used?
Anyway, I am absolutely convinced that there's another way to include the utf8 charset. I have come across this same problem before.
There's some code that W3C
and my tidy tool sees as valid. I am quite sure.
MrLeN