Omni Systems, Inc.   Mif2Go User's Guide, Version 55


33 Overriding configuration settings > 33.2 Overriding settings with markers or macros > 33.2.6 Assigning a macro or variable to a configuration variable

33.2.6 Assigning a macro or variable to a configuration variable

When you assign a value to a configuration variable, and the value includes the name of a macro or a macro variable, whether or not that name should be enclosed in quotes depends on the context:

For example:

HTMConfig: [ParaStyleCodeAfter]=<$macafter>

HTML Macro: <$$[ParaStyleCodeAfter]="<$macafter>">

Angle brackets get processed in a macro

When you assign a value to a configuration variable in a macro, and the value contains any < or > characters (angle brackets), absent enclosing quotes Mif2Go processes each angle bracket as the start or end of a macro, instead of assigning the entire value as a string. That is, Mif2Go would try to figure out if maybe the string is something else first. When the value includes a > character that it is not in quotes, the macro ends prematurely. In this example:

<$$[ParaStyleCodeAfter]=<hr>>

Mif2Go would assign only <hr to the configuration variable, because the > after <hr would be taken as the end of the macro; and then Mif2Go would drop the real ending > into the current text.

Unquoted variables are evaluated in a macro

When you assign a macro variable to a configuration variable in a macro: