From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/67910 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: [bugfixed] mm-charset-override-alist isn't used in decoding headers Date: Mon, 15 Dec 2008 13:16:06 +0900 Organization: Emacsen advocacy group Message-ID: References: <87myf1ckm2.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 1229314630 4048 80.91.229.12 (15 Dec 2008 04:17:10 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 15 Dec 2008 04:17:10 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M16356@lists.math.uh.edu Mon Dec 15 05:18:15 2008 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 1LC4uM-0000XI-8w for ding-account@gmane.org; Mon, 15 Dec 2008 05:18:14 +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 1LC4sy-0006YW-KY; Sun, 14 Dec 2008 22:16:48 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1LC4sx-0006YD-By for ding@lists.math.uh.edu; Sun, 14 Dec 2008 22:16:47 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1LC4su-00063H-BY for ding@lists.math.uh.edu; Sun, 14 Dec 2008 22:16:47 -0600 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1LC4t6-00060y-00 for ; Mon, 15 Dec 2008 05:16:56 +0100 Original-Received: from localhost ([127.0.0.1]:47026) by orlando.hostforweb.net with esmtpa (Exim 4.69) (envelope-from ) id 1LC4sK-0001H4-1z for ding@gnus.org; Sun, 14 Dec 2008 22:16:08 -0600 X-Hashcash: 1:20:081215:ding@gnus.org::TsN0U3wjSiGfbZTd:00003rpH X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:f360cXXDQH3DiutgugkLk+HlWfs= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:67910 Archived-At: >>>>> Reiner Steib wrote: > On Wed, Dec 10 2008, Katsumi Yamaoka wrote: >> (Note that that I mention here is the `gbk' charset, not the `gbk' >> coding system. So, `mm-charset-to-coding-system' is the best >> choice for checking whether it is available or not. However, >> when loading mm-util,elc the default value section and/or the >> `:set' section of `(defcustom mm-charset-override-alist ...)' >> are processed before defining that function.) > Would it help to move the defcustom down (or the defun up)? Or would > this introduce other problems? Thanks. There were two other reasons that made me hesitate to add the `(gb2312 . gbk)' pair to `mm-charset-override-alist': 1. In Emacs 22 the `gbk' charset is available because of `mm-charset-synonym-alist', however it does not support gbk characters fully. For example: (rfc2047-decode-string "=?gbk?B?m3I=?=") => "\x9br" 2. In XEmacs 21.4 w/o the Mule feature, (mm-charset-to-coding-system 'gbk) returns the symbol `gbk'. But I decided to consider that 1. is not due to a Gnus bug, and realized 2. is not a real problem (it won't get to be a straight cause of an error, and it is a matter of course that non-Mule XEmacs doesn't display gbk messages correctly). So I've added the `(gb2312 . gbk)' pair to the default value of `mm-charset-override-alist' for Emacsen that supports gbk, having moved `mm-charset-to-coding-system' and `mm-charset-eval-alist' forward. In addition, I've added the optional argument `silent' to `mm-charset-to-coding-system' so that it may not issue a warning message when examining whether gbk is available. Regards,