Ken Hornstein k...@pobox.com writes:
I've been living with par as my formatproc for a while now, and for
simple cases it's been great. But it has some unfortunate side effects.
It works okay on more modern messages designed to be reflowed (although
I still get q-p equal signs sprinkled
Ken wrote:
Okay, so I am thinking that perhaps we are close to ready to start the
1.5 release cycle; I don't have anything else on my plate that I'd like
to see in there. So if anyone else has any code they would like to see
in nmh for 1.5, now is the time they should speak up!
I'd prefer
But that got me to thinking - maybe I could have a more intelligent
formatproc that could handle MIME?
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
Shouldn't take much more than
#after opening for reading
binmode(IFH, ':utf8');
#before writing
binmode(OFH, ':utf8');
to fix your formatting script.
If adding perl dependency, you'll need to require at least 5.6.1
for utf8, although 5.8 or better yet 5.10 would be preferable;
perl may
Shouldn't take much more than
#after opening for reading
binmode(IFH, ':utf8');
#before writing
binmode(OFH, ':utf8');
to fix your formatting script.
That's not the problem; the perl script handled UTF-8 just fine. It's
just that nmh didn't know what to do with it.
--Ken
Lyndon Nerenberg lyn...@orthanc.ca writes:
On 2012-03-26, at 15:05 PM, Ken Hornstein wrote:
Weren't you and Paul Vixie supposed to be working on that?
Not me. I have other things I'm not working on!
This is one of the funnier lines I've read in a while :-).
--
Bill Wohler woh...@newt.com
On Fri, 30 Mar 2012 23:51:05 -0400, Ken Hornstein said:
But that got me to thinking - maybe I could have a more intelligent
formatproc that could handle MIME? Since the formatproc only has
access to the message body (don't ask; that is NOT easily fixable),
It's not as bad as all that - if
It's not as bad as all that - if you have the entire body handy, about the only
three things that you'd really need are the C-T-E from the main headers, the
main MIME type, and if it's a multipart/*, what the bodypart boundary string
is. And your Perl script already does 2 of those.
Actually,
I'll likely continue to use it until nmh's MIME handling
is redone to support the registration of custom formatters
based on a MIME entities content-type. It is not only
multipart bodies that reply needs to deal with, but
media-types like text/html which is becoming more
prevalent as time goes
