== Bad Character Encodeing of www.cacert.org and CAcert emails == A users writes: {{{ Could you this tag (at the end of this message) between this head tags of the french page(s) ? This page is coded in UTF-8 but the browsers try to decode it using iso-8859-1 charset, which leads to dreadful looking. Thank you in advance }}} chris@sirona tmp $ telnet cacert.org 80 {{{ Trying 202.87.16.201... Connected to cacert.org. Escape character is '^]'. GET / HTTP/1.1 Host: www.cacert.org HTTP/1.1 200 OK Date: Sun, 03 Jul 2005 09:50:49 GMT Server: Apache/1.3.33 (Debian GNU/Linux) mod_gzip/1.3.26.1a PHP/4.3.9-1 mod_ssl/2.8.22 OpenSSL/0.9.7d X-Powered-By: PHP/4.3.9-1 Set-Cookie: cacert=3a1dd53fdbba6cdc85f473a8b8a243eb; path=/ Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Transfer-Encoding: chunked Content-Type: text/html; charset=iso-8859-1 }}} A users write {{{ There may be Umlauts in emails sent via the contact form (see attached mail for an example), but there's no charset given, so the Umlauts are scrambled. The most simple solution is probably to take the charset information sent by the browser and put it into the Content-Type header of the email. }}} == Comments == The issue appears to be an obscure browser not honouring html entities properly. * ?? Set Status to ''Open, 2005-07-02'' * Duane set status to ''Closed, pending further feedback, 2005-07-22''