Re: [Nmh-workers] Understanding nmh (aka. What's the goal) [ really non-ASCII message bodies ]

[Jon Steinhart]

> markus schnalke wrote:
> > (4) no attachments & non-ASCII -> no MIME; the message contains
> >     non-ASCII chars; the recipient can not know which charset the
> >     non-ASCII chars had been.
> > 
> > To cover case 4, one needs to run mime at the whatnow prompt manually.
> 
> Yes, and I find that annoying.  Most of the time I want to sent non-MIME
> ASCII emails and I do that just fine.  Sometimes my English email will
> mention money, £42, and if I forget to "mime" at whatnow I send a broken
> email.  So far, markus' approach of catching this fourth case sounds
> good.  What's currently happening is wrong AFAICS.
> 
> Cheers,
> Ralph.

Let me try to summarize here because there seems to be lots of energy here
for commentary but little for things that move us forward:

 o  Many people still exclusively use nmh, some have drifted away.  'Nuf said
    on this topic.

 o  There is a general concensus that backward compatibility is important and
    that changes shouldn't break things unless there is a compelling reason.

 o  The particular thing that markus and Ralph want to address is how illegal
    body content is handled.  Fixing this would be convenient.

 o  markus is willing to write code.  Cool!

 o  Nobody objects to markus addressing this issue.  The objections are that
    his implementation breaks things, and handling illegal body content is
    not a compelling enough reason for breaking things.

 o  At least one suggestion (mine) has been floated on a way to implement this
    in a way that does not break things.

So, I think that enough has been said on this topic.  markus, can you outline
for us an implementation that doesn't break things?  I think that everyone will
bless your changes if you do.

Jon

P.S.    I'm trying to honor the way that you're name appears in your mail 
header.
        Do you really want it to be "markus" or should it be "Markus"?