On Mon, 18 Mar 2019 21:10:45 -0400, Ken Hornstein said:
> But the email you sent out was marked as having a character set of UTF-8
> with characters encoded as ISO-8859-1. Dude, I know you could do better
> (also, I am puzzled as to how that happened; I think with nmh you'd have
> to work to make
Valdis wrote:
> Deciding whether the detection of an issue should
> be in the bse64 decoder or elsewhere is bikeshedding compared to trying
> to decide what semantics you want..
Identifying whether the issue is due to invalid base64 characters or due to an
improperly constructed MIME part is pre
>With irony, in a discussion about how to handle bad encodings in
>mail, I found that I could not read this message by Valdis Klētnieks
>https://lists.nongnu.org/archive/html/nmh-workers/2019-03/msg00023.html
>
>Something bad seems to have happened to his encoding of a '§'.
Here are my thoughts ab
With irony, in a discussion about how to handle bad encodings in mail, I
found that I could not read this message by Valdis Klētnieks
https://lists.nongnu.org/archive/html/nmh-workers/2019-03/msg00023.html
Something bad seems to have happened to his encoding of a '§'.
Now, my .mh_profile says (a
