I don't think, that Yvonne has the problem that was mentioned in your linked thread.
Adding the "full document path to the weblinks" in the text" is a different one.
The URL begins with file:// and that indicates a file located in the local file system of her computer and not from a web server.
FWIW: She has CS6 8.1.0 installed. The problem mentioned in your linked thread was solved with CS8 8.0.2:
what is the actual URL you want to link to?
Does the file exist on the server?
I tried to find the PDF on the web and it seems that the file cannot be found.
But I found some references to a doc file type with the same name. With the same link path.
But that link also returned a 404 File Not Found message.
Hi Test Screen Name,
Would that missing http:// explain that behavior?
I don't think so.
After some testing I found the culprit:
I just tested www-only with InDesign CS6 8.1.0 on Mac OSX 10.10.5.
Used this as URL:
Result in the exported PDF:
Then I used the URL below where the slashes are encoded as %5C :
And the result was:
showing the path to my InDesign document on my harddisk.
So all instances of %5C should be replaced by /
Just did a test with CC 2017 with:
The URL was exported 1:1 to the PDF.
But this is also wrong because if I click the URL in the PDF the browser will start and is translating %5C to a backslash.
Replace all instances of %5C with a slash /
A full URL always has the form protocol:something . Examples (not real links)
The rules of URL allow a relative URL which is relative to the current base (such as the directory of the current file). For example if the current file is http://www.blah.com/zip/zap.htm then the URL graf/boggle.jpg means http://www.blah.com/zip/graf/boggle.jpg . If the current file is file://path/to/file.htm then the URL www.blah.com/zip/zap.htm (which has no protocol, no http://) means file://path/to/www.blah.com/zip/zap.htm
That is the rule. The makers of browsers years ago decided you could not type a relative URL so they assume http:// . But it stops there. In HTML files we must use full URLs or they are relative. Starting a URL with "www." Has no special meaning.
Other apps which look for URLs in an informal way might make assumptions but browsers won't. In a PDF an embedded link must follow full formal rules, while the "search text for URL" function makes all sorts of assumptions.
Hi Test Screen Name,
but why does InDesign add the InDesign document's path to the beginning of the URL only ( ? ) if a back slash is present in the URL and the URL is not beginning with http:// ?
I cannot provoke the file:/// addendum with an URL like that:
Wheras I can see the behavior in:
or in this equivalent of writing the same:
See an example InDesign document (IDML) and it's exported interactive PDF ( 2 pages ) here:
As I already wrote:
I think, the backslashes are wrong in the URL presented by Yvonne.
They should be replaced with forward slashes.
If of any reason backslashes are necessary, then the URL must be started with http://
My guess: InDesign assumes a slash or Www started URL is a full URL and adds the protocol. Backslashes are not legal in a URL as directory separators, so all bets are off if you do this, but it would look like a simple non-directory string and hence, correctly, a relative URL. Use correct URLs and the problem will vanish.
Here a reference on URL Encoding—nothing official, but nevertheless educating:
FWIW: I found an interesting discussion at Stack Overflow about backslashes with URLs from 2012:
This seems to be all academic if we discuss web links with InDesign documents, because it refers to
a. CSS and
b. localhost :
Using the userdir extensions of apache on linux will require to use user name in the URL in order to access public_html in the home directory.