Closed
Bug 201037
Opened 22 years ago
Closed 21 years ago
character encoding should be derived from message's content-type:charset in messages list
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
People
(Reporter: man, Assigned: sspitzer)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312
When I viewing a message in Mail&News, it's encoding is properly derived from
content-type: charset field, as it should be.
But in the messages list it's not! I've set default coding to KOI8-R in messages
list, but I get all kinds of mail - KOI8-R, CP1251, who know what else?
I don't understand, why the hell Mail&News doesn't understand each messages
subjects' encoding from the very same content-type: charset field.
This requires messages download, but why don't do that when they're stored locally?
I'm just angry when I see one subject ok, another's in gibberish
Reproducible: Always
Steps to Reproduce:
1.set default encoding for messages list to some encoding
2.get several messages of various encodings
Actual Results:
observe message bodies displayed ok (concerning encoding), but message subjects
in the messages list ok only for default encoding (see 1.)
Expected Results:
both bodies and subjects should be displayed ok (concerning encoding)
Comment 1•21 years ago
|
||
The same problem in the Mozilla Thunderbird 0.4 (under Windows). Only for 8-bit
headers (MIME-encoded subjects have "built in" charset and displayed OK).
Comment 2•21 years ago
|
||
*** This bug has been marked as a duplicate of 90584 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•