[#83] Wrong encoding on project home pages

Date:
2006-04-12 07:46
Priority:
2
State:
Closed
Submitted by:
Sascha Wilde (wilde)
Assigned to:
Sascha Wilde (wilde)
Summary:
Wrong encoding on project home pages

Detailed description
Reported on 11. April 2006 by Johannes Kastl:

when visiting e.g. gpg4win.wald.intevation.org the encoding is wrong.
See for example the imprint.

Analysis:

The declaration in the html header is correct:
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

but the server sends UTF8 as encoding in the http header:
Content-Type: text/html; charset=UTF-8
Message  ↓
Date: 2019-10-04 13:43
Sender: Thomas Arendsen Hein

This works on the pages I have checked.
The gpg4win home page is now served by a different web server anyway.

Date: 2014-01-10 10:11
Sender: Sascha Wilde

The problem still persists, but after some closer investigation it
seems to be quite local to on (or maybe a few) pages:

- only http://gpg4win.wald.intevation.org/ is affected, but not
http://gpg4win.wald.intevation.org/index-de.html
http://gpg4win.wald.intevation.org/index.html
or any other subpages I checked.

In all the later cases no charset is given in the HTTP-Headers, and
so the http-equiv is used.

(Note: "real" http headers take precedence over http-equiv in meta
tags. Both: according to standards and to my tests.)

- I wrote "but most modern Browsers seem not to care" in 2010, this
is not true (anymore?): Looking at
http://gpg4win.wald.intevation.org/ the wrong charset in the http
header leads to the "»" signs used on the page being garbled (look
behind the "About Gpg4win" link for an example).

- I still don't understand why in this one case
(http://gpg4win.wald.intevation.org/) the server includes an charset
in the http headers (and on top of that a wrong one) while it
doesn't in the other cases I tested. Mathias, maybe you can try to
analyze this some time..?

Date: 2010-01-05 10:44
Sender: Sascha Wilde

Technically the reported problem still persists:

GET / HTTP/1.1
Host: gpg4win.wald.intevation.org

HTTP/1.1 200 OK
Date: Tue, 05 Jan 2010 10:33:01 GMT
Server: Apache/2.0.54 (Debian GNU/Linux) DAV/2 SVN/1.1.4 mod_python/3.1.3 Python/2.3.5 PHP/4.3.10-22 mod_ssl/2.0.54 OpenSSL/0.9.7e
X-Powered-By: PHP/4.3.10-22
Content-Length: 7363
Content-Type: text/html; charset=UTF-8

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd";>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

[...]

but most modern Browsers seem not to care -- so the problem is not too visible.

Date: 2008-04-02 15:40
Sender: Bernhard Reiter

We probably have to split out the viewcvs problem with
text/plain; charset=iso-8859-1.
I have tried svn and looked up viewcvs.
Setting svn:mime-type text/plain; charset=iso-8859-1
is allowed, but does not change the result.
the viewcvs code snapshot from yesterday does not seem
to have provisions for svn:mime-type nor a charset coming from there.

Date: 2008-04-02 14:39
Sender: Bernhard Reiter

Currently I do not see encoding problems on http://gpg4win.wald.intevation.org/index-de.html
is the problem still there?

I do have encoding problems with something like
http://wald.intevation.org/plugins/scmsvn/viewcvs.php/trunk/doc/README-BETA-de.txt?rev=763&root=gpg4win&view=auto
where UTF is send by the server, but latin1 is the encoding. (I wonder if SVN has a way to denote this and viewcvs will followup on it.)

No attached documents

Field Old Value Date By
status_idOpen2019-10-04 13:43Thomas Arendsen Hein
close_dateNone2019-10-04 13:43Thomas Arendsen Hein
assigned_tomgebbe2015-01-07 15:49Bernhard Reiter
priority32014-01-10 10:11Sascha Wilde
assigned_towilde2014-01-10 10:11Sascha Wilde
priority42010-01-05 10:44Sascha Wilde
assigned_tonone2008-04-02 14:39Bernhard Reiter