Bug 3967 - Links containing Cyrillic characters are not highlighted properly
Summary: Links containing Cyrillic characters are not highlighted properly
Status: RESOLVED DUPLICATE of bug 3519
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Message View (show other bugs)
Version: 3.16.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2018-02-16 10:15 UTC by George
Modified: 2019-01-02 20:27 UTC (History)
0 users

See Also:

Attachments
screenshot (17.94 KB, image/png)
2018-02-16 10:15 UTC, George 		no flags Details
non-ASCII url bug (7.24 KB, image/png)
2018-02-16 11:18 UTC, Cristian Secară 		no flags Details
test message (725 bytes, text/plain)
2018-02-16 11:25 UTC, George 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description George 2018-02-16 10:15:41 UTC 
Created attachment 1846 [details]
screenshot

If there is a link in the message body which contains params with Cyrillic letters it is not highlighted as a whole link but only partially (till the first Cyrillic letter).

Please check attached screenshot.

Looking at the same message in Gmail's UI I see the link highlighted properly.
Comment 1 Paul 2018-02-16 10:48:58 UTC 
Attach an example message if you can - much more useful than a screenshot alone.
Comment 2 Cristian Secară 2018-02-16 11:18:57 UTC 
Created attachment 1847 [details]
non-ASCII url bug

This bug seems to be related to all (?) non-ASCII characters, not only Cyrillic and is present since ever both in Claws Mail and Sylpheed. I assume there were previous reports on this (for sure it was for Sylpheed), but never addressed.

My signature shows always broken and it uses only Latin characters – see attached snapshot.

Cristi
Comment 3 George 2018-02-16 11:25:47 UTC 
Created attachment 1848 [details]
test message

Attaching a sample message exported from claws-mail (with private info sanitized)
Comment 4 Andrej Kacian 2019-01-02 20:27:18 UTC 
Already fixed in #3519.

*** This bug has been marked as a duplicate of bug 3519 ***
Note You need to log in before you can comment on or make changes to this bug.