Bug 209030

Summary:	long URLs with "-" in kmail are broken: are wrapped and the second part doesn't belong to the link
Product:	[Applications] kmail2	Reporter:	Janet <bugzilla>
Component:	config dialog	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bendj095124367913213465, bjoern, burn.till.skid, kollix, korossy, luigi.toscano, matija, montel
Priority:	NOR
Version:	4.8.4
Target Milestone:	---
Platform:	unspecified
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=271000
Latest Commit:		Version Fixed In:	4.9.2
Bug Depends on:	163609
Bug Blocks:

Description Janet 2009-09-30 22:01:41 UTC

Version:           1.12.1 (using 4.3.1 (KDE 4.3.1), Debian packages)
Compiler:          cc
OS:                Linux (i686) release 2.6.31-1.slh.1-sidux-686

When I insert a long URL (longer than the line break border) that contains one or more "-"  into a mail and save or send the mail the link isn't clickable as whole. The second part that's wrapped is dead, doesn't belong to the link. So links with "-" from kmail mails always have to be pasted into the browser instead of being just clickable.

Comment 1 Martin Koller 2009-10-01 22:03:24 UTC

The problem is twofold:
1) QTextEdit breaks links on inserting at "-". See bug 163609 for a response
   of Nokia on that issue
2) Even if kmail sees a link (probably coming from another mail client) with line-breaks, it should detect these as 1 link.
  I tried to fix the second during fixing bug 202445 but the line break does not work yet. That's somehow not so trivial to fix in the way kmail handles line breaks ...
So I'll keep this issue open to fix the line-break detection in urls.

Comment 2 Oscar Pereira 2010-02-17 23:24:18 UTC

I can confirm this problem in KMail 1.13.0 (KDE 4.4.0, Archlinux packages). 

Seeming as the problem has its roots in a Qt limitation, why not follow the suggestion in bug 79144 and make word wrapping selectable on a per paragraph base?

Comment 3 Matija Šuklje 2010-11-26 17:10:43 UTC

The mentioned QTextEdit bug is currently not seen as a bug by Nokia (closed as "out of scope"), therefore either Nokia has to be persuaded that it *IS* a bug, or another solution has to emerge.

Comment 4 Luigi Toscano 2012-08-20 22:38:07 UTC

Still seen in 4.8.4 (both issues)

Comment 5 Laurent Montel 2012-09-04 05:37:20 UTC

fixed in 4.9.2