Dear Ken,
In message
<20160127155252(_dot_)1F0D93C244(_at_)pb-smtp0(_dot_)pobox(_dot_)com> you wrote:
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.
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" ?]
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd(_at_)denx(_dot_)de
Let's say the docs present a simplified view of reality... :-)
- Larry Wall in
<6940(_at_)jpl-devvax(_dot_)JPL(_dot_)NASA(_dot_)GOV>
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers