This is driving me nuts. I cannot figure out what it is that I may be doing. Here’s the issue: I’m trying to get a page to validate as XHTML 1.0 transitional using the W3C validator, and I’m getting a persistent error in the encoding:
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.
I have 1) changed the Doc Setup to utf-8, and 2) changed all of the pages, and their masters, to utf-8. I have set the language to none to see if that would make a difference (it didn’t). I can get this to validate if I set the document to Latin1, as well as the pages, but - that isn’t really the right way to do it.
The key must be the iso-8859-1 designation its finding, but I cannot find any way to change the header output to give me a validation, even with all pages set to utf-8.
UPDATE: Changed language to English (Intl) still no change. On a related note, I removed the anti-spam action, which encodes the email addresses in PHP, because it wasn’t validating. I’m assuming the email hiding button in the doc setup more or less kinda/sorta does the same thing.
Anyway, it validates with a warning now - still have this encoding issue.
UPDATE: I think this issue isn’t related to my FW file, specifically. I am thinking that the .htaccess file on my server is configured to return an iso-8859-1 by default, which accounts for my error warning, and the full validation when I set the page and the masters to Latin1.
So - the solution would be to add an .htaccess file with AddDefaultCharset Off. Or, perhaps it would be better by doing this in PHP.
My question at this point would be: is it necessary to have XHTML 1.0 (transitional) pages set to utf-8 encoding, or is this whole thing a waste of time? Several sources suggest that the XHTML specification isn’t correct unless set to utf-8.