From: Fabrice Popineau <Fabrice.Popineau@supelec.fr>
Subject: XEmacs 21.5, Gnus and UTF-8
Date: Tue, 17 May 2005 10:15:13 +0200 [thread overview]
Message-ID: <3bsm5kvi.fsf@esemetz.metz.supelec.fr> (raw)
Follow-up to my own message.
I have made some progress in understanding what prevents No Gnus to
display UTF-8 messages under my configuration.
In fact, #'article-decode-charset didn't decode the article.
This happens because I'm used to 'hide' most of headers, including Content-Type. And in this case,
#'article-decode-charset can't find it.
I think that to be safe, headers should be looked for in the original
article, not in the displayed buffer.
Best,
--
Fabrice Popineau
------------------------
e-mail: Fabrice.Popineau@supelec.fr | The difference between theory
voice-mail: +33 (0) 387764715 | and practice, is that
surface-mail: Supelec, 2 rue E. Belin, | theoretically,
F-57070 Metz | there is no difference !
reply other threads:[~2005-05-17 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3bsm5kvi.fsf@esemetz.metz.supelec.fr \
--to=fabrice.popineau@supelec.fr \
/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).