From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: No "Content-Type:"
Date: 16 Jan 2000 19:31:54 -0500 (EST) [thread overview]
Message-ID: <yosu901plerp.fsf@jpl.org> (raw)
In-Reply-To: <86ogaleuse.fsf@mediawars.ne.jp>
>>>>> In <86ogaleuse.fsf@mediawars.ne.jp>
>>>>> Shigeki Uno <shigeki@mediawars.ne.jp> wrote:
> I found *Content-Type: text/plain; charaset="iso-2022-JP"* line
> doesn't exist. And others which cause *unintelligible sequence of
> characters* also doesn't have *Content-Type* line.
You mean about the traditional japanese mails, I think. The body has
japanese plain text (iso-2022-jp, 7bit), but the header does not have
no indicators for it.
The user option `gnus-group-charset-alist' helps such messages only
for news:
(defcustom gnus-group-charset-alist
'(("^hk\\>\\|^tw\\>\\|\\<big5\\>" cn-big5)
("^cn\\>\\|\\<chinese\\>" cn-gb-2312)
("^fj\\>\\|^japan\\>" iso-2022-jp-2)
("^tnn\\>\\|^pin\\>\\|^sci.lang.japan" iso-2022-7bit)
[...]
but is does not work for mail groups. So far I don't know how to fix
the problem. Does anyone?
By the way, T-gnus or other Semi-gnusae can do that. It is controled
by the variable `default-mime-charset'.
--
~{I=8T?KC@~} <yamaoka@jpl.org>
next prev parent reply other threads:[~2000-01-17 0:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-16 18:27 Shigeki Uno
2000-01-16 22:23 ` Kai Großjohann
2000-01-17 8:32 ` Shigeki Uno
2000-01-17 0:31 ` Katsumi Yamaoka [this message]
2000-01-17 9:17 ` Kai Großjohann
2000-01-17 10:12 ` Katsumi Yamaoka
2000-01-17 10:19 ` Katsumi Yamaoka
2000-01-17 11:52 ` Shigeki Uno
2000-01-17 6:48 ` Michael Welsh Duggan
2000-01-17 13:15 ` Solved (was: Re: No "Content-Type:") Shigeki Uno
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=yosu901plerp.fsf@jpl.org \
--to=yamaoka@jpl.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).