Hi, * Thomas Roessler [06-06-09 14:18:08 +0200] wrote:
On 2006-06-09 12:08:20 +0000, Rocco Rutte wrote:
So we have a bug here since mutt knows of "aliases" for character sets, i.e. a mapping of commonly used non-MIME names to MIME names. And as this table contains"ANSI_X3.4-1968", mutt should properly map it to "us-ascii".
But when I look at the table in charset.c, there're more special characters...
Well, mutt should never be sending the special characters, and whatever software did send the ANSI_X3.4-1968 thingy actually violated the MIME spec by doing so.
No bug on mutt's side here, I think.
Hmm. But what's the point behind having ANSI_X3.4-1968 in our compatbility recognition in charset.c if rfc2047.c will never extract it so that there's no chance of it being looked up?
Note: I didn't check if that's the only place where the aliases for character set names are resolved to official MIME names. But if, it's superflous to define these in charset.c
Well, it's not a real bug, just confusing that mutt can't handle it though it already knows what ANSI_X3.4-1968 is and has code to find that out...
bye, Rocco -- :wq!