Bug 316301 - Back apostrophe causes the reply/forward mail to bu cut from the next line.
Summary: Back apostrophe causes the reply/forward mail to bu cut from the next line.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.9.5
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-07 11:42 UTC by leon pollak
Modified: 2017-01-07 21:52 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description leon pollak 2013-03-07 11:42:00 UTC
I received several mails from the Canada correspondent. He uses the back apostrophe in his text, for example"
"He just wants to make sure that there won’t be any surprises" - won't contains the trouble sign. This is the way the line looks like in plain text:
He just wants to make sure that there won=E2=80=99t be any surprises=
.
Now, when this mail is forwarded or replied, everything following this line up to the mail end is not sent.
Deleting ONLY this symbol in the source text before sending gets the thing function properly.

Reproducible: Always

Steps to Reproduce:
1. Receive such mail (I keep it saved and can forward it)
2. Press "reply" or "forward" and send.
3. Other side receives the cropped mail.


Expected Results:  
Normal length mail.

I keep this mail for the possible case reproducing/help.
Comment 1 Denis Kurz 2016-09-24 18:05:48 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:52:54 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.