From: Alberto Luaces <aluaces@udc.es>
To: ding@gnus.org
Subject: Re: problem with some codifications...
Date: Tue, 29 Apr 2014 09:32:20 +0200 [thread overview]
Message-ID: <878uqowpyz.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <871twgacr1.fsf@pedroche.home>
Igor Sosa Mayor <joseleopoldo1792@gmail.com> writes:
> Hi,
>
> since 2 weeks I'm using gnus without problem and I'm really happy.
>
> I'm only experiencing some strnage problems with the codification in one
> mailing list. I see some messages like that:
>
> http://picpaste.de/pics/gnus-lista-wpG3muCB.1398751584.png
>
> with this \363, \355,...
>
> It is this message:
> http://permalink.gmane.org/gmane.comp.lang.r.general.spanish/38
>
> I'm trying to analyse the headers, but I don't see where the problem
> could be...
>
> Any idea?
It is likely that either the Content-Type header doesn't specify the
correct encoding, or there are mixed encondings in the message.
--
Alberto
next prev parent reply other threads:[~2014-04-29 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 6:08 Igor Sosa Mayor
2014-04-29 7:32 ` Alberto Luaces [this message]
2014-04-29 16:09 ` Igor Sosa Mayor
2014-04-29 16:27 ` Alberto Luaces
2014-04-29 21:27 ` Igor Sosa Mayor
2014-05-20 14:48 ` Igor Sosa Mayor
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=878uqowpyz.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--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).