Tickets :: [#10481] When replying with the HTML editor, the text/plain part contains an extra ">"

6.0.0-beta1

7/26/25

Summary	When replying with the HTML editor, the text/plain part contains an extra ">"
Queue	IMP
Queue Version	FRAMEWORK_3
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	xavier.montagutelli (at) unilim (dot) fr
Created	09/02/2011 (5076 days ago)
Due
Updated	09/10/2011 (5068 days ago)
Assigned
Resolved	09/05/2011 (5073 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

09/10/2011 06:24:13 AM	michael (dot) groene (at) zel (dot) uni-hannover (dot) de	Comment #15	Reply to this comment
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.

09/08/2011 04:46:34 PM	xavier (dot) montagutelli (at) unilim (dot) fr	Comment #14	Reply to this comment
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 !

09/07/2011 04:03:37 PM	Michael Slusarz	Comment #13	Reply to this comment
See screenshot, what I mean... As mentioned previously, this was already fixed.

09/07/2011 09:19:28 AM	michael (dot) groene (at) zel (dot) uni-hannover (dot) de	Comment #12 New Attachment: quote.png	Reply to this comment
See screenshot, what I mean...

09/07/2011 09:05:45 AM	Michael Slusarz	Comment #11	Reply to this comment
[Show Quoted Text - 10 lines][Hide Quoted Text] 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.

09/07/2011 09:03:51 AM	Michael Slusarz	Comment #10	Reply to this comment
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.

09/07/2011 08:41:02 AM	michael (dot) groene (at) zel (dot) uni-hannover (dot) de	Comment #9	Reply to this comment
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)

09/07/2011 07:21:26 AM	Michael Slusarz	Comment #8	Reply to this comment
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.

09/07/2011 06:55:32 AM	michael (dot) groene (at) zel (dot) uni-hannover (dot) de	Comment #7	Reply to this comment
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.

09/06/2011 11:21:37 PM	Michael Slusarz	Comment #6	Reply to this comment
I don't see this after this commit: commit fc26681c1f61fb9ac720b744d94e2f437aa1c814 Author: Michael M Slusarz <slusarz@curecanti.org> 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.

09/06/2011 07:54:48 AM	xavier (dot) montagutelli (at) unilim (dot) fr	Comment #5	Reply to this comment
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 <blockquote> 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 ; <blockquote> 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 <blockquote> 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 ?

09/06/2011 07:27:29 AM	Michael Slusarz	Comment #4	Reply to this comment
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.

09/06/2011 06:43:21 AM	xavier (dot) montagutelli (at) unilim (dot) fr	Comment #3	Reply to this comment
I will try to produce some case test, if I can dig into the code.

09/05/2011 02:54:27 PM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
Cannot reproduce in IMP 5.

09/02/2011 02:55:29 PM	xavier (dot) montagutelli (at) unilim (dot) fr	Comment #1 Priority ⇒ 1. Low State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ IMP Summary ⇒ When replying with the HTML editor, the text/plain part contains an extra ">" Type ⇒ Bug	Reply to this comment
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.