Martin Marques wrote: > On Tue, 14 Mar 2006 7:57:59 -0300, Martin Marques <martin@bugs.unl.edu.ar> > wrote: >> When ever I go back to the INBOX screen, say from seeing a message, or >> from a composing message that just got sent, the default encoding changes >> from UTF to ISO-8859-1. > > Sorry, this wasn't totaly accurate. This behaviour only happens when sending > a composed message. When it gets back to the INBOX it switches encoding.
Hmmh, seems that the encoding behavior is different from GET to POST method. The 0.1beta has the following line in the .htaccess file: AddDefaultCharset UTF-8 I thought that this would solve the encoding problem in general (at least on Apache servers) > >> Also, even when the UTF encoding is correctly set, if a message comes in >> with ISO-8859-1 encoding, it's not converted, and so, it's not viewed >> correctly. > > This is also true. If a message specifies it's charset in the Content-Type header, RC will attempt to convert it to UTF-8. This does not work for HTML messages that have chars encoded with html entities. A decoding function handling html entities has to be written for that. Anyone? Regards, Thomas
