From: Matthias Andree <matthias.andree@gmx.de>
Subject: Re: nnimap compatibility issues (UTF-7, msg count, SEARCH vs. group
Date: Tue, 27 May 2003 16:41:25 +0200 [thread overview]
Message-ID: <20030527144124.GA14042@merlin.emma.line.org> (raw)
In-Reply-To: <rzqwugfht2c.fsf@albion.dl.ac.uk>
On Sun, 25 May 2003, Dave Love wrote:
> You said `misdisplayed in the server buffer', but in the text above
> which appears to be from the server, it isn't decoded, and shouldn't
> be.
Emacs 21.3.1 here.
This is how the IMAP server buffer looks like with unmodified utf7.el
revisions 6.1 and 6.2 from CVS, the X after the \216 is a square box
with dashed line style.
K 0: Entwurf
K 0: Gesendet
U 0: INBOX
K 0: Papierkorb
K 0: Postausgang
K 0: Trash
K 0: Unerw\216Xnscht
Now I apply this patch to utf7.el and reinstall things and restart
Emacs:
Index: utf7.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/utf7.el,v
retrieving revision 6.2
diff -u -r6.2 utf7.el
--- utf7.el 9 May 2003 20:37:56 -0000 6.2
+++ utf7.el 27 May 2003 14:15:19 -0000
@@ -219,7 +219,7 @@
(with-temp-buffer
(insert string)
(utf7-decode-internal for-imap)
- (mm-enable-multibyte)
+; (mm-enable-multibyte)
(buffer-string))))
(provide 'utf7)
This is what the IMAP server buffer looks like now, with the patch applied:
K 0: Entwurf
K 0: Gesendet
U 0: INBOX
K 0: Papierkorb
K 0: Postausgang
K 0: Trash
This is the complete server buffer, the "Unerwünscht" folder is missing.
So removing the mm-enable-multibyte clearly makes things worse, by
hiding a folder.
> > So somehow the character set the folder name was decoded to and the
> > buffer/display's character set didn't match?
>
> Something has decoded the multibyte text produced by the utf-7
> decoding (i.e. it has been doubly decoded). I assume this is in the
> imap code, but I can't test that.
Assuming it isn't the utf7-decoder, where do I look?
> I still don't know if it worked before I made changes to utf7.el. Did
> it work? If so, I guess the change should be reverted until someone
> can look at the imap code, but that means that mailbox names can only
> be Latin-1 even when your Emacs can support more.
I believe the 6.1 -> 6.2 changes in utf7.el are fine. They make no
visible difference AFAICT. Unless my emacs used the wrong files.
I've dug a little deeper. If I try to choose this group (any group
besides INBOX), I get a "can't select" complaint.
So there is something deep within imap.el or nnimap.el that doesn't
cooperate with this server anyways.
--
Matthias Andree
next prev parent reply other threads:[~2003-05-27 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 0:24 nnimap compatibility issues (UTF-7, msg count, SEARCH vs. group select) Matthias Andree
2003-05-13 17:47 ` nnimap compatibility issues (UTF-7, msg count, SEARCH vs. group Dave Love
2003-05-23 17:59 ` Matthias Andree
2003-05-25 16:47 ` Dave Love
2003-05-27 14:41 ` Matthias Andree [this message]
2003-05-27 15:37 ` Kai Großjohann
[not found] ` <843cj0e6yo.fsf@lucy.is.informatik.uni-duis?= =?iso-8859-15?q?burg.de>
2003-05-28 0:41 ` Matthias Andree
2003-05-28 9:08 ` Kai Großjohann
2003-05-29 17:52 ` Dave Love
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=20030527144124.GA14042@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
/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).