EndnoteProperties Class
Section-Wide Endnote Properties.When the object is serialized out as xml, its qualified name is w:endnotePr.
Inheritance Hierarchy
System.Object
DocumentFormat.OpenXml.OpenXmlElement
DocumentFormat.OpenXml.OpenXmlCompositeElement
DocumentFormat.OpenXml.Wordprocessing.EndnoteProperties
Namespace: DocumentFormat.OpenXml.Wordprocessing
Assembly: DocumentFormat.OpenXml (in DocumentFormat.OpenXml.dll)
Syntax
声明
<ChildElementInfoAttribute(GetType(EndnotePosition))> _
<ChildElementInfoAttribute(GetType(NumberingRestart))> _
<ChildElementInfoAttribute(GetType(NumberingFormat))> _
<ChildElementInfoAttribute(GetType(NumberingStart))> _
Public Class EndnoteProperties _
Inherits OpenXmlCompositeElement
用法
Dim instance As EndnoteProperties
[ChildElementInfoAttribute(typeof(EndnotePosition))]
[ChildElementInfoAttribute(typeof(NumberingRestart))]
[ChildElementInfoAttribute(typeof(NumberingFormat))]
[ChildElementInfoAttribute(typeof(NumberingStart))]
public class EndnoteProperties : OpenXmlCompositeElement
Remarks
The following table lists the possible child types:
EndnotePosition <w:pos>
NumberingFormat <w:numFmt>
NumberingStart <w:numStart>
NumberingRestart <w:numRestart>
[ISO/IEC 29500-1 第 1 个版本]
17.11.5 endnotePr (Section-Wide Endnote Properties)
This element specifies the endnote properties for the current section. Each of these properties are an override of the document-wide endnote properties (§17.11.4) and are stored as a child element within the endnotePr element.
If this element is omitted for a given section, then that section shall use the endnote properties defined at the document-wide level.
[Example: Consider a document consisting of three sections, which has endnotes in the first section which use lowercase roman numerals, and endnotes in the third section which use the Chicago Manual of Style format. The WordprocessingML for each section would be specified as follows:
<w:sectPr>
<w:endnotePr>
<w:numFmt w:val="lowerRoman" />
</w:endnotePr>
</w:sectPr>
…
<w:sectPr>
…
</w:sectPr>
…
<w:sectPr>
…
</w:sectPr>
This assumes that the document-wide endnote settings are specified to use the Chicago Manual of Style format, as follows:
<w:settings>
<w:endnotePr>
<w:numFmt w:val="chicago" />
</w:endnotePr>
</w:settings>
The resulting document would override the endnote numbering format for the first section to lowerRoman, but would use the chicago endnote numbering format for section three (and would also use it for section two if that section had endnotes. end example]
Parent Elements |
|---|
sectPr (§17.6.17); sectPr (§17.6.18); sectPr (§17.6.19) |
Child Elements |
Subclause |
|---|---|
numFmt (Endnote Numbering Format) |
§17.11.17 |
numRestart (Footnote and Endnote Numbering Restart Location) |
§17.11.19 |
numStart (Footnote and Endnote Numbering Starting Value) |
§17.11.20 |
pos (Endnote Placement) |
§17.11.22 |
[Note: The W3C XML Schema definition of this element's content model (CT_EdnProps) is located in §A.1. end note]
© ISO/IEC29500: 2008. 以上摘要已经由 Microsoft（和/或其代理公司）从英语翻译为简体中文，ISO 对此翻译不承担任何责任。
Thread Safety
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.