From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 7410@debbugs.gnu.org
Subject: bug#7410: Impossible multibyte->unibyte conversion
Date: Tue, 10 Apr 2012 22:59:11 +0200 [thread overview]
Message-ID: <m3398bwbfk.fsf@stories.gnus.org> (raw)
In-Reply-To: <m37gxnwbov.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 10 Apr 2012 22:53:36 +0200")
Found the real bug. The `gnus-article-wash-html' had parsed the
displayed article, and not the original one, so it was missing charset
info (and stuff). Now fixed in No Gnus, so I expect it to show up in
Emacs 24.1 soon.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2012-04-10 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 21:46 bug#7410: Impossible multibyte->unibyte conversion Stefan Monnier
2012-04-10 20:53 ` Lars Magne Ingebrigtsen
2012-04-10 20:59 ` Lars Magne Ingebrigtsen [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
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=m3398bwbfk.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=7410@debbugs.gnu.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.
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).