http://qa.mandrakesoft.com/show_bug.cgi?id=5398
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
------- Additional Comments From [EMAIL PROTECTED] 2003-08-09 15:33 -------
As discussed somewhere else yesterday, the problem is for plain text files which
would get no charset which is annoying...
If a japanese guy look at a txt file on your server how will its browser guess
it is iso-8859-15 ?
Maybe the default charset should remain for text/plain but not for text/html,
xml, wml, ...
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEW
creation_date:
description:
According to http://www.w3.org/TR/html401/charset.html#h-5.2.2 and
http://httpd.apache.org/docs-2.0/mod/core.html#adddefaultcharset when a charset
parameter is specified in the Content-Type HTTP header sent by the server, it
overrides the charset specified in the <meta> tag of the HTML document.
Apache shipped with Cooker has the directive AddDefaultCharset set to
"ISO-8859-1" (see commonhttpd.conf). Consequently, all HMTL documents are
considered as ISO-8859-1 documents by conforming web browsers such as Mozilla,
even if they are UTF-8 or Windows-1252 documents according to their <meta> tag.
This behavior, though not severe, is a bit irritating because in most case (if
not all) the <meta> tag reflects the correct character set for the document.
Therefore, the AddDefaultCharset directive should be set back to its default
value (Off).
