(Imported from Trac #767, reported by andersk on 2010-11-19)
On hackage.haskell.org, when you browse the source of a module that contains Unicode (e.g. Data.Eq.Unicode), it is sent with a Content-Type: text/html header with no charset. There is a charset in the XML declaration <?xml version="1.0" encoding="UTF-8"?>, but that is ignored by Firefox because of the non-XML Content-Type. Therefore, the wrong encoding is detected and the Unicode symbols get mangled.
Possible fixes include sending Content-Type: text/html; charset=UTF-8, or sending Content-Type: application/xhtml+xml so that the XML declaration is respected , or both (Content-Type: application/xhtml+xml; charset=utf-8), or adding equivalent <meta http-equiv="Content-Type"> tags.
(Imported from Trac #767, reported by andersk on 2010-11-19)
On hackage.haskell.org, when you browse the source of a module that contains Unicode (e.g. Data.Eq.Unicode), it is sent with a Content-Type: text/html header with no charset. There is a charset in the XML declaration <?xml version="1.0" encoding="UTF-8"?>, but that is ignored by Firefox because of the non-XML Content-Type. Therefore, the wrong encoding is detected and the Unicode symbols get mangled.
Possible fixes include sending Content-Type: text/html; charset=UTF-8, or sending Content-Type: application/xhtml+xml so that the XML declaration is respected , or both (Content-Type: application/xhtml+xml; charset=utf-8), or adding equivalent <meta http-equiv="Content-Type"> tags.