From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Message forwarding annoyance and message-forward-show-mml
Date: 02 Jun 2000 09:50:37 -0400 [thread overview]
Message-ID: <2n7lc8mbte.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Hrvoje Niksic's message of "02 Jun 2000 15:31:29 +0200"
Hrvoje Niksic <hniksic@iskon.hr> writes:
> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
>
> > What is the definition of the *raw* message?
>
> Un-decoded, un-MML-ified, the way it is seen in the mailbox or
> delivered by NNTP.
>
> > What if the original message contains non-ASCII characters or other
> > base64- or qp-encoded parts?
>
> Leave base64 and qp parts as they are. Non-ASCII characters should
> also be left as they are (their octet values unchanged), making sure
> that no additional (en|de)coding happens.
I recall the problem in forwarding an 8-bit-encoded message. The
8-bit raw text (esp. koi8-r and utf-8) might not be safe in an
Emacs/MULE multibyte buffer. That's why the original text is put into
an external buffer.
Shenghuo
next prev parent reply other threads:[~2000-06-02 13:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-02 7:50 Hrvoje Niksic
2000-06-02 12:52 ` Shenghuo ZHU
2000-06-02 13:31 ` Hrvoje Niksic
2000-06-02 13:50 ` Shenghuo ZHU [this message]
2000-06-02 13:51 ` Hrvoje Niksic
2000-06-02 14:08 ` Shenghuo ZHU
2000-06-03 15:28 ` Hrvoje Niksic
2000-06-03 17:55 ` Shenghuo ZHU
2000-06-04 11:13 ` Hrvoje Niksic
2000-06-04 13:02 ` Shenghuo ZHU
2000-06-04 19:29 ` Hrvoje Niksic
2000-06-04 20:31 ` Shenghuo ZHU
2000-06-05 7:02 ` Hrvoje Niksic
2000-06-05 14:31 ` Shenghuo ZHU
2000-06-27 13:08 ` Dave Love
2000-06-27 13:31 ` Shenghuo ZHU
2000-06-28 17:14 ` Dave Love
2000-06-27 13:04 ` Dave Love
2000-06-03 19:44 ` Vladimir Volovich
2000-06-02 20:50 ` Russ Allbery
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2n7lc8mbte.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).