NumberingRestart class

Office 2013 and later

Footnote and Endnote Numbering Restart Location. When the object is serialized out as xml, its qualified name is w:numRestart.


Namespace:  DocumentFormat.OpenXml.Wordprocessing
Assembly:  DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)

public class NumberingRestart : OpenXmlLeafElement

[ISO/IEC 29500-1 1st Edition]

numRestart (Footnote and Endnote Numbering Restart Location)

This element specifies when all automatic numbering for the footnote or endnote reference marks shall be restarted. When restarted, the next automatically numbered footnote or endnote in the document (each footnote/endnote type is handled independently) shall restart to the specified numStart value (§17.11.20).

If this element is omitted, then automatic numbering shall not be restarted between each page or section (a vlaue of continuous).

[Example: Consider the following two page document where the numbering must be reset after each page to its starting value:

The footnote automatic restarting of the numbering is represented by the following WordprocessingML:

  <w:numRestart w:val="eachPage" />

end example]

Parent Elements

endnotePr (§17.11.4); endnotePr (§17.11.5); footnotePr (§17.11.12); footnotePr (§17.11.11)



val (Automatic Numbering Restart Value)

Specifies when the automatic numbering shall be restarted for the current set of footnotes or endnotes.

[Example: Consider a WordprocessingML document where the numbering for its endnotes must be restarted after each section must be restarted after each page. This setting is represented by the following WordprocessingML:

  <w:numRestart w:val="eachSect" />

The val attribute value of eachSect specifies that numbering shal be restarted after each section. end example]

The possible values for this attribute are defined by the ST_RestartNumber simple type (§17.18.74).

[Note: The W3C XML Schema definition of this element’s content model (CT_NumRestart) is located in §A.1. end note]

© ISO/IEC29500: 2008.

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.