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 616515 - Understand URL open parameters
Understand URL open parameters
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
2.30.x
Other Linux
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 619658 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-04-22 13:17 UTC by Michael T
Modified: 2010-05-26 07:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael T 2010-04-22 13:17:40 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.
Comment 1 Carlos Garcia Campos 2010-04-22 15:40:04 UTC
> 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
Comment 2 Michael T 2010-04-22 19:52:03 UTC
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)?
Comment 3 Carlos Garcia Campos 2010-04-23 07:41:27 UTC
If you are using 2.30 it should work, otherwise it's a bug.
Comment 4 Michael T 2010-04-23 09:20:11 UTC
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.
Comment 5 Carlos Garcia Campos 2010-04-25 14:28:09 UTC
Right, it was a bug, file:///path/foo.pdf#3 should work now too.
Comment 6 Marek Kašík 2010-05-07 12:41:33 UTC
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
Comment 7 Carlos Garcia Campos 2010-05-11 12:34:00 UTC
(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!
Comment 8 Carlos Garcia Campos 2010-05-26 07:48:04 UTC
*** Bug 619658 has been marked as a duplicate of this bug. ***