Author: TomH
[Added to the original trac issue at 11.21am, Wednesday, 12th September 2012]

The "" is a result of your browser treating the page as Latin-1 instead of UTF-8 which is what it actually is. Most likely we need should teach our apache to explicitly state the encoding.

The text is as agreed with LWG this morning.

Don't get me started on what I think about links that force loading in a new tab...

Author: TomH
[Added to the original trac issue at 11.35am, Wednesday, 12th September 2012]

The character set is now being specified by apache, which fixes the misrendering of the copyright symbol.

Author: adjuva
[Added to the original trac issue at 5.31pm, Wednesday, 12th September 2012]

Could it be that this change of apache configuration breaks some other OSM applications? For example the web archive of the mailing lists on list.openstreetmap.org?

http://lists.openstreetmap.org/pipermail/talk-de/2012-September/thread.html

was fine on monday. Now all "Umlauts" are broken.

http says charset is UTF-8, html-meta says it's iso-8859-1 and the data is iso-8859-1.

Firefox 15 and Google Chrome wants to show this page with UTF-8.

On http errors (404) http charset is still iso-8859-1.

Author: TomH
[Added to the original trac issue at 5.59pm, Wednesday, 12th September 2012]

If you have discovered problems with other parts of the OSM infrastructure then please open tickets for them under the appropriate component (probably admin) as what you are reporting is clearly not a problem with the main web site.