33.2.4 Assigning values to configuration variables
A configuration-variable assignment can be any of the following, depending on the context and the extent of the configuration override:
where the components of the assignment are as follows: :
Name of the configuration-file section where the setting belongs |
|
Keyword whose value you want to change, or the format or object whose properties you want to change; omit for temporary overrides |
|
When you assign a value to a configuration variable, observe the following:
• Spaces around [Section] are optional.
• Section is not case sensitive.
• In a macro, [Section] must be prefixed with $$; in a *Config marker, the prefix is optional.
• Include Key only for a persistent override; see §33.2.1 Determining the extent of a configuration override.
• Key is case sensitive for variable-key settings.
• Key must be enclosed in quotes if Key contains any spaces or non-alphanumeric characters.
• If Key requires an on/off value, Mif2Go recognizes “1” (numeral one), “Yes”, and “True” as on, and “0” (zero), “No”, and “False” as off.
• In a macro, if Value is a text string, Value must be enclosed in quotes. In a *Config marker, quotes around text values are optional; if present, Mif2Go removes them. Therefore, if the value to be assigned actually contains quotes at both ends, you must double them for assignment in a *Config marker. For example:
HTMConfig: [StyleTextStore]=""a quoted phrase""
• If Value includes the name of a macro or macro variable, whether that name should be enclosed in quotes depends on the context; see §33.2.6 Assigning a macro or variable to a configuration variable.
> 33 Overriding configuration settings > 33.2 Overriding settings with markers or macros > 33.2.4 Assigning values to configuration variables