Re: [Nmh-workers] scan doesn't appear to understand language encodings

[Bob Carragher]

Whoa.  Mind blown.  B-)

Thanks for the recipe!

        Bob

On Fri, 02 Jun 2017 10:45:55 -0400 address@hidden sez:

> On Fri, 02 Jun 2017 09:19:25 -0400, Paul Fox said:
> > ken wrote:
> >  > scan can't decode the body of a message; you get the raw text output.
> >  > Which is why you see the beginning of the MIME multipart marker if your
> >  > message is a multipart.  Why can't scan do that?  Because no one made it
> >  > do that.  SHOULD it do that?  Yes, ...
> >
> > i'm not sure i agree.  frankly, the first-line snippet that scan
> > provides instead of a subject is hardly useful enough to be worth it.
> > i'd be just as happy if scan <<Missing Subject>> or somesuch.
> 
> The tail end of my usual scan format:
> 
> %(decode{subject})\
> %(void{content-type})\
> %<(match multipart)\
> %?(match text/html)\
> %|%<{body} <<%{body}%>\
> %>
> 
> In other words, if the outermost MIME time is multipart/* or text/html,
> don't bother with using %body to display the first 10-50 chars of the
> body (depending how long the  Subject: line was).  That deals with 99% of
> the problem.
> _______________________________________________
> Nmh-workers mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/nmh-workers