> There was a double encoding: vm-read-imap-folder-name calls vm-imap-
> encode-list-to-spec, which calls utf7-encode and thus returns an already
> encoded string to a function that normally takes and unencoded string.
Then I guess my patch didn't apply fully. The patch you sent me has more
utf7-encode's than mine, not less.
I have now pushed the changes into revision 1335 on the trunk. Let us see
if you are happy with that.
khinsen writes:
> There was a double encoding: vm-read- imap-folder- name calls vm-imap- list-to- spec, which calls utf7-encode and thus returns an already
> encode-
> encoded string to a function that normally takes and unencoded string.
Then I guess my patch didn't apply fully. The patch you sent me has more
utf7-encode's than mine, not less.
I have now pushed the changes into revision 1335 on the trunk. Let us see
if you are happy with that.
Cheers,
Udaay