From: enami tsugutomo <enami@ba2.so-net.or.jp>
Cc: ding@ifi.uio.no
Subject: Re: Red Gnus v0.67 is released
Date: 23 Nov 1996 12:31:20 +0900 [thread overview]
Message-ID: <87viaxv65z.fsf@plants-doll.enami.ba2.so-net.or.jp> (raw)
In-Reply-To: Tatsuya Ichikawa / =?ISO-2022-JP?B?GyRCO1RAbkMjOkgbKEI=?='s message of 21 Nov 1996 14:34:36 +0900
Tatsuya Ichikawa / =?ISO-2022-JP?B?GyRCO1RAbkMjOkgbKEI=?= <ichikawa@hv.epson.co.jp> writes:
> rgnus-0.66 spooled mail KANJI character code is 7bit JIS code like below.
Probably, you redefine the function
nnheader-insert-file-contents-literally localy so that it doesn't
decode the language code encoding of incoming mail, doesn't it?
But in Red Gnus 0.67, the function is renamed to
nnheader-insert-file-contents.
enami.
next prev parent reply other threads:[~1996-11-23 3:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-20 23:01 Lars Magne Ingebrigtsen
1996-11-21 5:34 ` Tatsuya Ichikawa / 市川達哉
1996-11-23 3:31 ` enami tsugutomo [this message]
1996-11-25 1:44 ` Tatsuya Ichikawa / 市川達哉
1996-11-21 7:44 ` Erik Selberg
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=87viaxv65z.fsf@plants-doll.enami.ba2.so-net.or.jp \
--to=enami@ba2.so-net.or.jp \
--cc=ding@ifi.uio.no \
/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).