So the short answer is yes, use mhfixmsg, but I think the only long-term
solution is to make nmh tools smarter.
So what exactly is your recommendation for now? I think mhfixmsg is a
powerful and useful tool, but I can't use it as I cannot edit the
resulting files as my favorite editor gets confused over the mix of
character sets in a single file.
Weeelll ... dumb question time. Why do you want to edit an 'email message'
with your editor, anyway?
Let me point out this gets back to the core problem I eluded to in my
previous message: you're trying to use a text processing tool (vim) on a
RFC-5322 format file, which does not not meet the definition of a text
file. So, yeah, it doesn't work well. It kinda worked before, but you
weren't guaranteed that it would and now it doesn't.
If your goal is to display a message, show (really, mhshow) does that.
If your goal is to extract a particular piece of content into a 'text file',
mhstore does that.
I do not believe that we can just arbitrarily convert text/html into
another character set without some knowledge of HTML (but I could be
wrong about that).
So should I kind of file a "feature request" to add some option to
mhfixmsg that makes it decode "text/plain" only, while leaving other
text parts (like "text/html" in my case) alone?
[Or an option that allows to pass a list of Content-Types which shall
be processed, something like "-decodeparts text/plain,text/html" ?]
Either one of those options is reasonable; since mhfixmsg is really David's
show then he should be the one to decide which one is appropriate.
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers