Re: Message forwarding annoyance and message-forward-show-mml

[Shenghuo ZHU <zsh@cs.rochester.edu>]

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic@iskon.hr> writes:

[...]

Hrvoje> Looking for ways to break the legs of "helpful" MML-ification of
Hrvoje> forwarded messages, I stumble upon `message-forward-show-mml'.  Great,
Hrvoje> said I, setting this to nil will surely make things sensible again.
Hrvoje> But what do I get:

Hrvoje>     <$part type=message/rfc822 disposition=inline buffer=" *Gnus forward*<3>">
Hrvoje>     <$/part>
Hrvoje>     (# intentionally transformed to $)

Hrvoje> Now I don't even get to *see* the message I'm forwarding.  If it's not
Hrvoje> MML, I'm not supposed to see it at all lest I be made into a pillar of
Hrvoje> salt by raw MIME.  And I don't even want to know about the "<3>"
Hrvoje> following the buffer name.

Hrvoje> Could this please be fixed to behave sensibly, specifically so that
Hrvoje> pressing `S o m' inserts this:

Hrvoje>     <$part type=message/rfc822 disposition=inline>
Hrvoje>     ... *raw* message (except for quoting of MML-like keywords ...
Hrvoje>     <$/part>

Hrvoje> Pretty please?

What is the definition of the *raw* message?  What if the original
message contains non-ASCII characters or other base64- or qp-encoded
parts?  If not decoded, it is still non-readable.  If decoded, it has
to be re-encoded when you send it.

Shenghuo