[Pidgin] #16107: Incorrect URI handling

[Pidgin]

#16107: Incorrect URI handling
-----------------------+---------------------------
 Reporter:  cron       |       Owner:
     Type:  defect     |      Status:  new
Milestone:             |   Component:  pidgin (gtk)
  Version:  2.10.7     |  Resolution:
 Keywords:  URI, link  |
-----------------------+---------------------------
Description changed by cron:

Old description:

> Pidgin doesn't handle URI's correctly if the URI is encapsulate in
> special characters, such as parenthesis "(" and ")". The lack of a
> leading space before the URI (and after, likely) causes it not be
> recognized as a link, and as such, it can't be clicked on. This effects
> the URIs for the game Unvanquished, which uses the URI "unv://". Known-
> protocol handling does not have this problem. For instance:
>
> (http://somewebpage.com) -Known protocol HTTP will work - this can be
> clicked
> (unv://unvanquishedserver:port) -URI, this will not work and can't be
> clicked
>
> The special characters should not break the recognition of the link, per
> RFC specs: http://tools.ietf.org/html/rfc3986#appendix-A

New description:

 Pidgin doesn't handle URI's correctly if the URI is encapsulated in
 special characters, such as parenthesis "(" and ")". The lack of a leading
 space before the URI (and after, likely) causes it not be recognized as a
 link, and as such, it can't be clicked on. This effects the URIs for the
 game Unvanquished, which uses the URI "unv://". Known-protocol handling
 does not have this problem. For instance:

 (http://somewebpage.com) -Known protocol HTTP will work - this can be
 clicked
 (unv://unvanquishedserver:port) -URI, this will not work and can't be
 clicked

 The special characters should not break the recognition of the link, per
 RFC specs: http://tools.ietf.org/html/rfc3986#appendix-A

--

-- 
Ticket URL: <https://developer.pidgin.im/ticket/16107#comment:1>
Pidgin <https://pidgin.im>
Pidgin