From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Broken encoding in HTML parts with shr
Date: Wed, 05 Jan 2011 15:32:50 +0100 [thread overview]
Message-ID: <877hejzai5.fsf@member.fsf.org> (raw)
In-Reply-To: <m3tyhno2hw.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 05 Jan 2011 15:21:15 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>> since shr is available, I switched my habit of preferring the plain
>> text part if there is a HTML alternative. Unfortunately, the
>> encoding is broken in the HTML part.
>>
>> For example, in the HTML part of some mail I have:
>>
>> Viele Gr|_e
>
> I'm not sure I understand. If the encoding is broken in the HTML
> part, there's nothing Gnus can do about that.
No, you got me wrong. Both parts are declared correctly:
--8<---------------cut here---------------start------------->8---
------=_NextPart_000_0007_01CBACC1.4925F100
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
--8<---------------cut here---------------end--------------->8---
with "Viele Gr=FC=DFe", and
--8<---------------cut here---------------start------------->8---
------=_NextPart_000_0007_01CBACC1.4925F100
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
--8<---------------cut here---------------end--------------->8---
also with "Viele Gr=FC=DFe".
So the encoding is identical, but Gnus displays the mail differently.
And it's not only that mail, but it applies to any HTML mail with
non-ASCII contents.
I'll forward that mail to you privately.
Bye,
Tassilo
--
Sent from my Emacs
prev parent reply other threads:[~2011-01-05 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 9:41 Tassilo Horn
2011-01-05 14:21 ` Lars Magne Ingebrigtsen
2011-01-05 14:32 ` Tassilo Horn [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=877hejzai5.fsf@member.fsf.org \
--to=tassilo@member.fsf.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).