Hi Joel,
I find it gives the behaviour you describe if the HTML file contains a
charset declaration that's incorrect for the content of the HTML, e.g.
ISO-8859-1 when mhstore shows the glyph is UTF-8 encoded. Lynx obeys
the charset in the file. Might be worth searching for `charset' in the
HTML you've got. I receive many such broken HTML emails.
The MIME part has this:
Content-Type: text/html; charset=UTF-8
The HTML in the MIME part has *no* encoding declaration, e.g.:
<?xml version="1.0" encoding="UTF-8"?>
And if you search for `charset'? For example,
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Perhaps see if you can get `lynx -dump' as specified in your
~/.mh_profile to give correct output on a HTML file you create, feeding
the output to cat one time and less another.
Cheers, Ralph.
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers