4.3 Understanding where project settings come from

When you set up a new conversion project, the Mif2Go plug-in copies a new output-type-specific starting configuration file into your project directory. This file is populated with the settings you specify in the Set Up dialog (see §3.4 Choosing project set-up options). Mif2Go gets this file from a repository of configuration templates located in your Mif2Go distribution; see §30.1.1 Understanding how templates are organized. Each configuration template already contains values for basic settings specific to the output type for your project.

Default configuration values

Configuration values presented in the Set Up dialog (see §3.4 Choosing project set-up options) are not always the same as the internal default values for configuration settings:

Set-up value:	The value people usually want (or expect) for a new project for a given output type.
Internal default:	The value Mif2Go applies when the setting is missing entirely from the configuration files for your project.

Often, the internal default value produces the effect you would have experienced before a feature was added to Mif2Go; this is to maintain backward compatibility with existing configuration files. The effect is almost always equivalent to turning the feature “Off”. However, if the feature corrects a defect, the corresponding configuration value might default to “On”, with the setting provided to support users who had already put a workaround in place and wanted its functionality left alone.

Referenced configuration values

Your project configuration file includes references to:

• an optional document-specific configuration file created when you set up this or a previous project (see §3.5 Understanding how Mif2Go sets up a project)

• a required chain of configuration templates located in your Mif2Go distribution.

Your project incorporates by reference any settings those files contain, unless the settings are overridden in your project configuration file. If you intend to work with many conversion projects, you might want to inspect and possibly modify the local editions of some of these templates. See §30.1 Working with configuration templates.

---

> 4 Editing configuration files > 4.3 Understanding where project settings come from