Header fields should be RFC 2047-decoded before any MH operation that
considers the content of the message, including pick, shouldn't they?
Is that a rhetorical question? :-)
In a perfect world, yes, that would happen. But RFC 2047 support wasn't
integral to MH; it got grafted on after MH development stopped, but
before we moved nmh to savannah. It was actually only implemented in
the format engine with the %(decode) function.
Besides the issue of dealing with decoded strings internally, there
are other problems as well. For example, we don't have a RFC 2047
encoder, so if we (for example) decode a subject line we have no
way of encoding it properly.
So right now anything that wants to handle decoded headers has to take
care of that itself. Everything so far that has done that uses the
format engine.
--Ken
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers