wrong charset may be automatically used when replying to a message

UNCONFIRMED
Unassigned

Status

MailNews Core
MIME
UNCONFIRMED
14 years ago
9 years ago

People

(Reporter: SR, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040107
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7a) Gecko/20040107

I defined utf-8 as my default charset.
I removed all the charsets but :
1- utf-8
2- iso-8859-1
from the two chrset lists I've found in mozilla to configure which charset
is used when composing a message.

If I write a message with only 7 bits characters, its charset is set
to us-ascii, neither UTF-8 nor latin1 is used.
I guess this is an optimisation, and this is a nice one.

If I write a message with 8 bit characters, and some that are not
in the latin1 charset (the euro symbol for instance), utf-8 charset
is used. That works fine.

BUT

When I *reply* to the first message :
If I introduce an 8bit character that exists in the latin1 charset
in my reply, latin1 charset is used. Nice, that also works fine.
When I reply to this last message, introducing the euro symbol that
does not exist in the latin1 charset then it's the windows 1252 charset
that is used, instead of UTF-8 !

I've removed this charset from the two lists (why 2 ?) I've found, so :
-there is a third list hidden somewhere (why 3 ???)
or
-there is a bug in charset selection algorithm


Reproducible: Always

Steps to Reproduce:
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
(Reporter)

Comment 2

12 years ago
The bug is still present with the latest relase version of mozilla mailnews.
I do confirm it :/
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: stephend → mime
(Assignee)

Updated

9 years ago
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.