Scripsit
do*********@gmail.com:
I have the following in the XHTML 1.0 Strict page:
<meta http-equiv="Content-Type" content="text/html;charset=utf-32" />
Why are you using XHTML, and why are you using utf-32? That's pointless
game on the Web these days: you have nothing to win and almost
everything to lose. Have you any reason to believe that browsers support
utf-32? And IE surely doesn't support XHTML, unless you fake it as
old-style HTML.
However W3 validator complains that
"The character encoding specified in the HTTP header (utf-8) is
different from the value in the <metaelement (utf-32). I will use
the value from the HTTP header (utf-8) for this validation."
That's correct.
How can I change the encoding in the header?
This depends on the server.
I don't have access to
change the HTTP server configuration.
Then you don't. But this does not matter, since you shouldn't anyway.
Problem URL:
http://www.quantumcrypto.de/dante/
A quick look suggests that it only uses ASCII characters, so what would
be the point of using utf-32? It would just multiply the size of the
file by 4 and would make browsers and search engines fail to process it.
If you really want to prepare for the inclusion of non-ASCII characters
directly as data, just use utf-8, if you know how to do that.
--
Jukka K. Korpela ("Yucca")
http://www.cs.tut.fi/~jkorpela/ 
