BUG: GMail adds spaces in UTF-8 encoded "Subject:"
simos
"Subject:" line if it contains Utf-8 encoded characters.
Could someone else verify with another language?
Simply send an e-mail to youself with a subject line in a non-latin
(for example non iso-8859-1) character as with
Subject: AAAAAAAAAAAAAAAAAAAAAAAAAAAAA (replace "A" with character of
choice).
The result (bug) should be like
Subject: AAAAAAAAAAAA AAAAAAAAAAAAA AAAA
I have reported this to GMail as bug #17701124.
I have verified this bug for Greek.
Could you please try to verify and report back here?
Klaus Alexander Seistrup
the subject line is QP encoded partially, and perhaps Gmail doesn't
"assemble" the line properly before decoding from Quoted Printable.
What does the subject line look like if you choose "show original"?
Is it QP encoded?
I haven't tried in Gmail, but I've seen the same happening in other
mail client using QP encoded iso-8859-1.
Cheers,
// Alex
Klaus Alexander Seistrup
Copenhagen · Denmark
simos
Subject: =?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6x?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrE=?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6x?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrE=?=
Notice that the second and subsequent lines do not start at position
one (there is a space character). This is easy to understand so that
the continuation lines of the Subject are not parsed as new header
lines. It appears as GMail somehow does not eliminate those
first-column spaces but uses them.
simos
appeared ok.
Ximian Evolution does not have the QP bug that GMail currently has.
Some testing. The double quotes are mine.
A. The original subject is
"Subject:
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
B. That's how the Subject appears on GMail:
"Subject: aaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa aaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa"
C. If you send an e-mail from GMail to a Evolution user (non GMail
account, not UTF processing..), it appears ok. The raw Subject is:
"Subject: =?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrE=?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsQ==?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsQ==?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsQ==?="
D. GMail processes the subject line when storing the mail in a way that
damages it. It appears to decode (wrongly) and then encode again.
"Subject: =?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6x?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrE=?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6x?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrE=?="
E. If you send such a wrongly decoded and then re-encoded e-mail to a
non-Gmail account (for example, go to "Sent mail" and forward it), it
looks like:
Subject: "=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xIM6xzrHOsSA=?=
=?UTF-8?B?zrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsSDOsc6x?=
=?UTF-8?B?IM6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrEgzrE=?=
=?UTF-8?B?IM6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6xzrHOsc6x?="
It appears the GMail adds more spaces in this version (inconclusive).
Klaus Alexander Seistrup
Base64-encoded chars using multiple lines.
simos
Yeah!
Tomi Häsä
>
> I have noticed that GMail adds spaces every 10-15 characters in the
> "Subject:" line if it contains Utf-8 encoded characters.
>
> Could someone else verify with another language?
>
> Simply send an e-mail to youself with a subject line in a non-latin
> (for example non iso-8859-1) character as with
>
> Subject: AAAAAAAAAAAAAAAAAAAAAAAAAAAAA (replace "A" with character
of
> choice).
>
> The result (bug) should be like
>
> Subject: AAAAAAAAAAAA AAAAAAAAAAAAA AAAA
I noticed the same kind of behaviour when I posted test messages with
different character encodings with different languages with Google
Groups web interface. For example, the problem didn't occur with
ISO-8859-1 and EUC-CN encodings, but it did occur with UTF-8 and
GB2312 encodings. See these test postings (as you can see, some of
the subjects contain added spaces, some don't):
This is OK (Finnish/ISO-8859-1):
http://groups.google.co.uk/groups?selm=ci7553%24bna%40odah37.prod.google.com&output=gplain
This isn't OK (Finnish/UTF-8):
This is OK (Chinese/EUC-CN):
This isn't OK (Chinese/GB2312):