#### 6.5.3 Assigning format-name prefixes to attribute values

To specify what to do with each value of each attribute to which AttrSectionName is assigned in [ElemSectionName] (see §6.5.2 Listing attributes whose values can affect output formats):

    [AttrSectionName]
    ; attribute value = prefix
    value1 = prefix1
    value2 = prefix2
    . . .

The attribute value can include wildcards. DITA2Go considers attribute values in the order they are listed in [AttrSectionName]; the first attribute value in the list that matches the value for a given instance of an element determines the prefix applied to the format name for that instance of that element. If the prefix assigned to a value is “*”, the attribute value itself becomes the prefix. If the prefix is blank, no prefix is applied for that value.

By default:

    [StepImportancePrefixes]
    required = ReqStep
    optional = OptStep

    [ImportancePrefixes]
    required = Req
    optional = Opt
    * = *

These default settings for required and optional values of the step element importance value are located in configuration template %omsyshome%\d2g\system\config\d2g_config.ini; see §39.1.3 Understanding how templates are chained together.

For example:

    [NoteTypePrefixes]
    note =
    warning = warn
    * = *

In this last example, a given <note> element would be mapped to a format name prefixed according to the value of the type element:

- If @type=note, DITA2Go would not apply a prefix to the format name.
- If @type=warning, the prefix warn would be applied to the format name; for example, warnNote.
- For any other value of the type attribute, DITA2Go would apply the attribute value itself as a prefix to the format name; for example, cautionNote.

Previous Topic: 6.5.2 Listing attributes whose values can affect output formats

Next Topic: 6.5.4 Assigning run-in headings to format-name prefixes

Parent Topic: 6.5 Mapping element attributes to output formats

Sibling Topics:

6.5.1 Listing elements whose attributes can affect output formats

6.5.2 Listing attributes whose values can affect output formats

6.5.4 Assigning run-in headings to format-name prefixes

6.5.5 Deciding which formats need a run-in heading property

6.5.6 Understanding the order of prefixes for multiple attributes

6.5.7 Understanding how prefixes modify output formats

6.5.8 Understanding default attribute-based prefixes and headings

Table of Contents • Index