From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Kenichi Handa <handa@ni.aist.go.jp>
Cc: jasonr@gnu.org, topia@clovery.jp, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: imap.el: international/utf-7.el vs. gnus/utf7.el
Date: Tue, 20 Nov 2007 22:08:12 +0100 [thread overview]
Message-ID: <v98x4socar.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1IpYuE-0001U7-MY@etlken.m17n.org> (Kenichi Handa's message of "Wed, 07 Nov 2007 09:36:30 +0900")
On Wed, Nov 07 2007, Kenichi Handa wrote:
>> > I think the right thing is to uncomment all codes for
>> > utf-7-map in utf-7.el, and modify gnus to use normal
>> > encode/decode-coding-region/string with utf-7-imap.
>> >
>> > I've just committed the former change.
I have modified gnus/utf7.el accordingly:
* utf7.el (utf7-encode, utf7-decode): Use coding system
`utf-7'/`utf-7-imap' from utf-7.el' if available.
> No, don't use utf-7-encode directly but use encode-coding-string.
>
> For instance, this[...] can simply be:
>
> (defun utf7-encode-NEW (string &optional for-imap)
> (encode-coding-string string (if for-imap 'utf-7-imap 'utf-7)))
>
> And the test for the availability is:
>
> (and (coding-system-p 'utf-7) (coding-system-p 'utf-7-imap))
Thanks for the hints.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2007-11-20 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k5p1ho29.wl%topia@clovery.jp>
[not found] ` <472B1AD5.3090006@gnu.org>
[not found] ` <E1IovyW-0001nS-4a@etlken.m17n.org>
2007-11-06 19:53 ` imap.el: international/utf-7.el vs. gnus/utf7.el (was: 23.0.50; utf7-decode failed with non latin-1 charactor) Reiner Steib
2007-11-07 0:36 ` Kenichi Handa
2007-11-20 21:08 ` Reiner Steib [this message]
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=v98x4socar.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=handa@ni.aist.go.jp \
--cc=jasonr@gnu.org \
--cc=topia@clovery.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).