After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 378085 - problem with external links when they contain a "%"
problem with external links when they contain a "%"
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
0.6.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-22 11:24 UTC by Jonh Wendell
Modified: 2006-12-23 12:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Jonh Wendell 2006-11-22 11:24:05 UTC 
This bug report was opened in Ubuntu (http://launchpad.net/bugs/71970):

I have a pdf document with plenty of hyperlinks like "http://en.wikipedia.org/wiki/Arcade%20game".

When use xpdf, if I click on one of these links, a browser starts at the correct address.

However, if I use evince, the "%" sign is escaped to "%25", which results in the following (incorrect) url: "http://en.wikipedia.org/wiki/Arcade%2520game"

There is attached (in the Ubuntu bug) a sample pdf to illustrate this behavior.
Comment 1 John Pye 2006-12-21 14:21:52 UTC 
I can confirm this bug. I am using Ubuntu 6.10. ALL of the links in the following PDF are broken:

http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf (1.6M)

(from the page http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX)

These links all contain '?' characters which are being url-encoded somewhere en route from evince to firefox, causing the '?' to be replaced by '%3F' by the time the URL appears in the firefox address bar. Maybe this is a inter-process-communication bug, or something like that.

When I copy link location from evince and paste it manually, the URL is correct, and works. Only when I click directly does it fail.

Cheers
JP
Comment 2 Carlos Garcia Campos 2006-12-23 12:26:29 UTC 
It's fixed in cvs head now. Thanks for the bug report.