Re: lynx-dev outgoing_mail_charset (was: megapatch)

[Henry Nelson]

> We are talking about a way of sending mail where the user has no chance
> to review the translation before it gets sent.  It may have become
> complete garbage, and the user wouldn't be able to notice that

If I am way off base, then please just disregard this.  When I compose
mail (more often news articles) in Japanese, the only way I can do it
"correctly" is to use a vi "macro" (map! ;mk ^[:.,$!/usr/local/bin/enMime)
which converts the euc_jp, which I can read on my display, to iso-2202-jp,
which I cannot read.  That is, I compose the message and then convert it
to a 7-bit form I cannot read until it comes back in the mail, and which
others, even on PCs, can read, too.  I think most Japanese people have
their mail servers set up properly to do this conversion automatically,
but not all of us do (or know how to).

What I am saying is, I would feel more at ease doing the conversion
manually than letting Lynx do it, and let Lynx pass on what it has
gotten from an external editor as is.  The internal editor is a
different issue, it is useless to me, and indeed I don't know for a
fact it even exists for sending mail since I've never used it.

What *would* be nice is a prompt to add the header:
  Content-Type: text/plain; charset=ISO-2022-JP
to the mail, perhaps by a mechanism similar to the ORGANIZATION header.

__Henry