Re: mhfixmsg character set conversion

[Valdis Klētnieks]

On Sun, 06 Feb 2022 09:26:14 -0800, David Levine said:

> Ok, commit 41ce4490ac5d might fix the problem for you.  The cause
> was mismatch between the character set of content generated by the
> external program (lynx, in this case) and mhfixmsg -textcharset
> UTF-8.  mhfixmsg wasn't capturing the charset of the generated
> output, assuming it was unchanged.  It then converted it again.

So I did a 'git pull', and 'git show HEAD' reports:
commit 51f9b175b18f4f37ebc7a5135346c7f3433cf100 (HEAD -> master, origin/master, 
origin/HEAD)
Author: David Levine <levinedl@acm.org>
Date:   Sun Feb 6 11:37:22 2022 -0500

    Fixed charset determination code.
    
    Fix to commit 41ce4490ac5d5c6a25240c4101cacefa16d885eb.

And I'm seeing 2 failures in 'make check',  am attaching the output from 'make
check |& tee check.output' as a gzip to avoid any possible charset wonkiness...

I also hit a third error, but I *think* it's just 'par' not being installed. I 
wonder
where it went, I'm pretty sure I installed it somewhere along the line.  In any
case, test-convert's message isn't correct, as the directory 
/home/valdis/src/nmh/test/testdir/Mail/
doesn't exist, and the file 'draft' is obviously not in the non-existent 
directory.

check.output.gz
Description: check.output.gz