Re: [Nmh-workers] 1.5 release and better repl/MIME handling

[Jon Fairbairn]

Ken Hornstein <address@hidden> writes:

>>>I haven’t been following the discussion very closely, but what strikes
>>>me is, are you saying that it’s difficult to arrange (within mh) that
>>>a different formatproc is called (for each mime part) depending on the
>>>mime type? So your perl script does this?
>
> In a bit of irony, the first time I used this in the "real" world exposed
> a defect.  Specifically, Jon's original message was in UTF-8 and included
> some UTF-8 characters (he used U+2019 as an apostrophe).  My script
> isn't UTF-8 aware and simply spit those bytes out as us-ascii, which
> results in a 3-byte weird sequence where apostrophes were supposed to
> be in the above message.  Sigh; still more work to do!
>
> But I see that Jon's original message was encoded in base64 and I didn't
> even realize it!  Jon, did you do that on purpose just to test me? :-)

No, and I didn’t realise it myself! I read this mailing list
through gmane using gnus, so quite what happens to utf-8 is a
bit of a mystery. In fact, by the time your follow-up got back
to me the apostrophe had turned back into an apostrophe.
(There’s also ó in my name, which means this must be happening
to all my messages. I don’t put it in the From: line to avoid
having that mime encoded, which some news readers [used to?]
mangle)

-- 
Jón Fairbairn                                 address@hidden