#### 39.3.1 Understanding document-specific configuration files

When you set up a conversion project, DITA2Go creates a document-specific configuration file for you, and places a reference to that file in your project configuration file. To establish a document-specific configuration, DITA2Go looks in this file:

    %omsyshome%\d2g\local\config\local_d2g_config.ini

or, if the required settings are not there, in this file:

    %omsyshome%\d2g\system\config\d2g_config.ini

for the following settings:

    [Setup]
    . . .
    ; used when creating document-specific configuration files
    LocalConfigPath = ..\_config\
    WinHelpDocName = winhelp_doc.ini
    WordDocName = word_doc.ini
    HTMLDocName = html_doc.ini

These are default values; see §1.3.7 Establish system-wide configuration settings. If the directory named by LocalConfigPath is not already present, DITA2Go creates this directory.

If not already present in the directory named by LocalConfigPath, DITA2Go creates a configuration file there with one of the following names (or other names if you have changed the defaults), depending on the output type of the project:

html_doc.ini | for HTML, HTML-based Help, or XML projects
word_doc.ini | for Word or WordPerfect projects
winhelp_doc.ini | for WinHelp projects

This document-specific configuration file is intended for settings that are likely to apply only to the current DITA document, and that will be the same for most outputs. Initially this file includes settings in the following sections:

html_doc.ini | [HTMLStyles], [HelpContentsLevels]
word_doc.ini | [WordSectionFiles], [WordCntStyles]
winhelp_doc.ini | [HelpStyles], [HelpCntStyles], [BrowseStart]

Also included is a comment to show that this file is referenced from the project configuration file. For example:

    ; Document-specific configuration for HTML outputs
    ; Referenced by _m2htm.ini

If a document-specific configuration file for the current output type is already present in the directory named by LocalConfigPath, DITA2Go does not overwrite that file, nor add a comment. For additional conversions from the same document you might want to add “referenced by” comments yourself, so you can keep track of which of your project configuration files reference the document-specific configuration file.

Previous Topic: 39.3 Including document-specific configuration files

Next Topic: 39.3.2 Referencing a document-specific configuration file

Parent Topic: 39.3 Including document-specific configuration files

Sibling Topics:

39.3.2 Referencing a document-specific configuration file

39.3.3 Deciding where to keep document-specific configuration files