From: Sven Joachim <svenjoac@gmx.de>
To: ding@gnus.org
Subject: Re: Garbled display of UTF-8 encoded mails
Date: Wed, 24 Nov 2010 08:03:29 +0100 [thread overview]
Message-ID: <87aakzdwzi.fsf@turtle.gmx.de> (raw)
In-Reply-To: <87lj4jdyns.fsf@turtle.gmx.de> (Sven Joachim's message of "Wed, 24 Nov 2010 07:27:19 +0100")
On 2010-11-24 07:27 +0100, Sven Joachim wrote:
> Maybe you'll see a difference in this mail. I include characters
> that cannot be encoded as iso-8859-1 and CC you. Hopefully no-one
> changes Content-Transfer-Encoding on the way.
Gnah, this displays fine in my GCC'ed copy, although other messages I've
sent appear broken. :-( I'll try to find an example that shows the bug.
> „Schöne Grüße aus Übersee“,
> Sven
next prev parent reply other threads:[~2010-11-24 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 20:11 Sven Joachim
2010-11-23 21:03 ` Sven Joachim
2010-11-24 4:39 ` Katsumi Yamaoka
2010-11-24 6:27 ` Sven Joachim
2010-11-24 7:03 ` Sven Joachim [this message]
2010-11-24 7:15 ` Katsumi Yamaoka
2010-11-24 7:17 ` Sven Joachim
2010-11-24 7:28 ` Katsumi Yamaoka
2010-11-24 7:58 ` Sven Joachim
2010-11-24 10:19 ` Sven Joachim
2010-11-24 12:54 ` Sven Joachim
2010-11-24 21:07 ` Lars Magne Ingebrigtsen
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=87aakzdwzi.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--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).