#### 19.5.7 Modifying the OmniHelp template

Your DITA2Go distribution directory contains a copy of file ohtpl.ini, which provides default text values and macros for variable presentation features. You do not need this file unless you plan to alter features for which no configuration settings are provided; see §19.1 Understanding how OmniHelp works.

You can copy ohtpl.ini to your project directory. If you are brave, you can specify a path to ohtpl.ini instead of placing it in the project directory; you can even give this template file a different name:

    [OmniHelpOptions]
    ; ProjectTemplate = path to template for generating
    ;  OHProj and myproj_ohx.js files, with sections containing text
    ;  and macro references for variable items
    ProjectTemplate=ohtpl.ini

You need ProjectTemplate only when settings are not sufficient; for example, if you undertake a drastic customization of OmniHelp, and add new variables. If you use the same template for all projects, it would be best to keep the template in:

%OMSYSHOME%\common\local\omnihelp\ohvd2g

Otherwise, keep the template in the project directory.

You can edit a copy of ohtpl.ini to experiment with various versions of this template; however, in general you should rarely need to use or modify ohtpl.ini.

Previous Topic: 19.5.6 Modifying OmniHelp CSS classes

Next Topic: 19.6 Choosing navigation features for OmniHelp

Parent Topic: 19.5 Customizing OmniHelp display features

Sibling Topics:

19.5.1 Configuring OmniHelp window usage and frameset dimensions

19.5.2 Altering OmniHelp top navigation frame content

19.5.3 Modifying OmniHelp navigation aids

19.5.4 Choosing whether to use cookies for OmniHelp

19.5.5 Localizing the OmniHelp interface

19.5.6 Modifying OmniHelp CSS classes

Table of Contents • Index