Gnus development mailing list
 help / color / mirror / Atom feed
From: Shigeki Uno <shigeki@mediawars.ne.jp>
Subject: Re: Content-Transfer-Encoding
Date: 14 Jan 2000 02:02:02 +0900	[thread overview]
Message-ID: <86vh4xx5v9.fsf@mediawars.ne.jp> (raw)
In-Reply-To: <yosuu2kixlya.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:
 
> (setq mm-body-charset-encoding-alist
>       '((iso-2022-jp . 7bit) (iso-2022-jp-2 . 7bit)))
 
Thanks to Yamaoka-san, It works great. *WOW*.

# This relate to mm-bodies.el e-lisp file, doesn't this ? 
# I couldn't find that. :-\

-------- result --------
To: Shigeki Uno <shigeki@mediawars.ne.jp> 
Subject: test
From: Shigeki Uno <shigeki@mediawars.ne.jp>
Date: 14 Jan 2000 01:03:53 +0900
User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5
Message-ID: <86zouavtzq.fsf@mediawars.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-2022-jp
Lines: 7
Xref: nana outbox:346
----- end of result -----

BTW, If I'd like to read *quoted-printable* encoded e-mail messages 
someone sent, are there any way to solve this problem (say, decode 
messages) ?  No way ?

Some *quoted-printable* encoded mails are sometimes sent to me. 

Thanks.
-- 
Shigeki Uno <mailto:shigeki@mediawars.ne.jp>




  reply	other threads:[~2000-01-13 17:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-13 10:23 Content-Transfer-Encoding Shigeki Uno
2000-01-13 11:14 ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-13 17:02   ` Shigeki Uno [this message]
2000-01-13 23:52     ` Content-Transfer-Encoding Katsumi Yamaoka
2000-01-14 18:18       ` Content-Transfer-Encoding Shigeki Uno
2000-04-21 13:22       ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-21 19:24         ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22  0:16           ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2000-04-22  8:43             ` Content-Transfer-Encoding Pavel Janik ml.
2000-04-22 12:28               ` Content-Transfer-Encoding Lars Magne Ingebrigtsen
2001-01-09 10:37 content-transfer-encoding vvv

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=86vh4xx5v9.fsf@mediawars.ne.jp \
    --to=shigeki@mediawars.ne.jp \
    /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).