[Table of Contents] [docx version]

WordprocessingML Reference Material - Table of Contents

lvlOverride (Numbering Level Definition Override)

This element specifies an optional override which shall be applied in place of zero or more levels from the abstract numbering definition for a given numbering definition instance. Each instance of this element is used to override the appearance and behavior of a given numbering level definition within the given abstract numbering definition.

[Example: Consider a numbering definition instance which inherits its information from the abstract numbering definition with abstractNumId of 4, but wishes to use a different set of properties for level 0 and level 1 of the numbering definition. The resulting WordprocessingML would look like:

<w:num w:numId="6">
<w:abstractNumId w:val="4" />
<w:lvlOverride w:ilvl="0">
<w:lvl w:ilvl="0">
<w:start w:val="4" />
<w:lvlText w:val="%1)" />
<w:lvlJc w:val="left" />
<w:pPr>
<w:ind w:left="360" w:hanging="360" />
</w:pPr>
</w:lvl>
</w:lvlOverride>

<w:lvlOverride w:ilvl="1">
<w:lvl w:ilvl="1">
<w:start w:val="5" />
<w:lvlText w:val="%Test)" />
<w:lvlJc w:val="left" />
<w:pPr>
<w:ind w:left="360" w:hanging="360" />
</w:pPr>
</w:lvl>
</w:lvlOverride>
</w:num>

end example]

[Note: The ability to set level overrides optimizes use of numbering in WordprocessingML as it prevents writing out redundant abstract numbering definitions if numbering sets only slightly differ.

Consider using WordprocessingML to create two numbered sets that only differ only in the appearance and style of the first numbering level. Both could use the same abstract numbering definition as long as each references a different numbering definition instance with one of the numbering definition instances leveraging a level override for the first numbering level. Below is WordprocessingML that illustrates this:

<w:num w:numId="5">
<w:abstractNumId w:val="4" />
</w:num>

<w:num w:numId="6">
<w:abstractNumId w:val="4" />
<w:lvlOverride w:ilvl="0">
<w:lvl w:ilvl="0">
<w:start w:val="4" />
<w:lvlText w:val="%1)" />
<w:lvlJc w:val="left" />
<w:pPr>
<w:ind w:left="360" w:hanging="360" />
</w:pPr>
</w:lvl>
</w:lvlOverride>
</w:num>

end note]

Parent Elements

num2.9.16)

 

Child Elements

Subclause

lvl (Numbering Level Override Definition)

§2.9.6

startOverride (Numbering Level Starting Value Override)

§2.9.28

 

Attributes

Description

ilvl (Numbering Level ID)

Specifies the numbering level of a given abstract numbering definition to be overridden.

 

If this number conflicts with the ilvl of the child lvl element, then the latter shall be ignored.

 

[Example: Consider a numbering definition instance which inherits its information from the abstract numbering definition with abstractNumId of 4, but wishes to use a different set of properties for level 0 of the numbering definition. The resulting WordprocessingML would look like:

 

<w:num w:numId="6">
<w:abstractNumId w:val="4" />
<w:lvlOverride w:ilvl="0">
<w:lvl w:ilvl="0">
<w:start w:val="4" />
<w:lvlText w:val="%1)" />
<w:lvlJc w:val="left" />
<w:pPr>
<w:ind w:left="360" />
</w:pPr>
</w:lvl>
</w:lvlOverride>
</w:num>

 

This level overrides level 0 of the abstract numbering definition's level properties with the specified set of numbering properties, replacing those in the abstract numbering definition. end example]

 

The possible values for this attribute are defined by the ST_DecimalNumber simple type2.18.16).

The following XML Schema fragment defines the contents of this element:

<complexType name="CT_NumLvl">

   <sequence>

   <element name="startOverride" type="CT_DecimalNumber" minOccurs="0"/>

   <element name="lvl" type="CT_Lvl" minOccurs="0" maxOccurs="1"/>

   </sequence>

   <attribute name="ilvl" type="ST_DecimalNumber" use="required"/>

</complexType>