From: James Cloos <cloos@jhcloos.com>
To: 464@emacsbugs.donarmstrong.com
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, ding@gnus.org
Subject: Re: bug#464: 23.0.60; [Regression] Implicit utf-8 no longer correctly decoded in gnus
Date: Thu, 03 Jul 2008 17:29:49 -0400 [thread overview]
Message-ID: <m37ic2wt97.fsf@lugabout.jhcloos.org> (raw)
|> I haven't hit on a utf-8 quoted-printable so am not yet sure whether
|> those work, but I suspect they would.
Just hit a qp and, indeed, they do work.
So it is in fact only mail with Content-Transfer-Encoding: 8bit which
now fail, but which used to work as of four to eight weeks ago, or so.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
next reply other threads:[~2008-07-03 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 21:29 James Cloos [this message]
2010-09-30 17:36 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2008-07-03 21:08 James Cloos
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=m37ic2wt97.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=464@emacsbugs.donarmstrong.com \
--cc=ding@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).