User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2a) Gecko/20020910 1. There is no way to change the display language for the foreign language newsgroup news.wonderspace.net/wonder.music.¼Ö¾¹¨¦ the newsgroup name appeared only as raw-characters instead of proper foreign language in Mozilla, even the default character set is setup properly. 2. I can read, but can't post anything to the newsgroup. Mozilla returns an error: A News (NNTP) error occured: cannot crosspost to nonexistent group (wonder.music....) see dnews.log for details Reproducible: Always Steps to Reproduce: 1. Subscribe the newsgroup: news://news.wonderspace.net/wonder.music.¼Ö¾¹¨¦ 2. Try to post something to the group 3. You will receive the error Actual Results: Mozilla returns an error message: A News (NNTP) error occured: cannot crosspost to nonexistent group (wonder.music....) see dnews.log for details Expected Results: Post message to the group successfully, just like M$'s Outlook Express
Do you have write access to the group? Does this problem stil loccurs?
(In reply to comment #1) > Do you have write access to the group? > Does this problem stil loccurs? I've removed the group a while ago, and I re-subscribe the group again as soon as I received your e-mail (I am using Mozilla 1.6 right now) The situation now is even worse... I can't even read any posted news when I click on any post. The post item would be selected, but the content won't display (i.e. Blank). Yes, I have write access to the group. I tried to access the group via M$ OE6, and I post and read without any problem. I've attached the display screen of both newsgroup readers. (i.e. If you need to see the newsgroup posts encoding correctly, you have to specify the right encoding from Edit->Newsgroup Properties. While Mozilla can't display the newsgroup name properly even after I changed the newsgroup encoding, OE6 can display both the newsgroup name and its posts with correct encoding)
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.