From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Message contains characters with unknown encoding. Really send? (y or n)
Date: Thu, 16 Jul 2009 10:52:04 -0500 [thread overview]
Message-ID: <87prc0pqvv.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mab35r2j8.fsf@jpl.org>
On Thu, 16 Jul 2009 07:42:51 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>>>>>> Reiner Steib wrote:
>> On Wed, Jul 15 2009, Ted Zlatanov wrote:
>>> On Mon, 13 Jul 2009 20:25:33 +0800 jidanni@jidanni.org wrote:
j> There I was, using NNRSS, when I was asked
j> "Message contains characters with unknown encoding. Really send? (y or n)"
KY> [...]
KY> It's issued by `mml-to-mime' that nnrss uses for making a MIME
KY> article from html data. The sequence is:
KY> nnrss-request-article
KY> mml-to-mime
KY> message-encode-message-body
KY> mml-generate-mime
KY> mml-parse
KY> mml-parse-1
KY> If html data contain funny characters, maybe as MML functions are
KY> assumed to be used for message sending, such a prompt is issued.
KY> The possible solutions might be:
KY> 1. Allow nnrss to generate articles with no query even if it might
KY> cause unreadable articles.
KY> --- nnrss.el~ 2009-01-22 08:09:02 +0000
KY> +++ nnrss.el 2009-07-15 22:41:29 +0000
KY> @@ -313 +313,3 @@
KY> - (mml-to-mime)
KY> + (let ((mml-confirmation-set
KY> + (cons 'unknown-encoding mml-confirmation-set)))
KY> + (mml-to-mime))
KY> 2. Make the prompt message general, like:
KY> "...Really send? (y or n) " -> "...Continue? (y or n) "
KY> I vote for 1.
My vote is for 1 as well. Thanks for looking into this!
Ted
prev parent reply other threads:[~2009-07-16 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 12:25 jidanni
2009-07-15 16:07 ` Ted Zlatanov
2009-07-15 18:11 ` Reiner Steib
2009-07-15 22:42 ` Katsumi Yamaoka
2009-07-16 15:52 ` Ted Zlatanov [this message]
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=87prc0pqvv.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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).