You can use a configuration setting to override the default production method for contents or index or both; however, usually there is little reason to change the default method. You can also omit production of contents or index.
§16.4 Configuring contents entries for Help systems
§16.5 Configuring index entries for Help systems
§18.9.1 Choosing how to generate HTML Help contents and index
§19.6 Choosing navigation features for OmniHelp
§20.4.4 Locating JavaHelp or Oracle Help contents and index files
§21.4.1 Choosing contents and index methods for Eclipse Help
To specify whether contents, index, or both are to be generated for HTML-based Help:
[MSHtmlHelpOptions] or [JavaHelpOptions]
; ListType (for filter to create) = Both (default), Contents, or Index
For OmniHelp, see §19.6 Choosing navigation features for OmniHelp.
For Eclipse Help, see §21.4.1 Choosing contents and index methods for Eclipse Help.
To specify how contents and index are generated for HTML-based Help, depending on the value of ListType:
[MSHtmlHelpOptions] or [JavaHelpOptions] or [OmniHelpOptions] ; RefFileType = Full or None
RefFileType values have the following effects:
DITA2Go creates the final contents and index files directly, depending on the value of ListType. |
|
You might set RefFileType=None if you are repeatedly re-running a conversion to tune something in text, and you do not want the (small) overhead of writing out the contents and index information every time.
For HTML Help, you can specify one additional value for RefFileType. See §18.9.1 Choosing how to generate HTML Help contents and index.
For Eclipse Help, the default value of RefFileType is Full, regardless of whether you are converting a DITA bookmap or a single-file document. See §21.4.1 Choosing contents and index methods for Eclipse Help.