Re: Can mutt handle message not encoded in current locale?
Henry Nelson <henry <at> irm.nara.kindai.ac.jp>
2003-01-01 02:45:56 GMT
> > [...] but it was rendered just as euc-jp.
> Good! Your filter converted my SJIS to what?
EUC-JP (That way, on any of my Un*x machines, whether it runs
NetBSD1.4 or 1.5, SunOS4.1.3, Solaris2.6 or old Linux, I can use
any native tools, assuming proper locale, especially `vi', to handle
the file after it is saved by mailx. I can also login to any of
these machines from any other and maintain a sane state.)
BTW, I recently received a mail with body in sjis and with no
charset header. My procmail filter, which as I told you looks for
specific patterns in the body, was not triggered. The matching rule
works on a weighted basis, so I lowered the score to one match per
ten lines, rather than one per four lines. It's still plenty
conservative that I will not get false positives. I've also added
a formail action to insert a charset=euc-jp content-type header.
Anyway, why I mention it is that the Japanese-patched mutt on my
NetBSD machine was not able to convert it (all rendered as "???").
After running through my filter, mutt handled it fine. I think it
means I will still need to keep the sjis filter around even when
I am able to switch completely to mutt.
One more thing I wanted to ask is: do you know how to have mutt
save read emails in a particular encoding? Specifically, I want
mutt to save all _Japanese_ emails, i.e., encoded in either euc-jp
or, more likely, iso-2022-jp, in euc-jp. If the files are saved
in iso-2022-jp, then on some machines they will not be legible. I
don't want mutt to try to save plain ascii files in euc-jp, however.