Bug 369043 - links to local files do not interpret %20 as space
Summary: links to local files do not interpret %20 as space
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.24.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-09-19 10:38 UTC by lorenzo233
Modified: 2018-12-17 03:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lorenzo233 2016-09-19 10:38:26 UTC
I've a pdf, generated with pandoc, wich links to another pdf. Since the name of the linked pdf contains spaces, the URI is formatted like this: file:///home/me/file%20linked.pdf . okular reads %20 as %20, not as spaces and thus doesn't find the file. 

Interestingly this error does not happen (spaces are read correctly) when I link a file in the local directory. (e.g.: when opening a file in /home/me, okular opens correctly the link to the file /home/me/file linked.pdf) even though evince tooltip tells me that the URI is formatted the same way

Reproducible: Always

Steps to Reproduce:
1. generate a pdf containing a link to another pdf with spaces in its filename
OR
2. download this pdf ( https://www.dropbox.com/s/829zrampnulwdl5/example.pdf?dl=0 )  which links to "good link.pdf" in the current directory and to "bad link.pdf" in /home
AND
3. move two pdfs to those paths

Actual Results:  
error message 'could not open "/home/me/file%20linked.pdf'. file does not exist

Expected Results:  
opens linked pdf
Comment 1 Sebastian 2018-11-17 19:29:17 UTC
Hey Lorenzo,

sorry for responding so late.
The link to the dropbox is dead for me.

If some maintainer looks here it would be beneficial to safe the file here so that it can be tested in the future.

Is it possible that you can upload the file here?

Thanks for your help.

Note: I am no maintainer but from the KDE Bugsquad
Comment 2 Bug Janitor Service 2018-12-02 03:44:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-12-17 03:44:27 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!