### 10.11.3 Using redirect pages for OmniHelp CSH calls

If your application has trouble passing a topic-specific URL to the operating system (and then to the default browser), try creating a redirect page for each CSH target topic. A redirect page has content like this:

<!DOCTYPE html PUBLIC

"-//W3C//DTD HTML 4.01 Transitional//EN"

"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">

<html lang="en">

<head><title>Topic title</title>

<meta http-equiv="refresh"

content="1;url=file:///path/to/_myproj.htm#IDH_contextID">

</head>

<body></body></html>

In this example, IDH_contextID is the content of a newlink marker in the target topic. You need one little file like this for every CSH entry point. This is not necessarily a bad thing; redirect files allow you to use a constant set of names in the calling program, even if the names change in the Help. Notice the three forward slashes in the file reference:

url=file:///path/to/_myproj.htm#IDH_contextID

For example:

url=file:///G:/Omnisys/UG/OH/Done/ugmif2go.htm#tablist

If you do not know the absolute path on the system where OmniHelp will be deployed, but you are able to place redirect files in the same directory as the OmniHelp output files (and invoke OmniHelp from that directory), you could use the following for the url value:

url=file:_myproj.htm#IDH_contextID

Relative paths would work like this:

url=file:./to/_myproj.htm#IDH_contextID

You could use a file name (file.htm) after the hash mark, with the same result; see §10.11.2 Referencing OmniHelp topic IDs from an application.

| 10.11.2 Referencing OmniHelp topic IDs from an application |  | 10.11.4 Executing browser commands for OmniHelp CSH calls |