294766 - Character encoding is not correct in replays if using Enigmail.

Status: RESOLVED EXPIRED

(Thunderbird :: Preferences, defect)

Description

[Alexandru]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Opera 7.54u1  [en]
Build Identifier: 1.0.2 (20050317)

For replay to gpg signed emails (even the option ‘Always use the default 
character encoding in replays’ is uncheck) the message use the default character 
encoding. 
Thunderbird with enigmail 0.91.0.0. 

Reproducible: Always

Steps to Reproduce:
1.Install enigmail version 0.91.0.0 and configure. 
2.Uncheck the option ‘Always use the default character encoding in replays’ 
(Options ->Fonts)
3.Receive e email with the character encoding iso-8859-2 (Content-Type: text/
plain; charset=iso-8859-2; DelSp=Yes; Format=Flowed) signed with PGP. 
4. Tray to replay to it.
5.Check the Options ->Character Encoding 
Actual Results:  
The character encoding is the default one not the one form the original mail (in 
this cas iso-8859-2) , and the message will be sent with the default one. 



Expected Results:  
The character encoding should be the the same as the one you replay to it. 
If you replay to a  message with encoding “iso-8859-2” the encoding should be 
“iso-8859-2”

Comment 1

[Gervase Markham [:gerv]]

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/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.