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

2017-06-02 Thread Bob Carragher
Whoa. Mind blown. B-) Thanks for the recipe! Bob On Fri, 02 Jun 2017 10:45:55 -0400 valdis.kletni...@vt.edu 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

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

2017-06-02 Thread valdis . kletnieks
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 > >

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

2017-06-02 Thread Laura Creighton
In a message of Fri, 02 Jun 2017 09:10:42 -0400, Ken Hornstein writes: >>Show prints things perfectly, of course. But it caused me to wonder. If >>scan can understand how to print 'Hallén' then surely it could understand >>how to print 'Södermannagatan' as well? > >Sigh. Technically the problem

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

2017-06-02 Thread Laura Creighton
In a message of Fri, 02 Jun 2017 11:40:40 +0100, Ralph Corderoy writes: >Hi Laura, > >> 374 06/01 Jacob Hallén Fang Yuan Shi Wu<> > >I would guess the `From' header encoded `Hallén' and nmh was happy to >decode. Judging by the single question mark, I think the body has a >single byte for th

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

2017-06-02 Thread Ken Hornstein
> > 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. fra

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

2017-06-02 Thread Paul Fox
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.

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

2017-06-02 Thread Ken Hornstein
>Show prints things perfectly, of course. But it caused me to wonder. If >scan can understand how to print 'Hallén' then surely it could understand >how to print 'Södermannagatan' as well? Sigh. Technically the problem is with CHARACTER set encodings, not language encodings (we handle language

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

2017-06-02 Thread Ralph Corderoy
Hi Laura, > 374 06/01 Jacob Hallén Fang Yuan Shi Wu<> I would guess the `From' header encoded `Hallén' and nmh was happy to decode. Judging by the single question mark, I think the body has a single byte for the `ö', but that isn't valid for its stated encoding, e.g. UTF-8. It would be u

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

2017-06-02 Thread Laura Creighton
One of the nice things about scan is that, if the subject line is short, you get something like this: nnn 06/01 Mail SenderSubject<> I got this today. 374 06/01 Jacob Hallén Fang Yuan Shi Wu<> (This is a restaurant in Stockholm where we will meet for lunch.) All fine and good b