Gnus development mailing list
 help / color / mirror / Atom feed
From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>, ding@gnus.org
Subject: Re: nnimap compatibility issues (UTF-7, msg count, SEARCH vs. group
Date: Fri, 23 May 2003 19:59:39 +0200	[thread overview]
Message-ID: <m31xypfss4.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <rzqissezqlk.fsf@albion.dl.ac.uk> (Dave Love's message of "Tue, 13 May 2003 18:47:03 +0100")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1972 bytes --]

Dave Love <d.love@dl.ac.uk> writes:

>> 1. UTF-7 decoding mangled
>>
>> Here's the IMAP excerpt:
>>
>> 1 CAPABILITY
>> * CAPABILITY IMAP4 IMAP4rev1 LITERAL+ UIDPLUS X-NETSCAPE
>> 1 OK Completed
>> 2 LOGIN "hohohoimnottellingyou" "youdlovetoknow"
>> 2 OK User logged in
>> 3 LIST "" "*%"
>> * LIST (\Noinferiors ) "/" "Trash"
>> * LIST (\Noinferiors ) "/" "Unerw&APw-nscht"
>> ...
>> 3 OK Completed
>>
>> The "Unerw&APw-nscht" string is misdisplayed in the server buffer, it
>> prints as "Unerw.ünscht";
>
> I'm not sure what that means and what exactly goes wrong.  Where is it
> decoded from the utf-7?

I don't know. Can you formulate a more specific question?

>> UTF-7 decoding is on. However, it appears
>> correctly as "Unerwünscht" in other client software, namely Sylpheed
>> 0.8.11claws and Mozilla 1.3. Just in case: CVS 5.10.x Gnus, emacs 21.3.
>
> Did this work before I changed utf7.el recently to cope with more than
> Latin-1?  If so, it's probably a coding conversion confusion, and
> perhaps the dot is a mangled \201 or similar.  Previously the decoder
> returned a unibyte string, which doesn't make much sense.  As far as I
> could tell, that just happened to work by automatic conversion (in a
> Latin-1 session).  You could test it by commenting out
> `mm-enable-multibyte' in `utf7-decode'.  I can't, I'm afraid.

If I comment this one out, then the Unerw.*nscht folder disappears in
the folder list when entering the buffer. And yes indeed, the original
buffer showed \201 before the other unprintable character.

So somehow the character set the folder name was decoded to and the
buffer/display's character set didn't match?

But my bigger concern however is that I can't fetch messages from that
server. See my previous mail.

I can't really help myself out because my Elisp isn't even good enough
to fully understand the code, and MULE isn't my strong point either.

-- 
Matthias Andree



  reply	other threads:[~2003-05-23 17:59 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 [this message]
2003-05-25 16:47     ` Dave Love
2003-05-27 14:41       ` Matthias Andree
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=m31xypfss4.fsf@merlin.emma.line.org \
    --to=ma@dt.e-technik.uni-dortmund.de \
    --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).