Dieter Maurer wrote at 2013-1-15 12:33 +0100:
Dieter Maurer wrote at 2013-1-13 11:10 +0100:
>================================================================
>Dear Bug Team!
>
>
>I have found a bug in the XEmacs package "vm":
>
>RFC 2047 requires in its section 5 that "encoded-words"
>must be separated from ordinary text by linear white space
>but "vm" fails to do so.
>
>The bug in in function "vm-mime-encode-words" (from
"vm-mime.el").
>It can be reproduced by a call to "vm-mime-encode-words-in-string"
>(which internally calls "vm-mime-encode-words"). Example:
>
> (vm-mime-encode-words-in-string "aÄoö")
>---> "aÄoö"
>
>The correct result would be:
>
> "aÄoö"
This bug seems to be fixed in the "vm" trunk version
("http://bazaar.launchpad.net/~vm/vm/trunk/view/head:/lisp/vm-mime.el").
I have copied over "vm-mime-charset-to-coding" and
"vm-mime-encode-words" (from "vm-mime-el") and
"vm-mime-encode-headers-words-regexp" (from "vm-vars.el") into
my XEmacs installation and initial tests look promising.
Meanwhile, I have encountered very strange behavior:
After the above change, "vm" can no longer persist
mark changes for some messages which use RFC 2047.
Example:
A message is newly received and marked with "N" ("new").
I read the message, the mark is correctly changed to " ".
When I then save the folder, leave "vm" and reenter "vm",
the message may again be marked with "N".
It seems that not all messages using RFC 2047 are affected, only
some of them.
I have no idea how my change could result in this behavior: the
changed functions affect only encoding and should have nothing
to do with mark handling. Maybe, the "X-VM-v5-Data" got somehow confused
by the change.
For the moment, I have reverted to the old state.
I may come back in the future when I have found time to look more
closely into this behaviour.
--
Dieter
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta