Closed Bug 209142 Opened 21 years ago Closed 19 years ago

crash when I read chinese message

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: 13964001012, Unassigned)

References

()

Details

(Keywords: hang)

Attachments

(4 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030610
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030610

the mailnews subscribe window can't display chinese correctly. and when I try to
click  on a chinese message to read, mozilla got totally no response. the
windows task mananger indicates that the cpu is 100% used. every time I set the
 news folder's Default Character Coding to GB2312, it comes back to IBM864 when
I open the properties window again.

Reproducible: Always

Steps to Reproduce:
1.right click on the folder name
2.select "Properties" to open the properties dialog
3.change the default character coding to GB2312
4.click ok to close properties dialog window
5.right click the folder name again
6.select the "Properties" to open the properties dialog
Actual Results:  
the default character coding comes back to IBM864

Expected Results:  
Mozilla can display chinese correctly in the news subscribe window. and the
properties window can save the setting of default character coding.
does it actually crash with the Netscape Feedback Agent ?
Keywords: hang
in mozilla 1.5 ia dose not realy crash,but in Thunderbird it's crash
Product: Browser → Seamonkey
Reporter:
Do You see this with a recent Mozilla or thunderbird Release ?
if yes: Please provide a talkbacvk ID from that crash.
 in  Thunderbird  version 1.0.2 (20050317) it not creash
and subscrib correctly.but the mailnews subscribe window can't display chinese
correctly .
can't display chinese correctly .
Attached image subscribe image
in this version the character coding save is ok
Attached image news title
Assignee: sspitzer → mail
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Component: MailNews: Subscribe → MailNews: Message Display
QA Contact: stephend → search
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: