-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, November 14 at 09:49 PM, quoth Dave Feustel:
>All I get when pager displays the following message is a lot of /xxx
>codes.
Officially, that's correct. That message is malformed. The content of
email messages are required to be US-ASCII unless otherwise specified.
That said, mutt can attempt to *guess* what the right character set
is. Now, I don't know much about Korean, so I can't attempt to render
it and then decide if the result is gibberish or not, but judging by
the From header, my guess would be that the body of the email is
probably encoded in EUC-KR (or possibly even windows-949). You can try
adding that to your $assumed_charset list.
A word of caution: adding EUC-KR to the $assumed_charset list can
prevent mutt from correctly guessing malformed emails with Western
character sets (it may incorrectly guess that messages are in EUC-KR).
So, if you don't usually get Korean email, that may not be something
you want to do. Then again, if you do sometimes get Korean email,
adding EUC-KR to your $assumed_charset list will probably be a good
thing. If you decide to add it to your configuration, I *think* you
probably want to add it to the *end* of the $assumed_charset list.
~Kyle
- --
It was we, the people; not we, the white male citizens; nor yet we,
the male citizens; but we, the whole people, who formed the Union.
[...] Men, their rights and nothing more; women, their rights and
nothing less.
-- Susan B. Anthony
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkkdsPwACgkQBkIOoMqOI15cTgCfSb+PeRfRriQRQ6w9Rk/VnkUI
d2cAoJ189bYNrkP3odoPz7k25NWW+bYj
=zuCC
-----END PGP SIGNATURE-----
