Closed
Bug 506614
Opened 16 years ago
Closed 16 years ago
Sender with spezial characters not show
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 468351
People
(Reporter: uwe, Unassigned)
Details
Attachments
(1 file)
81.85 KB,
image/pjpeg
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; SLCC1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.5.21022; .NET CLR 3.5.30729; MS-RTC LM 8; .NET CLR 3.0.30729)
Build Identifier: Thunderbird 3.0b3
sender in inbox or other folder with spezial characters (e.g. german öäüß...) in the name not show.
Answer to this sender is not possible. (it works in TB 2.x)
Reproducible: Always
Comment 1•16 years ago
|
||
Which of next cases? Or different/new case?
> Bug 468351 display of header values with unencoded special characters broken
> Bug 493544 invalid decoding of multiline utf-8 subject header
> (better to be tolerant with split of byte code at wrong position in RFC 2047 encoding)
Reporter | ||
Comment 2•16 years ago
|
||
Reporter | ||
Comment 3•16 years ago
|
||
I think it is a new problem.
Comment 4•16 years ago
|
||
This looks like bug 415368
Comment 5•16 years ago
|
||
(In reply to comment #2)
> Header is ok. Display broken
Header is never OK. Raw binary of non 7bits-us-ascii character is placed in From: header without encoding.
Because Content-Type: header is not provided by bug opener, it's impossible to know whether DUP of Bug 468351 or not from provided mail data. However, because bug opener says "it works in TB 2.x", I think DUP of Bug 468351. Closing as DUP of Bug 468351.
Re-open please, if it'll be found DUPing is wrong.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•