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 21:06:55 -0700 [thread overview]
Message-ID: <quack.20070320T2106.lth8xdrp7ds@roar.cs.berkeley.edu> (raw)
In-Reply-To: <871wjkwbva.fsf@mocca.josefsson.org>
>>>>> On 2007-03-20 01:35 PDT, Simon Josefsson writes:
Simon> I'm not sure there are two separate lists here. As far
Simon> as I understand, there is only one MIME charset name.
Simon> All the other aliases are not intended for MIME, and
Simon> should never be used for MIME. For compatibility, we
Simon> could add overrides for such aliases, if they are
Simon> common, though, but conceptually it is wrong to think
Simon> of them as "aliases". They are "overrides".
Okay, whichever way works :) Thanks,
--
Karl 2007-03-20 21:05
next prev parent reply other threads:[~2007-03-21 4:06 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
2007-03-20 8:35 ` Simon Josefsson
2007-03-21 4:06 ` Karl Chen [this message]
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.20070320T2106.lth8xdrp7ds@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).