From: Karl Chen <quarl@cs.berkeley.edu>
To: ding@gnus.org
Subject: Re: charset ANSI_x3.4-1968, et al
Date: Tue, 20 Mar 2007 00:50:19 -0700 [thread overview]
Message-ID: <quack.20070320T0050.lthr6rks69w@roar.cs.berkeley.edu> (raw)
In-Reply-To: <87lkhtwrm2.fsf@mocca.josefsson.org>
>>>>> 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.
--
Karl 2007-03-20 00:43
next prev parent reply other threads:[~2007-03-20 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 1:41 Karl Chen
2007-03-18 19:54 ` Simon Josefsson
2007-03-18 22:54 ` Reiner Steib
2007-03-19 0:02 ` Karl Chen
2007-03-19 8:43 ` Simon Josefsson
2007-03-20 7:50 ` Karl Chen [this message]
2007-03-20 8:35 ` Simon Josefsson
2007-03-21 4:06 ` Karl Chen
2007-03-18 23:57 ` Karl Chen
2007-03-19 8:45 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=quack.20070320T0050.lthr6rks69w@roar.cs.berkeley.edu \
--to=quarl@cs.berkeley.edu \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).