From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/68035 Path: news.gmane.org!not-for-mail From: jidanni@jidanni.org Newsgroups: gmane.emacs.gnus.general Subject: Re: Character of Death locks one out of all newsgroups Date: Sat, 03 Jan 2009 05:11:30 +0800 Message-ID: <871vvlxvjx.fsf@jidanni.org> References: <8763ky7qaz.fsf@marauder.physik.uni-ulm.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1230930787 16751 80.91.229.12 (2 Jan 2009 21:13:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 2 Jan 2009 21:13:07 +0000 (UTC) Cc: yamaoka@jpl.org To: ding@gnus.org Original-X-From: ding-owner+M16480=ding+2Daccount=gmane.org@lists.math.uh.edu Fri Jan 02 22:14:15 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1LIrKD-0001XK-6w for ding-account@gmane.org; Fri, 02 Jan 2009 22:12:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1LIrIx-0006oj-VJ for ding-account@gmane.org; Fri, 02 Jan 2009 15:11:40 -0600 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LIrIx-0006oe-3x for ding@lists.math.uh.edu; Fri, 02 Jan 2009 15:11:39 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LIrIu-0007Aw-L9 for ding@lists.math.uh.edu; Fri, 02 Jan 2009 15:11:39 -0600 Original-Received: from sd-green-bigip-207.dreamhost.com ([208.97.132.207] helo=homiemail-a2.g.dreamhost.com) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LIrJA-0003rm-00 for ; Fri, 02 Jan 2009 22:11:52 +0100 Original-Received: from jidanni.org (122-127-35-226.dynamic.hinet.net [122.127.35.226]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by homiemail-a2.g.dreamhost.com (Postfix) with ESMTP id EDB5FD25DF; Fri, 2 Jan 2009 13:11:32 -0800 (PST) X-Spam-Score: -2.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:68035 Archived-At: It seems the problem is that the former is called, instead of the latter: nnrss-mime-encode-string("Re: \x2563d\x2587c亲\x256cf经= nnrss-mime-encode-string("Re: \x2563d\x2587c&#20146;\x256cf&#32463;&#21382; 3") I.e., the correct rendering would have the ugly &s in it, as it is the posters fault. Instead nnrss-check-group tries too hard: it first runs a decoder over the message when it shouldn't. Otherwise the decoder gets run twice, when it should only be run once. So nnrss-mime-encode-string is OK, it was just being handed an overly filtered string mangled somewhere by nnrss-check-group before it call nnrss-mime-encode-string. In any case, if one day there are really bad characters (and not just ones created inside nnrss.el), "????" should be shown, and the error caught, instead of locking one out of all newsgroups. (Reiner, your reply got split into many mime parts (as would be expected.)