I believe adding AddDefaultCharset was a bad idea. It is only to be
used if one _knows_ that the files have that charset, which we
definitely don't.
It also overrides two out of three valid ways to specify the charset
of a page: the meta tag and type maps (see #414429). Only the way
via
[EMAIL PROTECTED]
Log:
Don't use AddDefaultCharset for our docs
You know, I think I agree with those (including you, I notice, reading
#415775 again) who say we shouldn't be using AddDefaultCharset _at
all_. The issue came up a bit too late for etch, but I think for lenny
it is reasonable to
On Dienstag, 26. Juni 2007, Peter Samuelson wrote:
but I think for lenny
it is reasonable to remove /etc/apache2/conf.d/charset and leave
only the commented line in /etc/apache2/apache2.conf.
ok. Maybe we can change that together with the change
of /etc/default/apache2 to a conffile and the
#
# bts-link upstream status pull for source package apache2
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #294648
# * http://issues.apache.org/bugzilla/show_bug.cgi?id=14090
# * remote status changed: (?) - NEW
#
# bts-link upstream status pull for source package apache2
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user [EMAIL PROTECTED]
# remote status report for #353443
# * http://issues.apache.org/bugzilla/show_bug.cgi?id=12355
# * remote status changed: REOPENED -
5 matches
Mail list logo
