After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 104459 - UTF-8 charset when replying
UTF-8 charset when replying
Status: RESOLVED DUPLICATE of bug 104479
Product: Pan
Classification: Other
Component: general
0.13.3
Other other
: Normal normal
: ---
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2003-01-26 10:20 UTC by Chema Mateos.
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chema Mateos. 2003-01-26 10:20:45 UTC 
A problem that I have found: if a message doesn't have the charset header
and you reply to it, the content will be taken as UTF-8 encoding, even if
your prefered charset is iso-8859-15.

An example of what I mean:

When I reply to this message (which doesn't have charset header):

"¿Alguien conoce esta marca? En la página de la Fnac [.....]"

I get this in the compose message window:

"¿Alguien conoce esta marca? En la página de la Fnac[...]"

Everything I write myself is encoded OK, but not the quoted text.
Comment 1 Christophe Lambin 2003-01-27 21:04:36 UTC 
Chema:  can you check whether this is a duplicate of #104479 ?  I
can't find any other way of reproducing this.
Comment 2 Chema Mateos. 2003-01-27 21:23:35 UTC 
It looks like it is to me... I did several tests before sending the
bug report... but I didn't look into the subject characters

I'll make another round of testing as soon as I can
Comment 3 Chema Mateos. 2003-02-20 20:10:17 UTC 
It seems that ASCII > 127 characters in the "From" field makes this
error to appear.

Messages with ASCII > 127 characters in the Subject don't do anything
Comment 4 Christophe Lambin 2003-03-11 22:54:41 UTC 

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