views:

1178

answers:

5

Hi all,

I spent the last few hours getting my website to validate HTML 4.01 Strict and I actually have succeeded in that but there is still one warning which I can't get rid of. The warning is:

Character Encoding mismatch!

The character encoding specified in the HTTP header (iso-8859-1) is different from the value in the element (utf-8). I will use the value from the HTTP header (iso-8859-1) for this validation.

The page in question is www.dubiousarray.net/default.html. As you can see from the page source I have the following meta element:

<meta http-equiv="Content-Type" content="text/html;charset=utf-8">

and I have made sure that the default.html file is saved with UTF-8 encoding. The strange thing is all the other pages in the site validate without this warning and they have the same meta tag and were saved in exactly the same way. I am pretty sure it is something to do with the server config. The .htaccess file looks like this at the moment:

# Use PHP5 as default
AddHandler application/x-httpd-php5 .php
AddDefaultCharset UTF-8

but I have tried all the fixes shown on this page and none of them worked. Does anyone have any ideas on how to go about getting rid of this warning? One last thing, in Firefox if you right click on the page and select 'View Page Info', default.html shows as ISO-8859-1 while all the other pages show UTF-8.

Thanks, Jacob

EDIT: Something else to note is that all the html file have been created and saved in the exact same way (character encoding set to UTF-8 without BOM) but default.html is the only one which isn't displaying as UTF-8. So I assume the server is doing something special to the default.html file though I am not sure what as there is not sign of it in the .htaccess file.

A: 

Can you remove AddDefaultCharset from .htaccess and check the encoding? I saved the HTML source of your webpage and opened it. Encoding was detected as UTF-8. However, on viewing the same webpage served by your webserver, the encoding is ISO-8859-1. That is why I suggest removal of the former redundant rule.

Alan Haggai Alavi
I removed that rule from the .htaccess file as you are right, it does seem redundant, it didn't do anything to fix the problem though.
Jacob de Lacey
+2  A: 

The server is clearly marking the document as ISO-8859-1 in the HTTP headers. Try saving default.html using UTF-8 encoding with a proper editor.

Hannson
The default.html file has been saved as UTF-8 with a proper editor (UTF-8 without BOM to be exact). And I am almost certain that the encoding is correct when I save it as all the other pages on the site are shown as UTF-8 when inspected by Firefox. The server seems to be doing something special to the default.html file.
Jacob de Lacey
+1  A: 

Okay, I have come up with a partial solution to my problem. As it was only the default.html file which was causing the warning I assumed that the server was doing something special to it because of its name. So I made a new file called home.html with the same contents as the default.html file and pointed the .htaccess file to the new file (see line 3 below).

# Use PHP5 as default
AddHandler application/x-httpd-php5 .php
DirectoryIndex home.html
AddDefaultCharset UTF-8

This fixed the problem and all files are now recognised as UTF-8. I'm still not sure what the server was doing to the default.html file or where the settings concerning that are but as my problem is gone I will forget about that.

Jacob de Lacey
+5  A: 

You need to replace the HTTP-level header.

This should work:

<?php 
 header('Content-type: text/html; charset=utf-8'); 
?>

Note that the above must be the FIRST thing in your file. No exceptions. See http://us2.php.net/manual/en/function.header.php

For general info on how to change the character set header in different web stacks, see http://www.w3.org/International/O-HTTP-charset

Larry

Larry K
That looks like it should fix the problem as it comes after the server messes with it but as I no longer have the default.html file that was causing the problem I can't test it. I'm going to assume it would have worked though :-).
Jacob de Lacey
A: 

I love you Larry, it WORKED!