From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: Debugger entered--Lisp error: (error "Can't rfc2047-encode `espa\x00f1ol \302\241Mira qui\x00e9n'")
Date: Fri, 22 Dec 2006 09:09:37 +0900 [thread overview]
Message-ID: <b4mhcvo3i66.fsf@jpl.org> (raw)
In-Reply-To: <v93b79rzhq.fsf@marauder.physik.uni-ulm.de>
Hi,
Could you let me know the url you subscribe to for the nnrss:eltiempo
group? I'd like to trace what Emacs 23 does, because I suspect Gnus
breaks the xml contents due to the unexpected unibyte-multibyte
conversion with Emacs 23. (I'm not sure I have time to do that in
this year-end, though. Sorry.)
>>>>> In <v93b79rzhq.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib wrote:
> $ emacs-23 -Q
> (require 'nnrss)
> (nnrss-mime-encode-string
> #("El actor venezolano Juan Alfonso Baptista qued\x00f3 segundo en concurso espa\x00f1ol \302\241Mira qui\x00e9n baila!"
> 0 46 (charset windows-1252)
> 47 72 (charset windows-1252)
> 73 86 (charset windows-1252)
> 87 95 (charset windows-1252)))
I could reproduce the error. However, that \xNNNN and \NNN things
appear in the string then is funny. Although those might only be
a deed of the debugger, they should have been decoded fully as
human-readable characters.
BTW, the following workaround might help temporarily.
--8<---------------cut here---------------start------------->8---
(defadvice mm-find-mime-charset-region (after delete-nil-elements activate)
"Delete nil elements in the return value."
(setq ad-return-value (delq nil ad-return-value)))
--8<---------------cut here---------------end--------------->8---
Regards,
next prev parent reply other threads:[~2006-12-22 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 10:08 Jhair Tocancipa Triana
2006-12-21 16:21 ` Reiner Steib
2006-12-22 0:09 ` Katsumi Yamaoka [this message]
2006-12-22 4:32 ` Katsumi Yamaoka
2006-12-22 6:57 ` Katsumi Yamaoka
2006-12-22 11:03 ` Jhair Tocancipa Triana
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=b4mhcvo3i66.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).