Re: Curiose encoding...
On 2006-06-09 13:05:17 +0000, Rocco Rutte wrote:
> 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?
That table is, among other things, used to map locale charsets
to MIME charsets. It's not at all unnecessary.
> 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...
What mutt can't handle are malformed RFC 2047 encodings. Some
character set identifiers that mutt knows about for locale
purposes can't show up in RFC 2047 encoded strings legitimately.
That's all.
--
Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.