Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Chen <quarl@cs.berkeley.edu>
To: ding@gnus.org
Subject: charset ANSI_x3.4-1968, et al
Date: Sat, 17 Mar 2007 18:41:14 -0700	[thread overview]
Message-ID: <quack.20070317T1841.lthd537s4zp@roar.cs.berkeley.edu> (raw)


Dear Gnus developers, I've been starting to receive a lot of
emails from cron [1] with this header:

 Content-Type: text/plain; charset=ANSI_X3.4-1968

I get the message: Unknown charset: ANSI_X3.4-1968

According to RFC 1345, "ANSI_X3.4-1968", along with other names,
are aliases for US-ASCII, and actually, "ANSI_X3.4-1968" is the
official name (though according to
http://www.iana.org/assignments/character-sets, "US-ASCII" is the
preferred MIME name).

Could you consider something such as the patch below, which works
for me:


--- mm-util.el	17 Mar 2007 18:08:14 -0700	7.62
+++ mm-util.el	17 Mar 2007 18:27:45 -0700	
@@ -641,8 +641,9 @@
    ((and allow-override
 	 (let ((cs (cdr (assq charset mm-charset-override-alist))))
 	   (and cs (mm-coding-system-p cs) cs))))
-   ;; ascii
-   ((eq charset 'us-ascii)
+   ;; ascii (see RFC 1345)
+   (memq charset '(us-ascii ansi_x3.4-1968 ansi_x3.4-1986 iso-ir-6 iso646-us
+                            iso_646.irv:1991 us ibm367 cp367 csascii))
     'ascii)
    ;; Check to see whether we can handle this charset.  (This depends
    ;; on there being some coding system matching each `mime-charset'


Regards, Karl

[1] This is now happening on multiple systems (which are all
    Debian).  cron appears to be using the default locale name.
    On Linux, you can get the string ANSI_x3.4-1968 if you run
    "LC_CTYPE=C locale charmap".




             reply	other threads:[~2007-03-18  1:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-18  1:41 Karl Chen [this message]
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
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.20070317T1841.lthd537s4zp@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).