[leafnode-list] Re: Base64 coding in list messages
Peter J Ross
peadar.ruadh at gmail.com
Tue Oct 21 20:34:26 CEST 2008
On Tuesday 21 October 2008 11:26:15 Whiskers wrote:
> On Tue, 21 Oct 2008 08:45:29 +0200 Matthias Andree
>
> <matthias.andree at gmx.de> wrote:
> > Whiskers <catwheezel at operamail.com> writes:
>
> [...]
>
> > > When it left me, the message had these headers:
> > >
> > > Content-Type: text/plain; charset=UTF-8
> > > Content-Transfer-Encoding: quoted-printable
> > >
> > > but on arrival from the mailing-list, these had changed to:
> > >
> > > Content-Type: text/plain; charset="utf-8"
> > > Content-Transfer-Encoding: base64
>
> [...]
>
> > Generally speaking, quoted-printable or base64 will usually happen
> > whenever umlauts are involved - or other characters that don't fit into
> > 7bit (I'm avoiding them in this message). In the message you sent it was
> > the German oe umlaut in the greeting that you had quoted from Torsten's
> > message.
>
> But it only happens occasionally even in that case; Torsten's messages
> don't get converted to Base64 - but in that thread, both Peter J Ross's
> reply and mine, did.
Mine was quoted-printable when it left me.
From: Peter J Ross <peadar.ruadh at gmail.com>
To: leafnode-list at dt.e-technik.uni-dortmund.de
Subject: Re: [leafnode-list] Fetchnews process takes very long
Date: Sun, 19 Oct 2008 04:54:23 +0100
User-Agent: KMail/1.9.9
References: <87hc7axn94.fsf at physik.rwth-aachen.de>
In-Reply-To: <87hc7axn94.fsf at physik.rwth-aachen.de>
MIME-Version: 1.0
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200810190454.23983.peadar.ruadh at gmail.com>
If you're not the only one receiving that as Base64, the problem arises
somewhere earlier in the chain.
> Torsten's messages get to me with
>
> Content-Type: text/plain; charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> so perhaps it isn't the actual characters, so much as the sender's
> character set - I used UTF-8 (automatic setting by my software when I use
> non-US-ASCII characters); perhaps Peter did too? If the messages go
> through a system that can't handle UTF-8 I can see that causing a problem.
I use UTF-8 whenever non-ASCII characters are required (because I'm living in
the 21st Century), but I'm not sending raw 8bit data. I don't understand why
messages sent as quoted-printable should be re-encoded as Base64.
--
PJR :-)
More information about the leafnode-list
mailing list