Using RH 7 HTML our corp wants to have help files able to function as "standalone" files on local PC's without network or server for business continuity. Presently most files have 150 or less topics and are published to a server. External files are in sub folders within the folder where the published file is located. Links to external attachments (.doc, .xls, .pdf, etc.) are absolute links and need to be changed to relative. An example existing link would be: HTTP://server.com/help/attachments/fname/sample.doc. Help is the foler where tje published file is located and Attachments is the folder where the external files to be linked are located. When link is changed to: ../Attachments/ some links work and some don't. I discovered that some links require: ../../Attachments/ to function correctly. It appears that links that are not in the root path of the project manager require additional ../'s. I am trying to find out how RH7 reads the links and how to back out of a directory and when. Any help is appreciated. Thanks.
You say that the files are stand alone, but that the files will be in a subfolder of your output. Does this mean that you can add the files as baggage files to your project, or is that impossible.
About the ../ and ../../, it simply means take parent directory and take parent directory of parent directory. When you have a file in MyFile/Doc/Important/ and the topic is in MyFile/Robo, the path will be ../Doc/Important. When the topic is in the directory MyFile/Robo/Project, the path will be ../../Doc/Important. When you add the files as baggage files, you simply add a hyperlink to the file and let Robo sort out the hyperlink. If you can't attach the files as baggage files, you'll have to manually add all relative links. I can't think of an easy way to automate this. Altough a developer might be able to create a script for you.
The easiest, and most efficient, way is to replicate the folder environment onto your local machine (all folders and files exactly as they will appear in the destination area), and let RH do the heavy lifting.
Therefore, to link to anything outside the current RH project, the method is:
(You'll get an info message about linking to an external file...when you initially create the link and every time you open it...just ignore it.)
We use this method in a 42-project merged project, and it's never failed us. The only time that your links will break is when you copy or move a file to another location. Since the relative paths are no longer valid, RH will automatically assign the links to within the current topic; you'll need to re-assign the link manually.