The link to a local file does not work in version 3.2. It works in 3.1.2 and in other pdf reader.
Most probably a
currently former known open issue that should now be fixed see entry Local Hyperlink problem below or closed issue
Does it add the
file:// prefix part way through the link ?
I have the same problem.
A temporary workaround
(works for 3.2 but not 3.1.2 and may not be valid in a later 3.2.1)
as mentioned in above reported issue,
is to try
/../ prefix which will be translated as another relative child of the same parent
Recently viewing a pdfTeX + eplain created file with a local figure figure.jpg :
Copy Link Address gives
Clicking in the figure gives the error:
(full file path and name) not found.)
This is just today - been using Sumatra with inverse search for many years!
Previously clicking the figure opened figure.jpg in the default viewer.
Currently version 3.2 - switched from 3.3.13146 updates when I got the error
Unfortunate relative file bug introduced with major overhaul of MuPDF that changed some inter-related abilities. For LaTeX users I would suggest that unless there is a major advantage to you in 3.2, then consider using both 3.1.2 and latest pre-release rather than 3.2.
One could be portable and the other installed or both installed or both portable, those choices are generally exclusive.
Reported 6 months ago, but the dev doesn’t seem to have got around to it yet:
i created a link with this structure (file///c:\evolution\cattura.jpg) on a word file.
after printing the file into pdf and opened with acrobat reader works fine.
if i try to open the link with sumatra pdf it doesn’t work. i can see that the program try to open a link composed with the file position (my desktop) and then the correct link.
can someone help me?
As mentioned by the dev above, can’t use absolute links. Unfortunately since 3.2 there’s a known bug with relative links too:
@kjk: Any chance we can have this fixed soon?
As @SumatraPeter has shown and Acrobat should have requested authority to open such a link
There are pitfalls in using such machine specific links as when run unchecked they can target known PC commands by a malicious author.
For that reason version 3.1.2 should allow a subset of relative links, It is not a secure system since relative links can be crafted to try working up/down different paths.
I personally would like ALL links to show their true target and be a user choice/option to allow without confirmation.
You may note that IF you need a relative link to workaround current bug then you need it to pretend it is a sibling I.e pretend it is a half brother/sister of the child.