273196 - Auto-detecting character set in mail doesn't work for mail with QP Latin-1 and standard encoding UTF-8

Status: RESOLVED DUPLICATE of bug 90584

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Christian Ertl]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910

When viewing e-mail encoded with quoted-printable ISO-8859-1 and standard
encoding is set to UTF-8 or user-defined, encoded characters like ü are viewed
as ??.
Detecting character set is set to universal.

This bug also appears in Thunderbird(version 0.9 (20041103)) though ignoring
MIME headers is not activated.
Settings are the same except detecting character set is off.

Reproducible: Always
Steps to Reproduce:




Expected Results:  
Mail should be viewed correctly.

Comment 1

[Christian Ertl]

Attachment: Example mail in quoted-printable

Example e-mail in ISO-8859-1 quoted-printable which is incorrectly viewed.

Comment 2

[Mike Cowperthwaite]

This symptom is seen if the folder is configured to always apply its character 
set to the messages in folder:  Right-click the folder, select Properties;
 [x] Apply default to all messages in the folder

If this checkbox is cleared, the message displays correctly, regardless of auto-
detect settings (because the message contains a legal charset spec).

The display of the Subject (from attachment 167888 [details]) will be wrong unless the 
folder's default character set is ISO-8859-1, because the subject contains an 
illegal character (ü).  This can be temporarily overridden by forcing the 
character set selection in the menu to ISO-8859-1, even tho that item is already 
selected (but that will not correct the display in the Thread Pane).

Comment 3

[Christian Ertl]

The checkbox was alyways unchecked.

Furthermore there is no ü in the subject.

Comment 4

[Mike Cowperthwaite]

(In reply to comment #3)
> The checkbox was alyways unchecked.

I find this hard to believe.  At any rate, I do not see your symptom unless that 
checkbox is checked.


> Furthermore there is no ü in the subject.

There most certainly is.  From the attachment:

Subject: Multimedia PC System 3200S+ für 0,- EUR!
                                      ^----------- right there

Comment 5

[Christian Ertl]

Oh sorry, I looked at the wrong mail.

> I find this hard to believe.  At any rate, I do not see your symptom unless that 
checkbox is checked.

I think that your assuption is inappropriate.
I checked all accounts on my different installations, this checkbox is never
checked.

At the moment I switch to UTF-8 or anything else then Latin-1 for incoming
mails, I get this problem.

Comment 6

[Mike Cowperthwaite]

OK, I'll reopen.  For the MailNews (suite) case, please verify:

Preferences | MailNews | Message Display
  Default Character Encoding: UTF-8

View | Encoding | AutoDetect    =>   Universal

Folder Properties:   Apply Default to All Messages   is turned off

All correct?

1) What is the character set specified on the Folder Properties dialog?

You select the above mail:
2)  How does the Subject appear in the Thread Pane?
3)  How does the Subject appear in the message envelope?
4)  How exactly does the word "Plätzchenduft" in the first sentence appear?
5)  Which character set is selected in the    View | Character Encoding
    submenu?

Comment 7

[Christian Ertl]

> All correct?
Yes.

1) UTF-8
2) [...] 3200S+ f???????????
3) the same
4) It appears as it should. (Plätzchenduft)
5) Western (ISO-8859-1)

Comment 8

[Mike Cowperthwaite]

(In reply to comment #7)
> 4) It appears as it should. (Plätzchenduft)

It does?  Then what is this bug about?  The Subject lines?

Comment 9

[Christian Ertl]

That's correct.

Comment 10

[Mike Cowperthwaite]

I don't see the word "subject" or "header" anywhere in your original bug report 
or summary.

The header of that message is illegal; RFC822 restricts the contents of mail 
headers to ASCII, which does not include the ü.  Non-ASCII header information is 
supposed to be encoded, such as described in RFC2047.

Mozilla actually allows you to display illegal header information according to a 
user-specified charset, such as the UTF-8 that you have associated with the 
folder.  You can override that per message, in the envelope panel, by explicitly 
selecting the desired character set.

Mozilla does not use the charset specified in the mail to decode the headers; 
that is what the dupe is about.

*** This bug has been marked as a duplicate of 90584 ***