Summary: | www links are created incorrectly from e-mail text | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Albert Astals Cid <aacid> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | arekm, kollix, montel |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | 4.10.1 | |
Sentry Crash Report: |
Description
Albert Astals Cid
2009-09-06 22:59:31 UTC
This is not a bug, it's a feature ;-) The URL detection was enhanced regarding RFC 3986, appendix-C http://tools.ietf.org/html/rfc3986#appendix-C which says In some cases, extra whitespace (spaces, line-breaks, tabs, etc.) may have to be added to break a long URI across lines. The whitespace should be ignored when the URI is extracted. So the current algorithm skips whitespace until it detects end-of-URL and an URL can be enclosed in different kind of brackets or quotes, e.g. (xx) <xx> [xx] etc. There's no line break in this case Also it's "obvious" from a url point of view that www.knovel.cominmycase is incorrect as cominmycase is not a valid domain name, not sure there's a easy way to check logical "validity" of urls Anyway i'm reopening the bug, i can show it to 100 people and almost 90 (if not 100) will agree it's not the expected behaviour. I agree that it is not the expected behavior but it is the correct behavior. The only way to check for valid top level domains would be to check against a list and since the TLDs change this would fail. All other methods will be a "best guess" approach. This bug exists also in kde 4.6.0 + kmail 4.4.10. Text: Test (www.aaa.pl, costam, innecostam) test. is visible as: Test (www.aaa.pl,costam,innecostam) test. Spaces are stripped, everyting inside () is treated as link but the link points to nowhere - to "http:" actually (and not even http://www.aaaa.pl,costam,innecostam). So there are two bugs here. Fixed in 4.10.1 Setting status according to comment #5. |