Anand Buddhdev writes:
Sam Varshavchik wrote:
Yes, and no. Character sets are meant to be shown in this fashion, in some circumstances. It remans to be seen whether this should happen in this specific instance.
Ok, the header looks like this:
From: =?iso-8859-1?q?Jean=20Swallow?= <[EMAIL PROTECTED]
I've deliberately left out the domain part to stop the address being harvested. So what is the reason for showing the character set in this case?
A few possible reasons are the browser using some character set other than iso-8859-1, or utf-8; or the --disable-unicode option was used to build sqwebmail.
My browser (firefox 0.8) sends:
ISO-8859-1,utf-8;q=0.7,*;q=0.7
in the accept charset HTTP header. And I did *not* build sqwebmail with the --disable-unicode option.
In this case the character set tag should not be necessary.
So it's a bug in sqwebmail?
I would describe it as "undesirable behavior". It is not a technical defect, just something that should be handled a little bit better.
pgpKJg4ZJdXFq.pgp
Description: PGP signature
