From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: [Fwd: UTF7 decode error in Gnus with IMAP]
Date: Fri, 09 Dec 2005 17:23:13 +0100 [thread overview]
Message-ID: <iluy82ub5ou.fsf@latte.josefsson.org> (raw)
In-Reply-To: <E1Ej6Cs-0001Sp-IZ@fencepost.gnu.org> (Richard M. Stallman's message of "Sun, 04 Dec 2005 21:35:58 -0500")
"Richard M. Stallman" <rms@gnu.org> writes:
> Would you please DTRT about this, then ack?
I believe no action is required, see below.
Kevin Rodgers <ihs_4664@yahoo.com> writes:
> 1. Is it safe to suggest to this user to (setq imap-use-utf7 nil)?
I believe it is safe, if used consistently. If you toggle the
variable, existing groups will rename themselves. Of course, you'll
loose non-ascii features.
> 2. Should imap-utf7-decode work on this string with non-nil imap-use-utf7?
> It contains only ASCII characters, but the "&" triggers the error:
>
> signal(error ("Unable to convert from Unicode"))
> error("Unable to convert from Unicode")
> utf7-u16-latin1-char-converter()
> utf7-fragment-decode(207 210 t)
> utf7-decode-internal(t)
> utf7-decode("Public Folders/Business Units/SC WW Sales and
> Marketing/Reporting/Commissions/2005 Commissions/2005 Adjustments/*2005
> Closed Adjustments/*closed*7.1.05 through 7.31.05/*closed*EPIC Tut
> Systems Videotele &IBM- TMS320C6415TGLZ1" t)
That isn't valid UTF-7 a'la IMAP, so I think the error is correct.
Imap.el call utf7-decode in a condition-case, so in practice you
shouldn't see the error.
How does this cause any real problem?
next prev parent reply other threads:[~2005-12-09 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 2:35 Richard M. Stallman
2005-12-09 16:23 ` Simon Josefsson [this message]
2005-12-13 21:46 ` Kevin Rodgers
2005-12-14 14:18 ` Simon Josefsson
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=iluy82ub5ou.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.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).