From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/905 Path: news.gmane.org!not-for-mail From: peterwu@hotmail.com (Peter Wu) Newsgroups: gmane.emacs.gnus.user Subject: Re: Mule again Date: 12 Aug 2002 18:48:48 -0700 Organization: http://groups.google.com/ Message-ID: <9acc2ac1.0208121748.2d54a985@posting.google.com> References: <86adnsw7yj.fsf@hotmail.com> <864re0gmf1.fsf@hotmail.com> NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138667776 8900 80.91.229.2 (31 Jan 2006 00:36:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 00:36:16 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:28:17 2006 Original-Path: quimby.gnus.org!news.ccs.neu.edu!news.dfci.harvard.edu!news.cis.ohio-state.edu!news.maxwell.syr.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail Original-Newsgroups: comp.emacs,gnu.emacs.gnus Original-NNTP-Posting-Host: 207.46.71.13 Original-X-Trace: posting.google.com 1029203328 6086 127.0.0.1 (13 Aug 2002 01:48:48 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: 13 Aug 2002 01:48:48 GMT Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:1045 Original-Lines: 22 X-Gnus-Article-Number: 1045 Tue Jan 17 17:28:17 2006 Xref: news.gmane.org gmane.emacs.gnus.user:905 Archived-At: Eric Marsden wrote: > >>>>> "pw" == Peter Wu writes: > > ecm> To force a charset for a broken article, use C-u gb2312 RET W M c > ecm> (gnus-article-decode-charset), in the Summary buffer. You could have > ecm> found this in the "MIME Commands" section of the Gnus manual, or by > ecm> saying "C-h a gnus.*charset". > > pw> However the method seemed to fail. When I press C-u and g, the > pw> mail is displayed with a lot of numbers. I guess they are > pw> UNICODE numbers. I did not have a chance to enter 'gb2312' and > pw> hit RETURN. > > sorry, I got that wrong, it should have been "C-u W M c gb2312 RET". Thanks, Eric. Unfortunately it does not work for me. :( All I see is such numbers as \233\212. I don't know what it is. If I save this message into file and open it in Mozilla, I can read it correctly after forcing Mozilla to use GB2312 encoding to render the message. Any idea? Thanks! - Peter