Closed Bug 270148 Opened 20 years ago Closed 20 years ago

Automatic detection of the encoding doesn't work in newsgroup

Categories

(Thunderbird :: Preferences, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: serval2412, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.5) Gecko/20041108 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr-FR; rv:1.7.5) Gecko/20041108 Firefox/1.0

If you define prefs about encoding, these prefs override the messages encoding
of the newsgroup.

Reproducible: Always
Steps to Reproduce:
1.use UTF8 by default for ingoing and outgoing.
2.go on a french newsgroup for example (most of the messages use is 8859-1)


Actual Results:  
characters like é display "?"

Expected Results:  
thunderbird shouldn't override the encoding of a newsgroup message (he doesn't
for an answer to a mail !)
(In reply to comment #0)
> Actual Results:  
> characters like [é] display "?"

There are a number of factors that affect this display.  
1) Messages can, and should, specify their preferred encoding, but this 
information is often missing and sometimes specified incorrectly.

2) Each folder or newsgroup can specify its preferred encoding for message 
display, and also specify whether the encoding will override the encoding 
specified in the message.  (Right-click on Folder, Properties)

3) The display of non-ASCII characters in the message headers is not controlled 
by the character set specified in the message, so it often happens that you'll 
see '?' in the header but the message body displayed correctly.

I am not seeing any difference in behavior between newsgroups and mail in this 
regard (TB 1.0, Win2K), so I am marking this bug WorksForMe.

Reporter (serval): if you disagree with this resolution, please feel free to 
reopen, and provide the following information:
1) Properties settings for the newsgroup's encoding
2) Save a message that is not displaying correctly as a .EML file, and attach 
that file to this bug, using the Create New Attachment link above.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.