GNOME Bugzilla – Bug 616515
Understand URL open parameters
Last modified: 2010-05-26 07:48:04 UTC
It would be nice if evince understood pdf URL open parameters as described in http://kb2.adobe.com/cps/317/317300.html . I must admit that I don't quite know how you would pass them through from a web browser given that you don't do a plugin (but I am not very knowledgable in that field), but evince file://foo.pdf#page=3 might be made to jump to page three of foo.pdf.
> file://foo.pdf#page=3 might be made to jump to page three of foo.pdf. file://foo.pdf#3 <- that should work with current code
It doesn't seem to with the version I have here (although if it works in development code that would be good enough for me). What about destinations (file:///.../foo.pdf#destination)?
If you are using 2.30 it should work, otherwise it's a bug.
I tested, and http://site.com/foo.pdf#3 worked; file:///path/foo.pdf#3 did not. http://site.com/foo.pdf#page=3 did not, and I couldn't immediately find any pdf files with destination information in them to try out.
Right, it was a bug, file:///path/foo.pdf#3 should work now too.
Hi, would it be possible to check whether exists a file with "#" in its name when checking the name for destination? I have a downstream bug in which reporter can not open file "A#21.pdf" in evince 2.30.1 (see https://bugzilla.redhat.com/show_bug.cgi?id=587495). Regards Marek
(In reply to comment #6) > Hi, > > would it be possible to check whether exists a file with "#" in its name when > checking the name for destination? > I have a downstream bug in which reporter can not open file "A#21.pdf" in > evince 2.30.1 (see https://bugzilla.redhat.com/show_bug.cgi?id=587495). Yes, fixed in master and gnome-2-30 branch now. Thanks!
*** Bug 619658 has been marked as a duplicate of this bug. ***