http://qa.mandrakesoft.com/show_bug.cgi?id=5398
--- Additional Comments From [EMAIL PROTECTED] 2003-08-09 16:42 ---
OK. There's an issue with text files, but there are many ways to solve this. For
example, we could add this directive in commonhttpd.conf :
AddCharset ISO-8859-1 .txt
which adds the charset parameters to all files with a .txt extension.
Changing the DefaultType directive would be a more definitive solution :
DefaultType text/plain
changed to
DefaultType text/plain; charset=ISO-8859-1
But remember that specifying a default value for the charset is not necessarily
a good thing because it may be different from the charset really used in the
text file.
I think setting AddDefaultCharset to Off would bring more beneficits than drawbacks.
--
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).
