Hi all,
My company puts together a CD that we give away to customers and on it is an index/table of contents pdf file that has hyperlinks to different articles on their own pdf files. For some reason that we cannot understand, the links work just fine when clicked on in Firefox or Chrome. When clicked on in Internet Explorer, though, we will get a "file not found" error returned.
If we change a setting to have the pdfs not display in the browser, they'll open as a separate window and work fine. However, we'd really like to figure out what's going on in Internet Explorer so we don't have to make our customers jump through hoops.
(If it helps, we're using IE 8 and Acrobat 7.)
Any help with this is appreciated!
Just nattering here; but, rather than reliance upon browsers, why not use Adobe Reader?
Unlike browsers, Adobe Reader exists soley to render PDFs.
(It helps if the PDF producer is ISO 32000-1:2008 compliant - not all are).
These days it is rare that a purchased computer does not have Adobe Reader installed.
For those few that do not, you can place the Reader install files on the CD/DVD.
Adobe does require a form to be submitted on which you identify who you are and what you want to do.
Adobe will email you once a year to ask if you want the renew your distribution of Reader.
No cost to you other than the a few minutes with the form and the annual email reply.
Each browser has its own behavior oddities. For a given browser, different releases are, well different.
Browser behavior is anything but a "given"; and that is for HTML.
Provide an autorun file to open a "start" or "welcome" PDF that is on the OSM's root.
One or more links from it take the user to the content topic(s).
I prefer to provide lower tier "round about" PDFs for end-user passage to and from content topics and sub-topics.
Build topic collections in a nested directory layout. Have all under an "umbrella" directory.
After build & QC, burn all under the "umbrella" directory to the OSM.
This preserves all PDF's relative location and thus the integrity of all links.
Provide tiered Catalog indices within the collections. Associated these with appropriate
"round about" PDFs. These provides end-users advanced Search of topics/sub-topics
throughout the OSM's content.
In all, the end-user is provided with an optimal usage experience and functionality.
Browsers are fine when plucking something like a PDF from the web server's branches.
OSMs with PDF is something else, eh?
Be well...
Be well...