Originally Posted by pete_1967
1- warrior ads Windows-1252 encoded text to a file that may or may not be saved in utf-8, Windows-1252 or any other encoding
2- On his page, he ads instruction to browser to encode the page in iso-8859-1
3- server encodes the page in utf-8
OK, now I see where you are confused. The Apache HTTP server doesn't
re-encode the files, unless you use the experimental mod_charset_lite output filter (which isn't icluded in FC6). The data is sent encoded in whatever way it was saved in step 1, and httpd adds the encoding headers simply based on its configuration files, not the actual data it transmits.
When the headers don't match the actual encoding of the saved data, the results displayed by the browser are as seen on the example page.