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 249663 - mail sent out in UTF encoding even when ISO8859-2 is explicitely specified
mail sent out in UTF encoding even when ISO8859-2 is explicitely specified
Status: RESOLVED DUPLICATE of bug 249548
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-10-14 22:55 UTC by Gabor BORGULYA
Modified: 2003-10-15 18:30 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gabor BORGULYA 2003-10-14 22:55:42 UTC
Description of Problem: 
mail sent out in UTF encoding even when ISO8859-2 is 
explicitely specified 
 
Steps to reproduce the problem: 
0. set the default encoding to ISO8859-2 
1. write a letter with characters not included in the 
ISO8859-2 charset (e.g. letter ?) 
2. click on ISO8859-2 encoding in the edit menu, to ensure 
that the encoding of the mail sent out would be this 
3. press the send button 
 
Actual Results: 
Mail is sent out in UTF encoding! :(( 
 
(lots of people reporting I sent an unreadable mail. When I 
tried again resending it, double-checking the encoding in 
the edit menu - all of them received the same again, 
blaming me) 
 
 
Expected Results: 
Mail sent out in the encoding I specify. 
If there are characters that don't fit in that coding, 
Evolution should ask what to do! 
Possible solutions: 
- UTF offered as a charset that can describe all the 
characters I used. 
- offering substitution of characters to degenerate versions 
(e.g. ? -> ü, or ? -> u, mabe ? -> u~ substitutions) Mozilla 
can do something like this. 
 
How often does this happen?  
Always. 
 
Additional Information:
Comment 1 Gerardo Marin 2003-10-15 18:30:13 UTC

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