I brought this issue up on CTT (comp.text.tex), and the hyperref author
responded (with instructions on how to prevent \href from generating
remote links)...
> Also I find it strange (wrong?) that \href produces a remote goto
> link, because those are supposed to be for links with a file *and* a
> destination in the file. For just linking to the file a URL link
> seems much more appropriate to me.
The response (the ">" are me):
=====
A remote goto link is handled by most PDF viewers directly without
using a web browser as intermediate step.
> Perhaps \href should act more like \url and produce a URL link. That
> is, it should only produce a remote goto link if there is also a
> destination with the file.
The file type is the important issue, not the destination.
I would consider a different link type based on the presence
or absence of a destination as bug.
> On Apr 3, 7:50 am, Ted Pavlic <[EMAIL PROTECTED]> wrote:
> > \href{file:/...}{see file}
The problem is that file: is also used for relative paths, something
like "file:abc.pdf', thus href doesn't change the stuff after file,
then probably the starting slashes ("///") cause the trouble.
The logic for remote links is based on the extension (".pdf").
Thus the extension can be changed:
\hypersetup{extension=notused}
However, if the file does not have an extension, then a remote
link with extension ".notused" will be created.
=====
--Ted
--
Ted Pavlic <[EMAIL PROTECTED]>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Skim-app-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/skim-app-users
