When replying with the HTML editor, the text/plain part contains an extra ">"

In IMP, if I use the HTML editor as my default editor, when

Fri, 02 Sep 2011 14:55:29 +0000

In IMP, if I use the HTML editor as my default editor, when I reply to an e-mail, my reply is sent in two forms : text/plain and text/html. The text/html version contains one single ">" (encoded as "> ") at the beginning of each quoted line. The text/plain version contains *two* ">" : ">>" at the first line "> >" for the remaining lines. I can see the same thing if I switch back and forth from the HTML editor to the text editor in the WEB composing page. If my default editor is the text editor, the reply has one ">". I switch to HTML, then again to text, and this time two ">" appears.

Cannot reproduce in IMP 5.

Mon, 05 Sep 2011 14:54:27 +0000

Cannot reproduce in IMP 5.

I will try to produce some case test, if I can dig into the

Tue, 06 Sep 2011 06:43:21 +0000

I will try to produce some case test, if I can dig into the code.

> I will try to produce some case test, if I can dig into th

Tue, 06 Sep 2011 07:27:29 +0000

> I will try to produce some case test, if I can dig into the code. If truly using Framework 3 (e.g. IMP 4), this code is no longer maintained for bug fixes like this. As Jan mentions, this is not seen in IMP 5.

>> I will try to produce some case test, if I can dig into t

Tue, 06 Sep 2011 07:54:48 +0000

>> I will try to produce some case test, if I can dig into the code. > > If truly using Framework 3 (e.g. IMP 4), this code is no longer > maintained for bug fixes like this. As Jan mentions, this is not > seen in IMP 5. Sorry, I did a mistake when I left the bug report, I am using the latest version, IMP 5.0.11 and Horde 4.0.9. My fault. The problem is that the reply Message is quoted twice when using HTML : with ">" symbols (coded with ">") *and* by using a global

tag added in the function replyMessageText in imp/lib/Compose.php (~ line 1624) When you switch back to text composing, the message is filtered by Horde_Text_Filter::filter ;
is turned into ">" and ">" in another ">". So I have two ">" at the end of the process. I think the reply message shoud contain only a
tag, *or* ">" at the beginnning of each line, but not both. If you can't reproduce that, perhaps something in my configuration generates this (small) bug ?

I don't see this after this commit: commit fc26681c1f61fb

Tue, 06 Sep 2011 23:21:37 +0000

I don't see this after this commit: commit fc26681c1f61fb9ac720b744d94e2f437aa1c814 Author: Michael M Slusarz Date: Tue Sep 6 13:46:24 2011 -0600 More intelligent quoting of flowed text messages sent in HTML format. Even if i did see, not really worth to track down. HTML -> Text conversion is all sorts of complicated - I'm not going to dwell on small inconsistencies in the converted product, absent someone providing easy-to-apply patches to fix allegedly bad behavior.

I yesterday had double quotes, too. Starting an reply in

Wed, 07 Sep 2011 06:55:32 +0000

I yesterday had double quotes, too. Starting an reply in text-mode, switching to HTML and back to text again, inserts extra > which was not there at the beginning.

> I yesterday had double quotes, too. > > Starting an repl

Wed, 07 Sep 2011 07:21:26 +0000

> I yesterday had double quotes, too. > > Starting an reply in text-mode, switching to HTML and back to text > again, inserts extra > which was not there at the beginning. Once you start doing these kind of multiple conversions, all bets are off. You really shouldn't be converting from text -> html -> text. You are going to lose all sorts of formatting, as the warnings clearly indicate to you.

> Once you start doing these kind of multiple conversions, a

Wed, 07 Sep 2011 08:41:02 +0000

> Once you start doing these kind of multiple conversions, all bets are > off. You really shouldn't be converting from text -> html -> text. > You are going to lose all sorts of formatting, as the warnings > clearly indicate to you. But already in first conversion text->html the quotes are doubled. The first level will be represented by the blue line (correct), the second level has redundant > (there never was a second level)

>> Once you start doing these kind of multiple conversions,

Wed, 07 Sep 2011 09:03:51 +0000

>> Once you start doing these kind of multiple conversions, all bets are >> off. You really shouldn't be converting from text -> html -> text. >> You are going to lose all sorts of formatting, as the warnings >> clearly indicate to you. > > But already in first conversion text->html the quotes are doubled. > The first level will be represented by the blue line (correct), the > second level has redundant > (there never was a second level) Don't see this.

>>> Once you start doing these kind of multiple conversions,

Wed, 07 Sep 2011 09:05:45 +0000

>>> Once you start doing these kind of multiple conversions, all bets are >>> off. You really shouldn't be converting from text -> html -> text. >>> You are going to lose all sorts of formatting, as the warnings >>> clearly indicate to you. >> >> But already in first conversion text->html the quotes are doubled. >> The first level will be represented by the blue line (correct), the >> second level has redundant > (there never was a second level) > > Don't see this. Actually, I guess this could happen if the original text was not flowed text. But if that is the case, the '>' don't mean anything. In other words: you can't assume that they are quoted lines. Either way, there is nothing broken here. This is still all expected behavior.

See screenshot, what I mean...

Wed, 07 Sep 2011 09:19:28 +0000

See screenshot, what I mean...

> See screenshot, what I mean... As mentioned previously,

Wed, 07 Sep 2011 16:03:37 +0000

> See screenshot, what I mean... As mentioned previously, this was already fixed.

>> See screenshot, what I mean... > > As mentioned previou

Thu, 08 Sep 2011 16:46:34 +0000

>> See screenshot, what I mean... > > As mentioned previously, this was already fixed. I confirm, applying the patches (from the git commit) mentioned in the thread earlier solves the bug. Thank you !

Just applied your commit, too. In my case it is working f

Sat, 10 Sep 2011 06:24:13 +0000

Just applied your commit, too. In my case it is working for some mails, for some not. Try to reply to a mail from the bugtracker, then hit HTML-mode, to convert. A short time the body of the mail is able to be seen, then it flushes away and there ist just "Object" to be seen.