#### 9.1.3 Processing complex otherprops settings

If your DITA files contain complex otherprops values, you might want DITA2Go to include these values in output. The default is to ignore complex otherprops values:

[ConditionOptions]
; ComplexOtherprops = No (default, ignore complex settings because
; they were deprecated in DITA 1.1), or Yes
ComplexOtherprops = Yes

When ComplexOtherprops=Yes, DITA2Go processes any complex otherprops values as though the group name is a distinct attribute name. For example:

otherprops="proglang(java cpp) commentformat(javadoc html)"

DITA2Go treats this example as exactly equivalent to:

proglang="java cpp" commentformat="javadoc html"

and processes it as:

proglang="java cpp"

and:

commentformat="javadoc html"

You can also have simple otherprops values:

otherprops="whatever"

But you cannot mix both in the same attribute:

INVALID: otherprops="proglang(java cpp) whatever"

For use in ditaval files, otherprops is always simple:

<prop att="otherprops" val="whatever" action="exclude">

For complex otherprops in ditaval files, you would use:

<prop att="proglang" val="cpp" action="exclude">
<prop att="commentformat" val="html" action="exclude">

without mentioning they were packaged in otherprops.

Complex otherprops values were “deprecated in favor of attribute specialization” in DITA version 1.1, and are still listed that way in version 1.2; therefore the default value of ComplexOtherprops is No.

Previous Topic: 9.1.2 Including wildcards in ditaval statements

Next Topic: 9.2 Defining conditional actions

Parent Topic: 9.1 Extracting conditions from ditaval files

Sibling Topics:

9.1.1 Specifying a single ditaval file

9.1.2 Including wildcards in ditaval statements

Table of Contents • Index