From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: Invalid coding system: unicode-1-1-utf-7
Date: Thu, 04 Aug 2005 11:42:21 +0900 [thread overview]
Message-ID: <b4mll3ipgmq.fsf@jpl.org> (raw)
In-Reply-To: <9eek9bqq1j.fsf@gowron.rz-berlin.mpg.de>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
>>>>> In <9eek9bqq1j.fsf@gowron.rz-berlin.mpg.de> Jochen Küpper wrote:
> In my .gnus I have
> ,----
>| (add-to-list 'mm-charset-synonym-alist (if (and (not (mm-coding-system-p 'unicode-1-1-utf-7))
>| (mm-coding-system-p 'utf-7))
>| '(unicode-1-1-utf-7 . utf-7)))
> `----
I loaded utf-7.el and tried it.
> However, when sending (S o m) messages with the unicode-1-1-utf-7
> coding system, Gnus gives the following error (and stops):
> ,----
>| mm-encode-body: Invalid coding system: unicode-1-1-utf-7
> `----
Though I couldn't find the way to reproduce it using `S o m', it
seems to be the same to encode the part like the following:
<# part type="text/plain" charset=unicode-1-1-utf-7 disposition=inline>
jugemujugemugokonosurikirekaijarisuigyonosuigyomatsuungyomatsu...
Gnus still confuses `charset' with `coding system' in several
places I think, and the problem is caused by one of them. Does
the following patch help?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 320 bytes --]
--- mm-bodies.el~ 2005-07-05 22:36:09 +0000
+++ mm-bodies.el 2005-08-04 02:39:45 +0000
@@ -93,6 +93,7 @@
(save-excursion
(if charset
(progn
+ (setq charset (mm-charset-to-coding-system charset))
(mm-encode-coding-region (point-min) (point-max) charset)
charset)
(goto-char (point-min))
next prev parent reply other threads:[~2005-08-04 2:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 10:21 Jochen Küpper
2005-08-04 2:42 ` Katsumi Yamaoka [this message]
2005-08-04 3:05 ` Katsumi Yamaoka
[not found] ` <b4m3bpqpfkx.fsf-NvgVpDro27E@public.gmane.org>
2005-08-04 20:33 ` Jochen Küpper
2005-08-05 6:58 ` Katsumi Yamaoka
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=b4mll3ipgmq.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).