Re: [Nmh-workers] A € for your thoughts - should we fix UTF-8 subject output in scan for 1.5?

[Ken Hornstein]

>Considering that this has never worked before, it seems a bit late in
>the release cycle to be fixing it post-RC2.

Well, I guess it depends on your perspective.  Is this a portability
problem?  Linux (the one I tested) returns 0 for isspace() &&
iscntrl() > 127.  If that's true for you, it works fine.

It may be that fixing cpstripped() (works for some systems, not
others) is one problem and fixing the scan output (has never worked
for anybody) is another problem.  Let's just consider the former:
fix for 1.5 or not?

--Ken