19.11 Setting up CSH for OmniHelp

To provide entry points for CSH (context-sensitive help) calls from an application to an OmniHelp system, you can embed symbolic IDs as TopicAlias PI markers in your DITA files, and list alias prefixes in the configuration file. OmniHelp does not use numeric values for CSH, so you do not need a map file. Actually opening an OmniHelp topic file from an application might require a redirect page or a visit to the Windows Registry.

In this section:

§19.11.1 Specifying alias prefixes for OmniHelp CSH calls

§19.11.2 Referencing OmniHelp topic IDs from an application

§19.11.3 Using redirect pages for OmniHelp CSH calls

§19.11.4 Executing browser commands for OmniHelp CSH calls

See also:

§16.10 Setting up Context Sensitive Help (CSH)

Previous Topic:  19.10.9 Highlighting search terms found in topics

Next Topic:  19.11.1 Specifying alias prefixes for OmniHelp CSH calls

Parent Topic:  19. Generating OmniHelp

Sibling Topics:

19.1 Understanding how OmniHelp works

19.2 Setting up OmniHelp viewer control files

19.3 Setting up an OmniHelp project

19.4 Using CSS with OmniHelp

19.5 Customizing OmniHelp display features

19.6 Choosing navigation features for OmniHelp

19.7 Configuring contents and index for OmniHelp

19.8 Providing related-topic links in OmniHelp

19.9 Jumping to secondary windows in OmniHelp

19.10 Configuring full-text search for OmniHelp

19.12 Merging OmniHelp projects

19.13 Assembling OmniHelp files for viewing

19.14 Deploying OmniHelp