Bug ID: 369043
           Summary: links to local files do not interpret %20 as space
           Product: okular
           Version: 0.24.0
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general

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
2. download this pdf ( )  which links to
"good link.pdf" in the current directory and to "bad link.pdf" in /home
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

You are receiving this mail because:
You are the assignee for the bug.

Reply via email to