From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: Content-Transfer-Encoding
Date: 13 Jan 2000 18:52:16 -0500 (EST) [thread overview]
Message-ID: <yosuembledhr.fsf@jpl.org> (raw)
In-Reply-To: Shigeki Uno's message of "14 Jan 2000 02:02:02 +0900"
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
>>>>> In <86vh4xx5v9.fsf@mediawars.ne.jp>
>>>>> Shigeki Uno <shigeki@mediawars.ne.jp> wrote:
>> (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. :-\
It is defined in mm-bodies.el, but it looks like an internal variable.
We japanese want it to be an user option and the default value is set
as follows:
(defcustom mm-body-charset-encoding-alist
'((iso-2022-jp . 7bit) (iso-2022-jp-2 . 7bit))
"Alist of MIME charsets to encodings.
Valid encodings are `7bit', `8bit', `quoted-printable' and `base64'."
:type '(repeat (cons (symbol :tag "charset")
(choice :tag "encoding"
(const 7bit)
(const 8bit)
(const quoted-printable)
(const base64))))
:group 'mime)
> 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.
Eh, can't you read such messages with Gnus 5.8.4? I can do it without
any customizing nor modifications...
[-- Attachment #2: Type: text/plain, Size: 107 bytes --]
うの-ｓａｎ, ｃａｎ'ｔ ｙｏｕ ｒｅａｄ ｔｈｉｓ ｌｉｎｅ?
[-- Attachment #3: Type: text/plain, Size: 35 bytes --]
--
~{I=8T?KC@~} <yamaoka@jpl.org>
next prev parent reply other threads:[~2000-01-13 23:52 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 ` Content-Transfer-Encoding Shigeki Uno
2000-01-13 23:52 ` Katsumi Yamaoka [this message]
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=yosuembledhr.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).