From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: sending delayed articles bug
Date: Fri, 25 Oct 2002 21:25:02 +0900 [thread overview]
Message-ID: <yotl7kg6yach.fsf@jpl.org> (raw)
Hi,
Someone found a bug while using the gnus-delay feature that
delayed articles won't be MIME encoded even if they contain
Japanese text. I've fixed it.
The function nndraft-request-article used the coding-system
emacs-mule or escape-quoted for reading articles from the
nndraft:drafts group but raw-text for the nndraft:delayed group.
However, the coding-system raw-text is for queued articles.
Therefore, especially in FSF Emacs, broken mails have been sent.
I've made the function use emacs-mule or escape-quoted even for
delayed articles.
By the way, why don't we use the universal coding-system, e.g.
iso-2022-7-bit, for saving and reading draft articles in both
FSF Emacs and XEmacs? In the present, FSF Emacs uses emacs-mule
and XEmacs uses escape-quoted by default, so draft articles made
by FSF Emacs can't be handled by XEmacs and the contrary is also
bad. :-{
--
Katsumi Yamaoka <yamaoka@jpl.org>
next reply other threads:[~2002-10-25 12:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 12:25 Katsumi Yamaoka [this message]
2002-10-25 13:01 ` Kai Großjohann
2002-10-29 9:58 ` coding-system for drafts (was Re: sending delayed articles bug) Katsumi Yamaoka
2002-10-29 14:27 ` coding-system for drafts Kai Großjohann
2002-10-30 1:36 ` Katsumi Yamaoka
2002-10-30 10:15 ` Kai Großjohann
2002-10-30 12:28 ` Katsumi Yamaoka
2002-10-30 16:14 ` Kai Großjohann
2002-10-31 4:44 ` Katsumi Yamaoka
2002-10-31 7:35 ` Katsumi Yamaoka
2002-10-31 17:35 ` Kai Großjohann
2002-11-01 4:32 ` Katsumi Yamaoka
2002-11-05 12:36 ` Kai Großjohann
2002-10-31 17:30 ` Kai Großjohann
2002-11-01 17:49 ` Kai Großjohann
2002-11-05 9:23 ` Katsumi Yamaoka
2002-11-05 12:38 ` Kai Großjohann
2002-11-08 7:25 ` Katsumi Yamaoka
2002-11-13 16:14 ` Reiner Steib
2002-11-02 15:34 ` TSUCHIYA Masatoshi
2002-11-05 12:23 ` Kai Großjohann
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=yotl7kg6yach.fsf@jpl.org \
--to=yamaoka@jpl.org \
/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).