From: Lars Ingebrigtsen <larsi@gnus.org>
To: Garjola Dindi <garjola@garjola.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Incorrect character encoding in received messages
Date: Fri, 27 Dec 2019 19:07:15 +0100 [thread overview]
Message-ID: <875zi13ang.fsf@gnus.org> (raw)
In-Reply-To: <87pngc6zpa.fsf@pc-117-162.ovh.com> (Garjola Dindi's message of "Wed, 25 Dec 2019 19:13:21 +0100")
Garjola Dindi <garjola@garjola.net> writes:
> I have recently been having trouble with Gnus decoding some e-mails as
> ASCII when actually they should be decoded as unicode.
Sounds like there's no Content-Type header in the message that says what
the charset it.
> For instance, in French, the “à” char gets displayed as “\340”.
Then the message isn't encoded as utf-8, but is probably latin-1.
`C-u W M c' in the summary buffer should allow you to decode the message
in the proper charset.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2019-12-27 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 18:13 Garjola Dindi
2019-12-27 18:07 ` Lars 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zi13ang.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=garjola@garjola.net \
--cc=info-gnus-english@gnu.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).