From: zsh@cs.rochester.edu (Öìʤ»ð)
Subject: re-encode edited article or not
Date: 15 Sep 1998 02:39:48 -400 [thread overview]
Message-ID: <2nogsh516z.fsf@zsh.cs.rochester.edu> (raw)
After a article is edited, gnus-request-replace-article encodes the
article then replaces original one. It works well in general cases.
But when "e" an article which is showed (gnus-summary-show-article)
with argument, i.e. [C-u g] in summary buffer, the article is not
decoded, but encoded when you finish editing, so some MIME headers are
changed. For example, edit this article after [C-u g], the charset
will be changed from "cn-gb-2312" to "us-ascii".
I think a local varible should be added to article buffer to indicated
whether the article has been decoded, so that it can be decided
whether the article needs to be encoded when
gnus-request-replace-article.
--
Shenghuo ZHU(朱胜火)
next reply other threads:[~1998-09-15 6:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-15 6:39 Öìʤ»ð [this message]
1998-09-16 9:29 ` Lars Magne Ingebrigtsen
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=2nogsh516z.fsf@zsh.cs.rochester.edu \
--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).