Closed
Bug 258320
Opened 20 years ago
Closed 20 years ago
RFC2047 decoding too strict, doesn't ignore embedded whitespace
Categories
(MailNews Core :: MIME, defect)
MailNews Core
MIME
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: stefpix, Assigned: mscott)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040905 Camino/0.8+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a3) Gecko/20040905 Camino/0.8+
Special Characters dont show up right
I have a problem with special characters [accented letters / umlauts etc.]
someone who is "From: bokförlaget"
TB becomes "From: =?iso-8859-1?B?Ym9rZvZybGFnZXQgdGV4dHVy ?="
it is swedish.
I tried different text encodings and back in the preferences.
the best one so far is Western (ISO 8859-1). But I still get the same garbage
text in the message list and in the message header.
i have the latest build 20040905 and Mac OS X10.3
what text encoding setting should I use?
or is it a bug?
with Apple Mail.app I do not have such problems - nor with web-browsers if I
look at my email through the webmail interface. the problem only exists in
Thunderbird.
Reproducible: Always
Steps to Reproduce:
1. changed different text encodings
2.
3.
Actual Results:
the problem persists.
Comment 1•20 years ago
|
||
From: =?iso-8859-1?B?Ym9rZvZybGFnZXQgdGV4dHVy ?= is invalid because of
^------ this space here
With the space removed, that string will be displayed as "bokförlaget textur".
I'm not sure if that problem is the fault of Mozilla or of the sending program.
Can you attach a sample failing message? Save as a .eml file, and use the
"Create New Attachment" link above.
Summary: special charachters [umlauts etc] show as garbage text in "From:" field → special characters [umlauts etc] show as garbage text in "From:" field
(In reply to comment #1)
> From: =?iso-8859-1?B?Ym9rZvZybGFnZXQgdGV4dHVy ?= is invalid because of
> ^------ this space here
>
> With the space removed, that string will be displayed as "bokförlaget textur".
> I'm not sure if that problem is the fault of Mozilla or of the sending program.
> Can you attach a sample failing message? Save as a .eml file, and use the
> "Create New Attachment" link above.
I get your point but the same message/text gets displayed correctly in my
webmail window in Camino and also in Apple Mail.app so it must be some bug of TB
at displaying certain characters in the message list and headers.
does it happen in the other OS versions?
Comment 5•20 years ago
|
||
> I'm not sure if that problem is the fault of Mozilla
To be clear: It was possible that the space had been introduced by a "folded"
header, e.g.
From: =?iso-8859-1?B?Ym9rZvZybGFnZXQgdGV4dHVy
?=
(I think that's illegal too, but Mozilla doesn't collapse the whitespace
entirely when unfolding and so might be accused of introducing the space.)
But the source of the message shows that the space was included in a single-line
header, putting the fault on:
X-Mailer: MIME-tools 5.41 (Entity 5.404)
(In reply to comment #3)
> I get your point but the same message/text gets displayed correctly in my
> webmail window in Camino and also in Apple Mail.app so it must be some bug of
> TB at displaying certain characters in the message list and headers.
It's not bug so much as it is an imposed strictness. Those other programs
ignore spaces, even tho the specification (rfc 2047) says there should be no
spaces. See bug 227290 for a similar issue.
> does it happen in the other OS versions?
Yes, I see it with Win2K. Confirming, changing platform, dropping severity,
updating summary, and moving to MailNews/MIME.
Severity: major → normal
Status: UNCONFIRMED → NEW
Component: General → MIME
Ever confirmed: true
OS: MacOS X → All
Product: Thunderbird → MailNews
Hardware: Macintosh → All
Summary: special characters [umlauts etc] show as garbage text in "From:" field → RFC2047 decoding too strict, doesn't ignore embedded whitespace
Version: unspecified → Trunk
Comment 6•20 years ago
|
||
I don't think we want to do anything about this. This is a rather serious bug
(but easy to fix) of the program generating malformed RFC 2047 encoded words.
Not many MUAs make such a serious mistake. You'd better file a bug report to the
program (MIME Tools 5.41) [1]. One reason I won't do anything here is that if
we do what Apple MailApp does, there's no way to tell literal
'=?iso-8859-1?B?Ym9rZvZybGFnZXQgdGV4dHVy ?=' (with space) from 'bokförlaget
textur'
[1] I may send a patch to the MIME Tools developer (Perl module).
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•