Need to answer post above...
A quick one though.
The index template declares this in the header: <meta charset="utf-8">
However, SMF/Wedge already specifies the charset in the *HTTP headers*. So I boldly tried to remove the line and... It worked. However, when validating the page, while it's seen as valid, it adds a warning that I should be specifying the charset in the document itself, to help people view the files offline (save to disk).
It absolutely makes sense, I'd say. But I still don't see the point in having the charset specified twice.
So I'm wondering... Wouldn't it make sense to just skip specifying the charset in the http headers, and focus on the document itself?
The only drawback, AFAIK, is that anything before the charset declaration might be seen as ISO, but then again, I used to have '©' in the copyright line, and it wasn't correctly output, even though the headers declared the charset correctly. This is why I rewrote it to use (c) instead. So at this point, I'm not sure declaring charsets in http headers has any point... (?)
A quick one though.
The index template declares this in the header: <meta charset="utf-8">
However, SMF/Wedge already specifies the charset in the *HTTP headers*. So I boldly tried to remove the line and... It worked. However, when validating the page, while it's seen as valid, it adds a warning that I should be specifying the charset in the document itself, to help people view the files offline (save to disk).
It absolutely makes sense, I'd say. But I still don't see the point in having the charset specified twice.
So I'm wondering... Wouldn't it make sense to just skip specifying the charset in the http headers, and focus on the document itself?
The only drawback, AFAIK, is that anything before the charset declaration might be seen as ISO, but then again, I used to have '©' in the copyright line, and it wasn't correctly output, even though the headers declared the charset correctly. This is why I rewrote it to use (c) instead. So at this point, I'm not sure declaring charsets in http headers has any point... (?)


