GutterAtTop class

Office 2013 and later

Position Gutter At Top of Page. When the object is serialized out as xml, its qualified name is w:gutterAtTop.

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

public class GutterAtTop : OnOffType

[ISO/IEC 29500-1 1st Edition]

gutterAtTop (Position Gutter At Top of Page)

This element specifies that a given WordprocessingML document’s gutter shall be positioned at the top of the document’s pages when the document is displayed. A gutter is the white space formed by the inner margins of two pages facing one another; such as the white space between the text on pages of a book when the book is opened.

If this element is omitted, then the gutter shall not be positioned at the top of the page. If the mirrorMargins (§17.15.1.57), bookFoldPrinting (§17.15.1.11), bookFoldRevPrinting (§17.15.1.13), or printTwoOnOne (§17.15.1.64) elements are used within a given document, the gutterAtTop element shall not be used. Rather, the gutter shall be positioned automatically as necessary to enable the printing and page layout capabilities of these settings.

[Example: Consider a one page WordprocessingML document with a 1,440 twentieths of a point (one inch) top margin and gutter, and a 720 twentieths of a point (one half of an inch) header. Consider also, that the gutter must exist at the top of the document's pages. This requirement is specified using the following WordprocessingML in the section properties:

<w:pgMar w:top="1440" … w:header="720" … w:gutter="1440" />

And the following WordprocessingML in the document settings:

<w:gutterAtTop w:val="true" />

The resulting document's pages would have the gutter positioned as follows:

The gutterAtTop element's val attribute is equal to true, specifying that the gutter must appear at the top of each page. end example]

Parent Elements

settings (§17.15.1.78)

This element’s content model is defined by the common boolean property definition in §17.17.4.

© 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.
Show: