Subject: bug#5458: closed (Re: bug#5458: Unknown charset: ansi_x3.4-1968)

From: [email-masked] (GNU bug Tracking System)
Date: Thu, 30 Jun 2011 01:39:01 +0000

Your bug report

#5458: Unknown charset: ansi_x3.4-1968

which was filed against the emacs,gnus package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
5458: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5458
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#5458: Unknown charset: ansi_x3.4-1968
From: Lars Magne Ingebrigtsen <[email-masked]>
To: [email-masked]
Cc: [email-masked], [email-masked], [email-masked]
Date: Thu, 30 Jun 2011 03:38:03 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Anyway, I just grepped for "Unknown charset", and there was just one
instance -- `mm-charset-to-coding-system' -- so I made that one map
ansi_x3.4 to ASCII.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Subject: Unknown charset: ansi_x3.4-1968
From: [email-masked]
To: [email-masked]
Date: Sat, 23 Jan 2010 13:36:07 +0800
List-Id: <debbugs-submit.debbugs.gnu.org>

X-debbugs-cc: [email-masked], [email-masked]

How could emacs/gnus not recognize this charset, made by cronjobs at a major
hosting provider?

From: [email-masked] (Cron Daemon)
To: [email-masked]
Subject: Cron <jidanni1@psX-X> echo wow
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <MAILTO=jidanni1>
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/jidanni1>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=jidanni1>
X-Gnus-Mail-Source: maildir:~/Maildir/new
Message-Id: <[email-masked]>
Date: Fri, 22 Jan 2010 21:30:01 -0800 (PST)
Lines: 2
Xref: jidanni1.jidanni.org mail.misc:27273

wow