From: Katsumi Yamaoka <yamaoka@ga.sony.co.jp>
Subject: Re: PATCH for mm-util.el
Date: 24 Nov 1998 15:51:55 +0900 [thread overview]
Message-ID: <28r9utshv8.fsf@kchisa.ga.sony.co.jp> (raw)
In-Reply-To: Shenghuo ZHU's message of "24 Nov 1998 01:30:09 -0500"
>>>>> In <2nbtlx1u32.fsf@zsh.cs.rochester.edu>
>>>>> Shenghuo ZHU <zsh@cs.rochester.edu> wrote:
KY> It seems that coding systems and MIME charsets are confused in
KY> mm-decode-coding-* and mm-encode-coding-*.
ZSH> Yes, coding systems, mule charsets, and MIME charsets are confusing.
ZSH> But, IMHO, your solution makes them more confusing and slows down the
ZSH> de/encoding processes.
I think so. :-)
Well, let's make new functions, e.g. mm-decode-mime-charset-*, ...
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~1998-11-24 6:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-24 1:59 Katsumi Yamaoka
1998-11-24 6:30 ` Shenghuo ZHU
1998-11-24 6:51 ` Katsumi Yamaoka [this message]
1998-11-24 10:21 ` Lars Magne Ingebrigtsen
1998-11-24 10:53 ` Katsumi Yamaoka
1998-11-24 11:24 ` Lars Magne Ingebrigtsen
1998-11-24 11:36 ` Katsumi Yamaoka
1998-11-24 16:14 ` Shenghuo ZHU
1998-11-24 19:55 ` Lars Magne Ingebrigtsen
1998-11-24 20:36 ` Shenghuo ZHU
1998-11-25 9:08 ` Lars Magne Ingebrigtsen
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=28r9utshv8.fsf@kchisa.ga.sony.co.jp \
--to=yamaoka@ga.sony.co.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).