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 248682 - Receive mail with DBCS characters
Receive mail with DBCS characters
Status: VERIFIED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
1.5.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks: 246841
 
 
Reported: 2003-09-22 05:22 UTC by hart wang
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
mail (5.94 KB, text/plain)
2003-09-28 05:40 UTC, hart wang
Details

Description hart wang 2003-09-22 05:22:46 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. send a mail with DBCS characters
2. reply this mail twice 
3. 

Actual Results:
The DBCS in this mail is not displyed correctly.

Expected Results:
The DBCS in this mail should be displyed correctly.

How often does this happen? 


Additional Information:
Comment 1 Jeffrey Stedfast 2003-09-22 15:05:39 UTC
what are DBCS characters?
Comment 2 Jeffrey Stedfast 2003-09-23 15:09:33 UTC
please attach the message and/or test with 1.4.5
Comment 3 hart wang 2003-09-24 03:57:57 UTC
这是一行简体中文的测试。验证中文是否能正确显示。   
There are some DBCS charaters .
You can send a mail with these DBCS charaters.
After the mail is replied twice ,these DBCS characters will
be displayed :
这是一行简体中文的测试。验证中文是否能正确显示。
Comment 4 Gerardo Marin 2003-09-24 05:05:12 UTC
Please attach said mail to this report.
Comment 5 hart wang 2003-09-28 05:40:00 UTC
Created attachment 42950 [details]
mail
Comment 6 Jeffrey Stedfast 2003-09-29 15:27:16 UTC
uh..... the reason it doesn't show properly is because the charset
specified in the Content-Type header is iso-8859-1.

it needs to be set to the proper charset. and even if it were set to
the proper charset now, it's probably long since been corrupted after
all those replies.

this is not a bug in evolution