From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/64417 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: charset ANSI_x3.4-1968, et al Date: Tue, 20 Mar 2007 09:35:53 +0100 Message-ID: <871wjkwbva.fsf@mocca.josefsson.org> References: <87tzwiwcmo.fsf@mocca.josefsson.org> <87lkhtwrm2.fsf@mocca.josefsson.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1174379804 23254 80.91.229.12 (20 Mar 2007 08:36:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 20 Mar 2007 08:36:44 +0000 (UTC) Cc: ding@gnus.org To: Karl Chen Original-X-From: ding-owner+M12941@lists.math.uh.edu Tue Mar 20 09:36:38 2007 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 1HTZpd-0002QU-P2 for ding-account@gmane.org; Tue, 20 Mar 2007 09:36:38 +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 1HTZpO-00006A-7E; Tue, 20 Mar 2007 03:36:22 -0500 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 1HTZpL-00005l-4f for ding@lists.math.uh.edu; Tue, 20 Mar 2007 03:36:19 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.63) (envelope-from ) id 1HTZpE-0003rX-SQ for ding@lists.math.uh.edu; Tue, 20 Mar 2007 03:36:18 -0500 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1HTZpC-0001YG-00 for ; Tue, 20 Mar 2007 09:36:10 +0100 Original-Received: from mocca.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l2K8ZrNp029939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Mar 2007 09:35:53 +0100 OpenPGP: id=B565716F; url=http://josefsson.org/key.txt Mail-Copies-To: nobody X-Hashcash: 1:22:070320:ding@gnus.org::m4yPfs2KPgAATmJJ:HOp1 X-Hashcash: 1:22:070320:quarl@cs.berkeley.edu::rQrMV3CvlGgoKJPl:bpVz In-Reply-To: (Karl Chen's message of "Tue\, 20 Mar 2007 00\:50\:19 -0700") User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.95 (gnu/linux) X-Spam-Status: No, score=-0.7 required=4.0 tests=AWL,BAYES_50, FORGED_RCVD_HELO autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on yxa-iv X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on yxa.extundo.com X-Virus-Status: Clean X-Spam-Score: -2.1 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:64417 Archived-At: Karl Chen writes: >>>>>> On 2007-03-19 01:43 PDT, Simon Josefsson writes: > > Simon> I looked at a cleaner way to solve this. Can you test > Simon> the patch below? > > Thank you, yes, I tried it and it gets rid of the warning message, > but... > > Simon> (defcustom mm-charset-override-alist > [..] > Simon> - (iso-8859-9 . windows-1254)) > Simon> + (iso-8859-9 . windows-1254) > Simon> + (ansi_x3.4-1968 . us-ascii)) > > I'm not sure it's "cleaner": as far as I can tell > mm-charset-override-alist is intended to be a user-level override > list. For example, there could be aliases for iso-8859-1, but the > user shouldn't have to manually list all aliases to "override" > into windows-1252. If the user wants to override us-ascii to > something else he'd have to manually add mappings for all the > us-ascii aliases. I think it'd be cleaner (in terms of semantics, > maybe not patch size) to keep "override alist" and "alias alist" > separate. I'm not sure there are two separate lists here. As far as I understand, there is only one MIME charset name. All the other aliases are not intended for MIME, and should never be used for MIME. For compatibility, we could add overrides for such aliases, if they are common, though, but conceptually it is wrong to think of them as "aliases". They are "overrides". However, I do agree that using user variables for this is a bad idea -- if the user customizes the variable in one Gnus version, and we add compatibility mappings in a later version, they will miss the new mappings. However, I can think of users that do not want to map ansi_x3.4-1968 to us-ascii, for the same reason some users do not want to map iso-8859-9 to windows-1254, so whatever we come up with, it should be possible for users to customize it. /Simon