From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 25420@debbugs.gnu.org
Subject: bug#25420: Unknown encoding 8bit;; defaulting to 8bit
Date: Thu, 12 Jan 2017 00:44:28 +0800 [thread overview]
Message-ID: <87mvexzgur.fsf@jidanni.org> (raw)
In-Reply-To: 87vatpx9aq.fsf@jidanni.org
OK I'm sending it to them.
Dear bug-gnu-emacs:
>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:
KY> On Wed, 11 Jan 2017 08:39:21 +0800, 積丹尼さん wrote:
>> [1. application/gzip; smsc.cpio.gz]...
KY> Thanks. I could reproduce the problem; a workaround is below.
KY> Feel free to forward this reply to the Emacs bug list or other.
KY> (defadvice ietf-drums-strip (after remove-garbage activate)
KY> "Remove garbage."
KY> (let ((regexp (concat "[" ietf-drums-tspecials "]+")))
KY> (while (string-match regexp ad-return-value)
KY> (setq ad-return-value
KY> (concat (substring ad-return-value 0 (match-beginning 0))
KY> (substring ad-return-value (match-end 0)))))))
KY> A mail that contains this header
KY> Content-Transfer-Encoding: 8bit;
KY> causes Gnus to issue the following warning:
KY> Unknown encoding 8bit;; defaulting to 8bit
KY> This means that Gnus doesn't know the encoding method named:
KY> 8bit;
KY> Note that this is not "8bit", but "8bit;". This is due to a bug
KY> of a certain mail software. Gnus does no bad. But it is easy
KY> and harmless to make Gnus fix it, so, I think we had better do
KY> something like the above workaround if it generally happens.
KY> I'm not quite sure whether using `ietf-drums-tspecials' is the
KY> right choice, though.
next parent reply other threads:[~2017-01-11 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vatpx9aq.fsf@jidanni.org>
2017-01-11 16:44 ` 積丹尼 Dan Jacobson [this message]
2017-01-12 0:07 ` bug#25420: Unknown encoding 8bit;; defaulting to 8bit Katsumi Yamaoka
2017-01-12 23:51 ` Katsumi Yamaoka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvexzgur.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=25420@debbugs.gnu.org \
--cc=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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).