#### 42.2.8 Overriding fixed-key configuration settings

An override to a fixed-key configuration setting stays in effect until the end of the current DITA file, or until changed again by another configuration PI marker or configuration-variable assignment to the same setting. You can override some (but not all) settings in the configuration sections listed in Table 42-2. For example, to switch mid-file to adjusting inter-paragraph spacing in Word:

Configuration setting | RTFConfig override
    [Options]
    ParaSpace=Normal
    [Options]ParaSpace=Frame

Only persistent overrides work for fixed-key settings; temporary overrides do not work. Also, persistent overrides work only for fixed-key settings that do not have to apply to an entire DITA file. For instance, it would make no sense to try to change, in the middle of a file, the value of [Setup]ApplyTemplateFile; applying a conversion template is a one-time function that takes place before DITA2Go processes the file content. Other settings such as [WordOptions]SideHeads affect margins, and must apply to an entire file.

If you are producing HTML output, the only way to specify attributes for <body> is with a configuration override. For example, placing a PI marker at the beginning of the second topic:

    <?dthtm config="[Attributes]body= onload='prettyPrint()'" ?>

Then at the beginning of the fourth topic:

    <?dthtm config="[Attributes]body=" ?>

The effect would appear in HTML output for the second and third topics, but not the fourth. The PI marker affects the output file for the topic in which it is included (right after the root), and continues until set otherwise.

You can also override a fixed-key setting with a configuration-variable assignment in a regular DITA2Go macro instead of in a PI marker. See §37.9.3 Surrounding or replacing text with code or macros.

Table 42-2 Fixed-key configuration sections subject to overrides

Fixed-key configuration section * | HTML/XML | Word | WinHelp
* Some settings cannot be overridden in these sections; you might have to experiment.
    [Attributes]
| Yes |  |
    [Base]
| Yes |  |
    [Classes]
| Yes |  |
    [Defaults]
|  | Yes | Yes
    [Setup]
| Yes | Yes | Yes
    [GraphExport]
| Yes | Yes | Yes
    [Graphics]
| Yes | Yes | Yes
    [HelpBrowse]
|  |  | Yes
    [HelpContents]
|  |  | Yes
    [HelpOptions]
|  |  | Yes
    [HTMLOptions]
| Yes |  |
    [Inserts]
| Yes | Yes | Yes
    [JavaHelpOptions]
| Yes |  |
    [LocalTOC]
| Yes |  |
    [Macros]
| Yes |  |
    [MSHtmlHelpOptions]
| Yes |  |
    [NavigationMacros]
| Yes |  |
    [OmniHelpOptions]
| Yes |  |
    [Options]
| Yes | Yes | Yes
    [Tables]
| Yes |  |
    [Trails]
| Yes |  |
    [WordOptions]
|  | Yes |

Previous Topic: 42.2.7 Understanding fixed-key vs. variable-key settings

Next Topic: 42.2.9 Overriding variable-key configuration settings

Parent Topic: 42.2 Overriding settings with PI markers or macros

Sibling Topics:

42.2.1 Determining the extent of a configuration override

42.2.2 Overriding settings with configuration PI markers

42.2.3 Overriding settings with macros

42.2.4 Assigning values to configuration variables

42.2.5 Adding a new configuration setting on the fly

42.2.6 Assigning a macro or variable to a configuration variable

42.2.7 Understanding fixed-key vs. variable-key settings

42.2.9 Overriding variable-key configuration settings

42.2.10 Assigning HTML table and graphic groups with overrides