Bug 321424

Summary: the Quoted Message Text did not add the Quote indicator when reply the mail
Product: [Applications] kmail2 Reporter: TOM Harrison <l12436.tw>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: montel, shai
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description TOM Harrison 2013-06-20 12:09:14 UTC 
this a function error.
i think the %QUOTE will add the quote indicator automatically
but since i use the kmail, it did not add.
is there any settings i missed? or the quote indicator is not working ?

Reproducible: Always

Steps to Reproduce:
1.replay the mail
2.you will see the quoted message did not add the quote indicator
Comment 1 TOM Harrison 2013-06-20 12:11:50 UTC 
when i use the add quote characters, the quoted message text format will change.
Comment 2 TOM Harrison 2013-06-20 12:13:47 UTC 
and the quoted message will remove the old quoted characters that has been exists when the mail is received
Comment 3 Laurent Montel 2013-06-27 14:20:06 UTC 
Reply in html ?
Which quote do you use ?
Comment 4 TOM Harrison 2013-06-27 14:34:44 UTC 
'>'
the default setting of repy quote.
it not work if the mail is text mail
Comment 5 TOM Harrison 2013-06-27 15:04:18 UTC 
this problem seem solved in 4.10.80.
but it cause another problem.
the all chinese word in quote message are all garbled.
i think it a bug in 4.10.80
Comment 6 Laurent Montel 2013-06-28 09:39:35 UTC 
So reopen an other bug
and give an testcase
thanks
Comment 7 TOM Harrison 2013-06-28 10:25:46 UTC 
the garbled text is cause from the main which can turn to html type.
it is a known bug?
Comment 8 TOM Harrison 2013-06-28 10:26:31 UTC 
wrong: the garbled text is cause from the main which can turn to html type.
correct: the garbled text is cause from the mail which can turn to html type.

sorry for the wrong word
Comment 9 Laurent Montel 2013-07-19 11:05:54 UTC 
*** Bug 322461 has been marked as a duplicate of this bug. ***