DocumentID: ECMA-376/Part4/2.15.1
Title: ECMA-376, Part4: 2.15.1 Document Settings
Extracted-From: ECMA-376 Office Open XML File Formats, 1st Edition / December 2006
Warning: Coverted to HTML format by a script known to have bugs

• Next: 2.15.1 Document Settings
• Up: 2.15 Settings
• Table of contents: Table of contents
• Previous: 2.15 Settings

2.15.1 Document Settings

The first group of settings stored in WordprocessingML is document settings. These settings specify all document-level properties which affect the handling of the current document.

[Example: Consider the following WordprocessingML fragment for the document settings in a WordprocessingML document:

<w:settings>
  <w:defaultTabStop w:val="720" />
  <w:characterSpacingControl w:val="dontCompress" />
</w:settings>

The settings element contains all of the document settings for this document. In this case, the two settings applied are automatic tab stop increments of 0.5" using the defaultTabStop element (§2.15.1.24), and no character level whitespace compression using the characterSpacingControl element (§2.15.1.18). end example]

2.15.1.1 activeWritingStyle (Grammar Checking Settings)

This element specifies information about the parameters of the grammar checking which was performed on the contents of the current WordprocessingML document. [Note: This information may be used as desired by applications; for example, to determine if the current grammar checking state, specified by the proofState element (§2.15.1.65) is sufficient. end note]

[Example: Consider the following WordprocessingML fragment from the document settings:

<w:activeWritingStyle w:lang="en-CA" w:vendorID="64" w:dllVersion="131078" w:nlCheck="1" w:optionSet="0" /> 

The activeWritingStyle element's lang attribute specifies that the English (Canada) language setting for grammatical and stylistic checks shall be applied; the vendorID attribute specifies information about the vendor associated with the DLL used to perform the grammatical and stylistic checks; the dllVersion attribute specifies the version of this DLL; the nlCheck attribute specifies if natural language checks were performed or not; and the optionSet element specifies that the hosting application should allow its grammar engine to check both the grammar and style of the given WordprocessingML document, if that functionality is available. end example]

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

<complexType name="CT_WritingStyle">

<attribute name="lang" type="ST_Lang" use="required"/>

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

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

<attribute name="nlCheck" type="ST_OnOff" use="optional"/>

<attribute name="checkStyle" type="ST_OnOff" use="required"/>

<attribute name="appName" type="ST_String" use="required"/>

</complexType>

2.15.1.2 alignBordersAndEdges (Align Paragraph and Table Borders with Page Border)

This element specifies that paragraph borders specified using the pBdr element (§2.3.1.24) and table borders using the tblBorders element (§2.4.37) shall be adjusted to align with extents of the page border defined using the pgBorders element (§2.6.10) if the spacing between these borders is less than or equal to 10.5 points (one character width) or less from the page border. The presence of this setting shall ensure there are no gaps of one character width or less between adjoining page and paragraph/table borders, as borders which are perfectly aligning shall not be displayed in favor of the intervening page border.

If this element is omitted, then borders shall not be automatically adjusted to prevent gaps of less than one character width. If the page border is not measured from the text extents using a value of text in the offsetFrom attribute on the pgBorders element, then it may be ignored.

[Example: Consider the following WordprocessingML fragment from the document settings:

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

The alignBordersAndEdges element has a value of true specifying that borders shall be adjusted to prevent gaps of less than one character width. If a document has a page border specified to appear 4 points from the text extents, and within that page a paragraph border specified to appear one point from the text extents, that would normally appear like this:

If this element is present, then those gaps (which are all of three points in width) shall be adjusted to ensure that the borders align exactly and the paragraph border is suppressed:

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.3 alwaysMergeEmptyNamespace (Do Not Mark Custom XML Elements With No Namespace As Invalid)

This element specifies whether custom XML markup specified via the customXml element which has no associated namespace shall be treated as an error and moved into a special error namespace (for the purposes of validation) when the document is opened. If this element is turned on, when an application determines that the current XML markup is in the empty namespace, those elements shall not automatically be moved into an error namespace.

If this element is not present in a WordprocessingML document than custom XML markup which has no associated namespace shall be treated as an error and moved into a special error namespace when the document is opened.

[Example: Consider a WordprocessingML document which should not automatically flag empty namespace XML as invalid. This requirement would be specified using the following WordprocessingML:

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

The alwaysMergeEmptyNamespace element's val attribute has a value of true specifying that custom XML markup in the empty namespace shall never be treated as an error. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.4 alwaysShowPlaceholderText (Use Custom XML Element Names as Default Placeholder Text)

This element specifies that each custom XML element specified using the customXml element within this document shall always show some form of in-document placeholder text presentation when it contains no run content. If the placeholder element (§2.5.2.24) is present in the custom XML element's properties, then this is the placeholder text displayed and this effect has no effect. If the placeholder element is omitted, then the application shall use the name of the element to generate default placeholder text in its place.

If this element is omitted, then custom XML markup which does not contain a placeholder element within its properties shall not display any placeholder text.

[Example: Consider the following WordprocessingML fragment from the document settings:

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

The alwaysShowPlaceholderText element has a value of true, which specifies that placeholder text shall be generated using the element's name if no placeholder text is present. If two custom XML elements are defined as follows:

<w:customXml w:name="spec" ... >
  <w:customXmlPr>
    <w:placeholder w:val="Type the name of the specification." />
  </w:customXmlPr>
</w:customXml>
...
<w:customXml w:name="spec" ... >
</w:customXml>

The first custom XML element has placeholder text, and the second doesn't, so if this element is omitted, these two elements might be displayed as follows:

Notice that the second custom XML element has no placeholder text, and therefore is not displayed. However, when this element is present, then the application should generate default placeholder text in its place:

The application generated default placeholder text from the element name, resulting in a value of [spec] in the document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.5 attachedSchema (Attached Custom XML Schema)

This element specifies that the custom XML schema whose target namespace matches the value specified in the val attribute should be associated with this document when it is loaded, if such a schema is available to the hosting application. Applications may also load and utilize any additional schemas as well as those explicitly mentioned here. [Note: These custom XML schemas may then be used to validate the structure of the custom XML markup in the document, etc. end note]

If no elements of this type are present, then no custom XML schemas have been explicitly associated with the contents of this document.

[Example: Consider the following WordprocessingML fragment from the document settings:

<w:attachedSchema w:val="http://www.example.com/schema1" />

<w:attachedSchema w:val="http://www.example.com/schema2" />

The attachedSchema elements specify that two custom XML schemas with namespaces of http://www.example.com/schema1 and http://www.example.com/schema2 should be associated with the custom XML markup in the current document. end example]

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

<complexType name="CT_String">

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.6 attachedTemplate (Attached Document Template)

This element specifies the location of a document template which shall be attached to the current WordprocessingML document if it is accessible and of a format supported by an application. Specifically, this element's val attribute shall contain the file path of the associated document template.

If this element is omitted, then the document shall not have an attached document template, and applications should use their default template in its place.

[Example: Consider a WordprocessingML document which is attached to a WordprocessingML template located on the local C drive within a file whose name is c:\template.dotx. This association is specified using the following WordprocessingML:

<w:attachedTemplate w:val="c:\template.dotx" />

The attachedTemplate element contains the path to the associated template. end example]

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

<complexType name="CT_Rel">

<attribute ref="r:id" use="required"/>

</complexType>

2.15.1.7 autoCaption (Single Automatic Captioning Setting)

This element specifies what type(s) of objects shall automatically labeled with captions (§2.15.1.17), and with which captions the specified objects shall be labeled as defined in the caption element (§2.15.1.16).

[Example: Consider the diagram below illustrating a two page WordprocessingML document that has leveraged WordprocessingML to automatically label WordprocessingML tables with a specified caption when tables are inserted into the given document.

This type of automatic captioning is specified using the following WordprocessingML fragment:

<w:captions>
  <w:caption w:name="Table" w:pos="below" w:chapNum="On" w:heading="2" w:numFmt="upperCase" w:sep="8212" />
  <w:autoCaptions>
    <w:autoCaption w:name="wfwTable" w:caption="Table" />
  </w:autoCaptions>
</w:captions>

Here, the autoCaption element specifies through the name attribute being set equal to wfwTable that tables will automatically be labeled with the caption specified in the caption element whose name attribute is equal to Table, as the caption element's caption attribute has a value of Table. end example]

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

<complexType name="CT_AutoCaption">

<attribute name="name" type="ST_String" use="required"/>

<attribute name="caption" type="ST_String" use="required"/>

</complexType>

2.15.1.8 autoCaptions (Automatic Captioning Settings)

This element specifies that one or more types of objects, when inserted into a WordprocessingML document, will automatically be labeled with a specific caption defined using the caption element (§2.15.1.16).

[Example: Consider the following example illustrating a two page WordprocessingML document that has leveraged WordprocessingML to automatically label WordprocessingML tables with a specified caption.

This type of automatic captioning is specified using the following WordprocessingML fragment:

<w:captions>
  <w:caption w:name="Table" w:pos="below" w:chapNum="On" w:heading="2" w:numFmt="upperCase" w:sep="8212" />
  <w:autoCaptions>
    <w:autoCaption w:name="wfwTable" w:caption="Table" />
  </w:autoCaptions>
</w:captions>

The autoCaptions element specifies set of objects that when inserted into a WordprocessingML document will automatically be labeled with a given caption. end example]

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

<complexType name="CT_AutoCaptions">

<sequence>

<element name="autoCaption" type="CT_AutoCaption" minOccurs="1" maxOccurs="unbounded"/>

</sequence>

</complexType>

2.15.1.9 autoFormatOverride (Allow Automatic Formatting to Override Formatting Protection Settings)

This element specifies whether formatting automatically applied by an application (i.e. not explicitly applied by a use or an application) shall be allowed to override formatting protection enabled via the formatting attribute on the documentProtection element (§2.15.1.9) when those formatting operations would add formatting which has been explicitly disabled. [Example: Automatically adding superscript to the st in the string 1st. end example]

If this element is omitted, then no automatic formatting rule(s) shall be allowed to override the formatting restrictions enabled for the document.

[Example Consider a WordprocessingML document which has been protected such that a user shall not be able to directly format text within the document. Consider also that the hosting application has been constructed such that if a user enters a ampersand, then one or more alphabetical characters, then another ampersand, that the alphabetical characters are to take on italicized formatting.

If the autoFormatOverride element is omitted or set to false and document protection is enabled, the aforementioned series of events will not cause the English alphabetical characters to be italicized as the document protection preventing formatting of the document in question will supersede the formatting to take place after these events. If this operation should not be prevented when active formatting restrictions are used, this would be specified using the following WordprocessingML:

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

The autoFormatOverride element's val attribute is equal to on specifying that the automatic formatting behavior shall be applied regardless of the formatting restrictions in place. End Example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.10 autoHyphenation (Automatically Hyphenate Document Contents When Displayed)

This element specifies whether the content of a given WordprocessingML document should automatically be hyphenated by the hosting application before it is displayed, if the application supports this functionality.

If this element is omitted, then hyphenation shall not automatically be performed by application displaying this document.

[Example: Consider the images below illustrating a paragraph of text in a WordprocessingML document:

If the content in this document shall automatically be hyphenated when it is displayed, that requirement would be specified using the following WordprocessingML in the document settings:

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

The resulting output might look like the following (depending on the application's hyphenation algorithm and the hyphenation zone setting (§2.15.1.53):

The autoHypehenation element has its val attribute equal to true, the document is automatically hyphenated and the word sample, beginning at the end of the second line, is hyphenated automatically and thus carried over onto the third line. Conversely, when the autoHypehnation element has its val attribute equal to off, the entire word sample is carried over to the third line as it was not hyphenated automatically and could not fit onto the second line. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.11 bookFoldPrinting (Book Fold Printing)

This element specifies if the contents of a given WordprocessingML document should be printed as signatures. Signatures are printed sheets, which depict several pages of a document that are folded and bound with other signatures to form a booklet, a set of which can be bound together to form a book like publication. Specifically, this element specifies that each page in a given WordprocessingML document should be oriented in a landscape fashion, divided in half vertically with two left margins emanating from the bisector of the page, and two right margins instantiated at the left and right side of each page.

This element is used in conjunction with the bookFoldPrintingSheets element (§2.15.1.12) to enable a WordprocessingML document to be printed such that the series of signatures printed may be folded and bound to create a booklet.

This element has no impact on the settings of printer leveraged by the hosting application. In other words, if the printer leveraged by the hosting application has been configured to print on one side of a page, including the WordprocessingML for this element has no effect.

If this element is omitted, then pages shall not be printed as signatures. If the bookFoldRevPrinting element (§2.15.1.13) is also specified, then this element shall be ignored.

[Example: Consider a four page WordprocessingML document with a 2,160 twentieths of a point (one and a half inch) left margin, and 1,440 twentieths of a point (one inch) bottom, right, and top margins using the pgMar element (§2.6.11) surrounding the text extents of the page (represented by the gray shaded area in diagrams below). These page margins are specified using the following WordprocessingML:

<w:pgMar w:top="1440" w:right="1440" w:bottom="1440" w:left="2160" />

The necessary WordprocessingML and consequential effect of setting the bookFoldPrinting element's val attribute to true versus false and the bookFoldPrintingSheets element's val attribute to 4, is depicted graphically below--diagrams not drawn to scale:

Assuming the page was already oriented in a landscape fashion, setting the bookFoldPrinting element's val attribute to true divided the page in half vertically, with two left margins emanating from the bisector of the page, and right margins instantiated at the left and right side of each page, enabling two signatures to be printed.

In addition, this element is used in conjunction with the bookFoldPrintingSheets element to enable the given WordprocessingML document to be printed such that the series of signatures printed may be folded and bound to create a booklet. Specifically, the signatures may be placed back to back, with top the bottom of each sheet aligned, and folded such that a booklet is created. end example]

[Note: This element could also be leveraged by the hosting application to notify the application to display two pages per sheets within its user interface to allow for a WYSIWYG user experience. end note]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.12 bookFoldPrintingSheets (Number of Pages Per Booklet)

This element shall be used in conjunction with the bookFoldPrinting (§2.15.1.11) and bookFoldRevPrinting (§2.15.1.13) elements to specify the number of pages to be included in each booklet when printing a series of signatures. Signatures are printed sheets, which depict several pages of a document that are to be folded and bound with other signatures to form a booklet. Booklets can be bound together to form a book like publication.

If this element is omitted, then its default behavior shall be to print the contents of the content on a single sheet. A sheet is a single piece of paper which is folded and cut to produce a book.

[Example: Consider a four page WordprocessingML document will be printed as a set of two signatures to be compiled into a single booklet. This setting would be specified using the following WordprocessingML fragment in the document settings part:

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

<w:bookFoldPrintingSheets w:val="4" />

The bookFoldPrintingSheets element's val attribute specifies that 4 pages shall be included in each booklet. Since each signature contains two pages and are printed such that the signatures may be placed back to back, with top the bottom of each sheet aligned, and folded such that the booklet is created, a booklet containing four pages distributed over two signatures may be created.

This setting is depicted visually using the illustration below (gray shading represents a page):

end example]

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

<complexType name="CT_DecimalNumber">

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

</complexType>

2.15.1.13 bookFoldRevPrinting (Reverse Book Fold Printing)

This element specifies if pages of a given WordprocessingML document are to be printed as signatures in reverse order. Signatures are printed sheets, which depict several pages of a document that are folded and bound with other signatures to form a booklet, a set of which can be bound together to form a book like publication. Specifically, this element specifies that each page in a given WordprocessingML document should be oriented in a landscape fashion and divided in half vertically, with two left margins emanating from the bisector of the page, and right margins instantiated at the left and right side of each page.

In addition, this element is used in conjunction with the bookFoldPrintingSheets element (§2.15.1.12) to enable given WordprocessingML document to be printed such that the series of signatures printed may be folded and bound to create a booklet.

This element has no impact on the settings of printer leveraged by the hosting application. In other words, if the printer leveraged by the hosting application has been configured to print on one side of a page, including the WordprocessingML for this element has no effect.

If this element is omitted, then pages shall not be printed as reverse book fold signatures. If the bookFoldPrinting element (§2.15.1.11) is also specified, then that element shall be ignored, and this element shall be used instead.

[Example: Consider a four page WordprocessingML document with a 2,160 twentieths of a point (one and a half inch) left margin, and 1,440 twentieths of a point (one inch) bottom, right, and top margins using the pgMar element (§2.6.11) surrounding the text extents of the page (represented by the gray shaded area in diagrams below). These page margins are specified using the following WordprocessingML:

<w:pgMar w:top="1440" w:right="1440" w:bottom="1440" w:left="2160" />

The necessary WordprocessingML and consequential effect of setting the bookFoldRevPrinting element's val attribute to true versus false and the bookFoldPrintingSheets element's val attribute to 4, is depicted graphically below--diagrams not drawn to scale:

<w: bookFoldRevPrinting w:val="false"/>	<w: bookFoldRevPrinting w:val="true"/> <w: bookFoldPrintingSheets w:val="4"/>
First Printed Sheet	First Printed Signature
(missing picture pict-2.15.1.13-7)
Second Printed Sheet	Second Printed Signature
(missing picture pict-2.15.1.13-8)

Assuming the page was already oriented in a landscape fashion, setting the bookFoldRevPrinting element's val attribute to true divided the page in half vertically, with two left margins emanating from the bisector of the page, and right margins instantiated at the left and right side of each page, enabling two signatures to be printed.

In addition, this element is used in conjunction with the bookFoldPrintingSheets element to enable the given WordprocessingML document to be printed such that the series of signatures printed may be folded and bound to create a booklet. Specifically, the signatures may be placed back to back, with top the bottom of each sheet aligned, and folded such that a booklet is created. end example]

[Note: This element could also be leveraged by the hosting application to notify the application to display two pages per sheets within its user interface to allow for a WYSIWYG user experience. end note]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.14 bordersDoNotSurroundFooter (Page Border Excludes Footer)

This element specifies that a given WordprocessingML document's page border specified using the pgBorders element (§2.6.10) should not surround contents of the footer.

If this element is omitted, then the page border shall not exclude the footer on the page. As well, this element shall be ignored if the pgBorders element has an offsetFrom attribute which is not equal to text.

[Note: If the pgBorders element has a offsetFrom attribute equal to page, the bordersDontSurroundFooter element shall be ignored as specifying the pgBorders element with a offsetFrom attribute equal to page is to specify that the positioning of borders within the document shall be calculated relative to the edge of the page and therefore irrespective of document content in the footer. end note]

[Example: Consider the following page in a WordprocessingML document:

If this WordprocessingML document is modified to leverage the behavior enabled by this element, this setting would be specified using the following WordprocessingML fragment in the document settings:

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

The bordersDontSurroundFooter element's val attribute is equal to true specifying that the page border shall not surround the text extents of the footer, as follows:

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.15 bordersDoNotSurroundHeader (Page Border Excludes Header)

This element specifies that a given WordprocessingML document's page border specified using the pgBorders element (§2.6.10) should not surround contents of the header.

If this element is omitted, then the page border shall not exclude the header on the page. As well, this element shall be ignored if the pgBorders element has a offsetFrom attribute which is not equal to text.

[Note: If the pgBorders element has a offsetFrom attribute equal to page, the bordersDontSurroundHeader element shall be ignored as specifying the pgBorders element with a offsetFrom attribute equal to page is to specify that the positioning of borders within the document shall be calculated relative to the edge of the page and therefore irrespective of document content in the header. end note]

[Example: Consider the following page in a WordprocessingML document:

If this WordprocessingML document is modified to leverage the behavior enabled by this element, this setting would be specified using the following WordprocessingML fragment in the document settings:

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

The bordersDontSurroundHeader element's val attribute is equal to true specifying that the page border shall not surround the text extents of the header, as follows:

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.16 caption (Single Caption Type Definition)

This element specifies the contents and positioning for captions which may be used to automatically label objects in a WordprocessingML document. A caption is a string that labels an object included in a WordprocessingML document, and typically consists of a string plus a field which numbers this item within a collection of similar objects.

[Example: Consider the diagram below illustrating a WordprocessingML document containing a table that has been labeled with a caption:

In this diagram, the table contained in the WordprocessingML document has been labeled by inserting a caption below the table consisting of the string Table followed by a field whose result is a decimal number. The settings which automatically produced this form of caption are specified using the following WordprocessingML fragment:

<w:captions>
  <w:caption w:name="Table" w:pos="below" w:numFmt="decimal" />
</w:captions>

The caption element specifies the parameters for the resulting caption to be used to automatically label content within the WordprocessingML document. Specifically, the name and numFmt attributes specify that captions of this type inserted in the given WordprocessingML document shall consist of the string Table followed by an incrementing decimal number field. In addition, the pos attribute specifies that these captions shall be placed below the object they are used to label.

WordprocessingML is designed such that the caption element may be used in conjunction with applications to provide a dynamic captioning experience. In other words, an application may use the WordprocessingML in the example above to automatically insert a caption consisting of the string Table followed by an incrementing decimal number field below tables when tables are inserted into a WordprocessingML document as defined by the autoCaption element (§2.15.1.7). end example]

Attributes	Description
chapNum (Include Chapter Number in Field for Caption)	Specifies whether or not to display numbering associated with the most recent chapter heading in the WordprocessingML document within the caption field. A chapter heading is a paragraph of text within a WordprocessingML document that is formatted with a style that has been specified by the heading attribute to demarcate chapters in documents. Only a style with its styleID attribute equal to Heading1, Heading2, Heading3, Heading4, Heading5, Heading6, Heading7, Heading8, or Heading9 may be specified as the style used to demarcate chapters in a document. The choice of which of these heading levels shall be used to determine the current chapter number is defined by the value of the corresponding heading attribute. [Example: Heading1 is used as the chapter heading when chapNum is true and heading is 1. end example] If this attribute is omitted, then chapter numbers shall not be included in the resulting caption. [Example: Consider the diagram below: (missing picture pict-2.15.1.16-9) This diagram depicts a WordprocessingML document containing two chapters, each containing two tables labeled with captions. The Heading 2 style has been associated with chapter headings and applied to the strings: Chapter 1 - FY02 and Chapter 2 - FY03 in this document. Specifically, the style used to demarcate chapters, is the style with a styleID attribute equal to Heading2 as specified by the heading attribute value of 2 in the WordprocessingML for this caption, defined as follows: <w:caption w:name="Table" w:pos="below" w:chapNum="true" w:heading="2" w:numFmt="upperCase" w:sep="8212" />  The chapNum attribute has a value of true, specifying that the captions used to label the tables within this document will contain a symbol corresponding to the one-based index of the chapter in which it is contained. This can be seen in that the captions in Chapter 1 contain a 1, while the captions in Chapter 2 contain a 2, each corresponding with their respective chapter number. end example] The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).
heading (Style for Chapter Headings)	Specifies the given style that is used to demarcate chapter headings in a document. This value is used to link the chapter headings with paragraphs with a styleID attribute as follows: Value Description 1 Style with styleID of Heading1 2 Style with styleID of Heading2 3 Style with styleID of Heading3 4 Style with styleID of Heading4 5 Style with styleID of Heading5 6 Style with styleID of Heading6 7 Style with styleID of Heading7 8 Style with styleID of Heading8 9 Style with styleID of Heading9 Any other value Application-defined. May be ignored. If this attribute is omitted, then its value shall be assumed to be 1. [Example: Consider the diagram below: (missing picture pict-2.15.1.16-11) This diagram depicts a WordprocessingML document containing two chapters, each containing two tables labeled with captions. The Heading 2 style has been associated with chapter headings and applied to the strings: Chapter 1 - FY02 and Chapter 2 - FY03 in this document. Specifically, the style used to demarcate chapter headings is the style with its styleID attribute equal to Heading" as specified by the heading attribute value of 2 in the WordprocessingML below. <w:caption w:name="Table" w:pos="below" w:chapNum="On" w:heading="2" w:numFmt="upperCase" w:sep="8212" /> In other words, the WordprocessingML above may be used to label tables inserted in a given WordprocessingML document generated by an application with a caption consisting of: the string Table followed by a decimal number corresponding with the chapter number in which the table is present, a dash as defined in the sep attribute, and a capital English letter defined by the numFmt attribute corresponding with the given table's ordering within the current chapter. end example] The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).
name (Caption Type Name)	Specifies the literal string component of this caption. This value is used as follows: It is added to the field containing the chapter number and item number of this object when a caption is automatically added to the document. It is used to uniquely label this caption type, allowing it to be linked with classes of objects via the autoCaption element (§2.15.1.7) It may be used to label this caption type in a user interface. [Example: Consider the diagram below illustrating a WordprocessingML document containing a table that has been labeled with a caption: In this diagram, the table contained in the WordprocessingML document has been labeled by inserting a caption below the table consisting of the string Table followed by a decimal number. This caption format is specified with the following WordprocessingML: <w:caption w:name="Table" w:pos="below" w:numFmt="decimal" /> Specifically, the name attribute specifies that the first part of the string that comprises the give caption shall consist of the string Table. end example] The possible values for this attribute are defined by the ST_String simple type (§2.18.89).
noLabel (Do Not Include Name In Caption)	Specifies if the string specified in the name attribute shall be included in the resulting caption when it is automatically added to the document. If set to true, then the label text in the name attribute is omitted when adding the caption. If this attribute is omitted, then the name shall be added to the caption. [Example: Consider the diagram below illustrating a WordprocessingML document containing a table that has been labeled with a caption: In this diagram, the table contained in the WordprocessingML document has been labeled by inserting a caption below the table consisting of only a decimal number. This caption format is specified using the following WordprocessingML: <w:caption w:name="Custom" w:pos="below" w:noLabel="true" w:numFmt="decimal" />  Here, the noLabel attribute is equal to true specifying that when this caption format is automatically added, it shall not include the label. end example] The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).
numFmt (Caption Numbering Format)	Specifies the format of the numbering which shall be included in an automatically generated caption to specify the index of this item in that collection (within the current chapter if chapNum is specified, or within the current document story). If this attribute is omitted, then its default value shall be assumed to be decimal. [Example: Consider the diagram below illustrating a WordprocessingML document containing a table that has been labeled with a caption: In this example, the table contained in the WordprocessingML document has been labeled by inserting a caption below the table consisting of only a decimal number. This caption format is specified using the following WordprocessingML: <w:caption w:name="Custom" w:pos="below" w:noLabel="true" w:numFmt="decimal" />  Here, the numFmt attribute is equal to decimal, specifying that a decimal number shall be included in the table caption when it is automatically inserted. End Example] The possible values for this attribute are defined by the ST_NumberFormat simple type (§2.18.66).
pos (Automatic Caption Placement)	Specifies how an automatically inserted caption shall be positioned relative to the object that it is captioning. If this attribute is omitted, then the default value shall be below. [Example: Consider the diagram below illustrating a WordprocessingML document containing a table that has been labeled with a caption. In this diagram, the table contained in the WordprocessingML document has been labeled by inserting a caption below the table consisting of the string Table followed by a decimal number. This caption format is specified using the following WordprocessingML: <w:caption w:name="Table" w:pos="below" w:numFmt="decimal" />  The pos attribute specifies that the given caption shall be placed below the object it is labelling. end example] The possible values for this attribute are defined by the ST_CaptionPos simple type (§2.18.8).
sep (Chapter Number/Item Index Separator)	Specifies the character which shall be used to separate the chapter number used in this caption from the caption item numbering. A caption format consists of three components: The (optional) literal string The (optional) chapter number The index of this caption within the chapter/document When the latter two items are both present, they are delimited using the chapter separator specified by this attribute. If this attribute is omitted, then its default value shall be hyphen. If the chapter number is not part of the caption format, then this parameter shall be ignored. [Example: Consider the diagram below: (missing picture pict-2.15.1.16-13) This diagram depicts a WordprocessingML document containing two chapters, each containing two tables labeled with captions. The Heading 2 style has been associated with chapter headings and applied to the strings: Chapter 1 - FY02 and Chapter 2 - FY03 in this document. Specifically, the style used to demarcate chapter headings is the style with a styleID attribute equal to Heading2 as specified by the heading attribute value of 2 in the WordprocessingML below. <w:caption w:name="Table" w:pos="below" w:chapNum="On" w:heading="2" w:numFmt="upperCase" w:sep="hyphen" /> The sep attribute value of hyphen specifies that the chapter number and caption index shall be separated by a hyphen character when displayed in the document. end example] The possible values for this attribute are defined by the ST_ChapterSep simple type (§2.18.9).

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

<complexType name="CT_Caption">

<attribute name="name" type="ST_String" use="required"/>

<attribute name="pos" type="ST_CaptionPos" use="optional"/>

<attribute name="chapNum" type="ST_OnOff" use="optional"/>

<attribute name="heading" type="ST_DecimalNumber" use="optional"/>

<attribute name="noLabel" type="ST_OnOff" use="optional"/>

<attribute name="numFmt" type="ST_NumberFormat" use="optional"/>

<attribute name="sep" type="ST_ChapterSep" use="optional"/>

</complexType>

2.15.1.17 captions (Caption Settings)

This element specifies the presence of information about captions in a given WordprocessingML document. This information is divided into two components:

• The child element caption defines the format for a single type of caption to be automatically added to the document.
• The child element autoCaptions defines the types of objects to which a caption format shall automatically be applied.

This information should be used to determine the captions which are automatically added to objects when they are inserted into a WordprocessingML document. [Note: This setting is typically ignored unless it is specified in an application's default template. end note]

[Example: Consider the diagram below illustrating a WordprocessingML document containing a table that has been labeled with a caption:

In this diagram, the table contained in the WordprocessingML document has been labeled by inserting a caption below the table consisting of the string Table followed by a decimal number. This automatically inserted caption format is specified using the following WordprocessingML:

<w:captions>

  <w:caption w:name="Table" w:pos="below" w:numFmt="decimal" /> 

</w:captions>

Here, the captions element specifies the presence of one or more caption formats in a given WordprocessingML document with its child element caption. Specifically, the child element caption specifies a single type of caption to be used within the WordprocessingML document. end example]

Captioning leverages fields (§2.16.5) to label objects with reference to either:

• Other captioned objects within a given document
• Other captioned objects within the same chapter in a given document (when chapter numbers are added by specifiying the chapNum attribute on the caption type.
  
  A chapter is a section of text within a WordprocessingML document that is preceded by content with a style that has been specified by to demarcate chapters in documents. Only one style may be specified as the style used for a single caption type to demarcate chapters in a document. A chapter ends immediately above the next instance of content with the style used to demarcate chapters.

[Example: Consider the diagram below:

This diagram depicts a WordprocessingML document containing two chapters, each containing two tables labeled with captions. The style associated with chapter demarcation has been applied to the strings: Chapter 1 - FY02 and Chapter 2 - FY03 in this document. Specifically, the style used to demarcate chapters is the style with its styleID attribute equal to Heading2 as specified by the heading attribute value of 2 in the WordprocessingML for the caption format:

<w:caption w:name="Table" w:pos="below" w:chapNum="On" w:heading="2" w:numFmt="upperCase" w:sep="8212" /> 

In other words, the WordprocessingML above may be used to label objects (in this case, tables) inserted in a given WordprocessingML document generated by an application with a caption consisting of: the string Table followed by a decimal number corresponding with the chapter number in which the table is present, a hyphen, and a capital English letter corresponding with the given table's index within the given chapter. end example]

[Note: WordprocessingML is designed such that the caption element may be used in conjunction with applications to provide a dynamic captioning experience. In other words, an application may use the WordprocessingML in the example above to automatically insert a caption consisting of the string Table followed by an incrementing decimal number field below tables when tables are inserted into a WordprocessingML document as defined by the autoCaption element (§2.15.1.7). End note]

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

<complexType name="CT_Captions">

<sequence>

<element name="caption" type="CT_Caption" minOccurs="1" maxOccurs="unbounded"/>

<element name="autoCaptions" type="CT_AutoCaptions" minOccurs="0" maxOccurs="1"/>

</sequence>

</complexType>

2.15.1.18 characterSpacingControl (Character-Level Whitespace Compression)

This element specifies how full-width characters in the current WordprocessingML document should be compressed to remove additional whitespace when the contents of this document are displayed, specifically by specifying the set(s) of characters which may be compressed to remove additional whitespace. [Note: The behavior of this element is functionally identical to the CSS text-justify-trim property. end note]

If this element is omitted, then the default value shall be dontCompress.

[Example: Consider the WordprocessingML below:

<w:characterSpacingControl w:val="dontCompress" />

The characterSpacingControl element has a val attribute value of dontCompress, which specifies that no character compression shall be applied to any character when the document is displayed. end example]

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

<complexType name="CT_CharacterSpacing">

<attribute name="val" type="ST_CharacterSpacing" use="required"/>

</complexType>

2.15.1.19 clickAndTypeStyle (Paragraph Style Applied to Automatically Generated Paragraphs)

This element specifies the paragraph style, specified using the style element, which shall be applied to paragraphs which are automatically created when text is inserted into a WordprocessingML document in an area of the document that has no other style associated with it. This style is referenced via the val attribute, which stores the style ID of the style (stored in the styleId attribute on the style definition).

[Guidance: Consider a WordprocessingML document opened in an application that allows users to place their cursor anywhere within the document editing canvas and enter text. The clickAndTypeStyle element should be used to specify the paragraph style to be associated with the paragraph of text entered after a user places their cursor somewhere in the blank document that results in the generation of new paragraphs. end guidance]

If this element is omitted, then the default paragraph style (the paragraph style whose default attribute is set to true), shall be used for automatically generated paragraphs. If the style whose styleId is specified using the val attribute is not a paragraph style or does not exist in the document, then the default paragraph style shall be used instead.

[Example: Consider a WordprocessingML document that has specified that paragraphs which are automatically created when text is inserted in a given area of the document which has no other style associated with it shall be associated with the paragraph style that has a styleId equal to BalloonText.

This is accomplished by specifying a clickAndTypeStyle element with a val attribute equal to the value of the ID of the desired style. This constraint would be specified using the following WordprocessingML:

<w:clickAndTypeStyle w:val="BalloonText" />

The corresponding style in the styles part would be defined as follows:

<w:style w:type="paragraph" w:styleId="BalloonText">
  ...
</w:style>

The clickAndTypeStyle element specifies the use of the paragraph style with the style ID of BalloonText. end example]

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

<complexType name="CT_String">

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.20 clrSchemeMapping (Theme Color Mappings)

This element specifies the theme color, stored in the document's Theme part to which the value of this theme color shall be mapped. This mapping enables multiple theme colors to be chained together.

[Example: Consider a WordprocessingML document that shall have the theme color value background1 mapped to the theme color light1 as defined in the document's theme part. This requirement would be specified using the following WordprocessingML in the document settings:

<w:clrSchemeMapping w:bg1="light1" />

The clrSchemeMapping element's attribute background1 has a value of light1, specifying that theme color value background1 shall be mapped to the theme color light1. end example]

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

<complexType name="CT_ColorSchemeMapping">

<attribute name="bg1" type="ST_ColorSchemeIndex"/>

<attribute name="t1" type="ST_ColorSchemeIndex"/>

<attribute name="bg2" type="ST_ColorSchemeIndex"/>

<attribute name="t2" type="ST_ColorSchemeIndex"/>

<attribute name="accent1" type="ST_ColorSchemeIndex"/>

<attribute name="accent2" type="ST_ColorSchemeIndex"/>

<attribute name="accent3" type="ST_ColorSchemeIndex"/>

<attribute name="accent4" type="ST_ColorSchemeIndex"/>

<attribute name="accent5" type="ST_ColorSchemeIndex"/>

<attribute name="accent6" type="ST_ColorSchemeIndex"/>

<attribute name="hyperlink" type="ST_ColorSchemeIndex"/>

<attribute name="followedHyperlink" type="ST_ColorSchemeIndex"/>

</complexType>

2.15.1.21 consecutiveHyphenLimit (Maximum Number of Consecutively Hyphenated Lines)

This element specifies the maximum number of consecutive lines of text that can end with a hyphen when the contents of this document are displayed. Once this limit has been reached, the following line shall not be hyphenated regardless of whether or not it meets the criteria needed for hyphenation.

If this element is omitted or has its val attribute equal to 0, the given WordprocessingML document shall have no limit on the number of consecutive lines of text that may end with a hyphen.

[Example: Consider a WordprocessingML document which should automatically be hyphenated. If the contents of this document result in hyphens appearing on every line in the document, as follows:

This output may be undesirable. If the document shall have a maximum of two consecutive hyphens, this requirement is specified using the following WordprocessingML in the document settings:

<w:consecutiveHyphenLimit w:val="2" />

The consecutiveHyphenLimit element's val attribute has a value of 2 specifying that a maximum of two hyphens should be allowed, limiting the hyphenation output like this:

end example]

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

<complexType name="CT_DecimalNumber">

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

</complexType>

2.15.1.22 decimalSymbol (Radix Point for Field Code Evaluation)

This element specifies the character that shall be interpreted as the radix point when evaluating the contents of all fields in the current document.

[Rationale: When evaluating field instructions based on the contents of the current document, it is necessary to know the character which shall be treated as the radix point in order to prevent changes to the calculation of the same field instructions based on the current user's locale. This element stores the radix point which shall be used to evaluate fields in the contents of this document, irrespective of the locale of the application loading the file. end rationale]

If this element is omitted, the application shall use the default radix point of its current locale setting to evaluate field instructions. If this element's attribute value is more than a single character, then the document is non-conformant.

[Example: Consider a WordprocessingML document which should use the comma character as the radix point for all field instructions. This requirement is specified using the following WordprocessingML in the document settings:

<w:decimalSymbol w:val="," />

The decimalSymbol element's val attribute has a value of , specifying that the comma character shall be interpreted as the radix point.

For instance, the string 12.345,00 would be interpreted as a numeric value of twelve thousand three hundred and forty five. If the decimalSymbol was a period, the same string would be twelve and three hundred and forty five thousandths. end example]

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

<complexType name="CT_String">

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.23 defaultTableStyle (Default Table Style for Newly Inserted Tables)

This element specifies the table style which shall automatically be applied to the table properties of tables added to this document by an application. Note that it does not change the table style applied to tables which do not reference a style, instead, it automatically applies the style to that table via the tblStyle element (§2.4.59). This link is made by referencing the styleId attribute value of the table style which shall be used to format newly inserted tables.

If this element is omitted, then no table style shall automatically be applied to inserted tables (therefore inheriting the default table style). If the referenced style is not present or not a table style, then no table style shall automatically be applied to inserted tables.

[Example: Consider a WordprocessingML document which should use the LightShading-Accent3 style. This requirement is specified using the following WordprocessingML in the document settings:

<w:defaultTableStyle w:val="LightShading-Accent3" />

The corresponding table style must therefore exist in the styles part:

<w:style w:type="table" w:styleId="LightShading-Accent3">
  ...
</w:style>

The defaultTableStyle element's val attribute has a value of LightShading-Accent3 specifying that that style will be applied automatically to newly inserted tables. end example]

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

<complexType name="CT_String">

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.24 defaultTabStop (Distance Between Automatic Tab Stops)

This element specifies the value which shall be used as the multiplier to generate automatic tab stops in this document. Automatic tab stops refer to the tab stop locations which occur after all custom tab stops in the current paragraph have been surpassed.

If this element is omitted, then automatic tab stops should be generated at 720 twentieths of a point (0.5") intervals across the displayed page.

[Example: Consider a WordprocessingML document which should have automatic tab stops every 360 twentieths of a point (0.25 inches). This requirement is specified using the following WordprocessingML in the document settings:

<w:defaultTabStop w:val="360" />

The defaultTabStop element's val attribute has a value of 360 specifying that automatic tab stops shall occur every 1/4th of an inch across the page.

If a custom tab stop was located at 2.28", then the next three automatic tab stops would be at 2.5", 2.75" and 3.0" (the next three multiples of the default tab stop value). end example]

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

<complexType name="CT_TwipsMeasure">

<attribute name="val" type="ST_TwipsMeasure" use="required"/>

</complexType>

2.15.1.25 displayBackgroundShape (Display Background Objects When Displaying Document)

This element specifies whether the images and colors defined in the document's background using the background element (§2.2.1) shall be displayed when the document is displayed in print layout view as specified in the view element (§2.15.1.93).

If this element is omitted, then background shapes shall not be displayed when the document is displayed in print layout view.

[Example: Consider a WordprocessingML document that has a turquoise background specified for all pages and is being displayed in page layout view, as follows:

(missing picture pict-2.15.1.25-17)

If the document's background should not be displayed, that requirement would be specified using the following WordprocessingML in the document settings:

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

The resulting document would display the background in page layout view:

(missing picture pict-2.15.1.25-18)

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.26 displayHorizontalDrawingGridEvery (Distance between Horizontal Gridlines)

This element specifies the number of horizontal grid units defined using the drawingGridHorizontalSpacing element (§2.15.1.44) which shall be allowed between subsequent visible horizontal drawing grid lines in this document, if gridlines are being shown. [Note: The display of gridlines is an application-level setting not specified in this Office Open XML Standard. end note] The drawing grid is a grid which may be used by applications to help position floating objects in the document.

If this element is omitted, then gridlines shall be displayed for each horizontal grid unit.

[Example: Consider the image below illustrating a WordprocessingML document in which all horizontal grid units are visible (the default setting):

If the gridlines in this document shall only be displayed for every 4th horizontal drawing gridline, that requirement would be specified using the following WordprocessingML in the document settings:

<w:displayHorizontalDrawingGridEvery w:val="4" />

The resulting grid would look like the following:

The displayHorizontalDrawingGridEvery element has its val attribute equal to 4, therefore every fourth gridline is displayed in the document when the drawing grid is turned on. end example]

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

<complexType name="CT_DecimalNumber">

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

</complexType>

2.15.1.27 displayVerticalDrawingGridEvery (Distance between Vertical Gridlines)

This element specifies the number of vertical grid units defined using the drawingGridVerticalSpacing element (§2.15.1.46) which shall be allowed between subsequent vertical gridlines in this document, if gridlines are being shown. [Note: The display of gridlines is an application-level setting not specified in this Office Open XML Standard. end note] The drawing grid is a grid which may be used by applications to help position floating objects in the document.

If this element is omitted, then vertical gridlines shall not be displayed.

[Example: Consider the image below illustrating a WordprocessingML document in which all vertical grid units are visible (the default setting):

If the vertical drawing gridlines in this document shall only be displayed for every 4th gridline, that requirement would be specified using the following WordprocessingML in the document settings:

<w:displayVerticalDrawingGridEvery w:val="4" />

The resulting grid would look like the following:

The displayVerticalDrawingGridEvery element has its val attribute equal to 4, therefore every fourth vertical gridline is displayed in the document when the drawing grid is turned on. end example]

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

<complexType name="CT_DecimalNumber">

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

</complexType>

2.15.1.28 documentProtection (Document Editing Restrictions)

This element specifies the set of document protection restrictions which have been applied to the contents of a WordprocessingML document. These restrictions shall be enforced by applications editing this document when the enforcement attribute is turned on, and should be ignored (but persisted) otherwise. Document protection is a set of restrictions used to prevent unintentional changes to all or part of a WordprocessingML document - since this protection does not encrypt the document, malicious applications may circumvent its use. This protection is not intended as a security feature and may be ignored.

If this element is omitted, then no protection shall be applied to this document.

When a password is supplied via an application which shall be hashed and stored in this element, that process shall be done in two stages:

First, the password shall be hashed using the following algorithm:

• Truncate the password to 15 characters.
• Construct a new NULL-terminated string consisting of single-byte characters:
• Get the single-byte values by iterating through the Unicode characters of the truncated password. For each character, if the low byte is not equal to 0, take it. Otherwise, take the high byte.
• From now on, the single-byte character string is used.
• If the password is empty, return 0.
• Compute the high-order word of the new key:
• Initialize from the initial code array (see below), depending on the password's length. For each character in the password:
• For every bit in the character, starting with the least significant and progressing to (but excluding) the most significant, if the bit is set, XOR the key's high-order word with the corresponding word from the encryption matrix
• Compute the low-order word of the new key:
• Initialize with 0
• For each character in the password, going backwards, low-order word = (((low-order word SHR 14) AND 0x0001) OR (low-order word SHL 1) AND 0x7FFF)) XOR character
• Lastly, low-order word = (((low-order word SHR 14) AND 0x0001) OR (low-order word SHL 1) AND 0x7FFF)) XOR password length XOR 0xCE4B.

Initial code array

The initial code array contains the initial values for the key's high-order word. The initial value depends on the length of the password, as follows:

Encryption matrix

The encryption matrix contains codes used during the calculation of the key's high-order word. As described in the algorithm above, for every bit of the password's characters, if the bit is set, a corresponding value is taken from this encryption matrix and is used to XOR the key's high-order word with it. Each row in the encryption matrix corresponds to a single character from the password, and each of the seven columns corresponds to a particular bit (0-6) in this character.

The values are taken in such a way so that the last character of the password uses the last row in the encryption matrix. The next-to-last character uses the next-to-last row in the matrix, and so on. This means that the beginning of the matrix may be unused, depending on the length of the password.

[Example: Consider a password which has been supplied - the string "Example". It is already under 15 characters, so truncation does not affect it. It is then converted to a string of single-byte characters.

• The password is 7 characters long, so, from the initial code array, the initial value for the key's high-order word is 0xF1CE.
• The key's high-order word is then computed further depending on the password's characters:
• The first character is 'E' (0x45). This is the first character of a 7-character password, so its corresponding row in the encryption matrix is "Last-6".
• Bit 0 is set, therefore the key's high-order word is combined (via XOR) with the corresponding value for Bit 0 on row "Last-6", which is 0xB861. The new result is 0xF1CE XOR 0xB861 = 0x49AF.
• Bit 2 is set, so the key's high-order word is XOR-ed with the corresponding value for Bit 2 on row "Last-6", which is 0xC1C6. The new result is 0x49AF XOR 0xC1C6 = 0x8869.
• This process is repeated for each bit.
• The next character is 'x' (0x78). Its corresponding row in the encryption matrix is "Last-5".
• Bit 3 is set. The value for Bit 3 on row "Last-5" in the encryption matrix is 0x0D42. The current value for the key's high-order byte is 0x5585, so the new one should be 0x5585 XOR 0x0D42 = 0x58C7.
• This process is repeated for each bit.
• This process is repeated for all characters.
• After the last character has been processed, the above step produced 0x64CE for the key's high-order word. Now the low-order word needs to be calculated:
• The initial value is 0.
• It is then calculated using the password:
• The last character of the password is 'e' (0x65), so, by the formula, low-order word = (((low-order word SHR 14) AND 0x0001) OR ((low-order word SHL 1) AND 0x7FFF)) XOR 'e' = (((0 SHR 14) AND 0x0001) OR ((0 SHL 1) AND 0x7FFF)) XOR 0x65 = 0x0065.
• The next to last character of the password is 'l' (0x6C). Again, by the formula, (((0x0065 SHR 14) AND 0x0001) OR ((0x0065 SHL 1) AND 0x7FFF)) XOR 0x6C = (0x0000 OR 0x00CA) XOR 0x6C = 0x00CA XOR 0x6C = 0x00A6.
• This process is repeated for each character.
• After the password's first character has been processed, we have 0x1199 for the key's low-order word. Lastly, the password's length is combined into it: low-order word = (((0x1199 SHR 14) AND 0x0001) OR ((0x1199 SHL 1) AND 0x7FFF)) XOR 0x0007 XOR 0xCE4B = 0x2332 XOR 0x0007 XOR 0xCE4B = 0x2335 XOR 0xCE4B = 0xED7E.
• The end result for the key is 0x64CEED7E.

end example]

[Rationale: This pre-processing step is necessary for compatibility with legacy word processing applications which hashed their password solely using this mechanism. end rationale]

Second, the byte order of the result shall be reversed [Example: 0x64CEED7E becomes 7EEDCE64. end example], and that value shall be hashed as defined by the attribute values.

[Note: The algorithm above can be stated as follows using diagrams:

(missing picture pict-2.15.1.28-19)

end note]

[Example: Consider a WordprocessingML document which specifies that applications shall not allow any modifications to this document other than the addition of comments. This requirement would be specified using the following WordprocessingML in the document settings:

<w:documentProtection w:edit="comments" w:enforcement="true" ... 
  w:cryptAlgorithmClass="hash" w:cryptAlgorithmType="typeAny"
  w:cryptAlgorithmSid="1" w:hash="9oN7nWkCAyEZib1RomSJTjmPpCY=" /> 

The documentProtection element has an edit attribute value of comments, specifying that the only modification allowed should be comments, the enforcement attribute has a value of true, specifying that the document protection specified is to be enforced on the given document. Finally, in order for the hosting application to stop enforcement of the document protection applied to the document, the hosting application would have to be provided with a password that the hosting application would then hash, compare to the value of the hash attribute (9oN7nWkCAyEZib1RomSJTjmPpCY=), and if the two values matched, halt enforcement of any document protection. end example]

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

<complexType name="CT_DocProtect">

<attribute name="edit" type="ST_DocProtect" use="optional"/>

<attribute name="formatting" type="ST_OnOff" use="optional"/>

<attribute name="enforcement" type="ST_OnOff"/>

<attributeGroup ref="AG_Password"/>

</complexType>

2.15.1.29 documentType (Document Classification)

This element specifies the classification of a given WordprocessingML document as a letter, email, or general document.

[Note: This element may be used by hosting applications to facilitate customized user interface and/or automatic formatting behaviors based on the 'type' of a given WordprocessingML document. end note]

If this element is omitted, then the document shall be classified as a general document.

[Example: Consider a set of WordprocessingML documents which should be classified as 'letters'. This classification would be specified using the following WordprocessingML in the document settings of these documents:

<w:documentType w:val="letter" /> 

The documentType element's val attribute is equal to letter, specifying that the hosting application shall apply the behaviors it has specified for letters to the given WordprocessingML document. end example]

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

<complexType name="CT_DocType">

<attribute name="val" type="ST_DocType" use="required"/>

</complexType>

2.15.1.30 docVar (Single Document Variable)

This element specifies the parameters of a single document variable. A document variable is a storage location for arbitrary customer data in name/value pairs that will be persisted in a given WordprocessingML document. Specifically, this element specifies through its name and val attributes the name and value pair for a given document variable.

[Note: This mechanism is maintained for legacy compatibility only, and should be avoided in favor of the custom XML data support defined in this Office Open XML Standard. end note]

[Example: Consider the following WordprocessingML fragment specifying a document variable named example and containing the value example value:

<w:docVars>

  <w:docVar w:name="example" w:val="example value" />

</w:docVars>

The docVar element defines a single document variable, named example using the name attribute, and assigned the value example value through the val attribute. end example]

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

<complexType name="CT_DocVar">

<attribute name="name" type="ST_String" use="required"/>

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.31 docVars (Document Variables)

This element specifies the presence of document variables in a WordprocessingML. A document variable is a storage location for arbitrary customer data in name/value pairs that will be persisted in a given WordprocessingML document.

[Note: This mechanism is maintained for legacy compatibility only, and should be avoided in favor of the custom XML data support defined in this Office Open XML Standard. end note]

[Example: Consider the following WordprocessingML specifying three document variables:

<w:docVars>

  <w:docVar ... />
  <w:docVar ... />
  <w:docVar ... />
</w:docVars>

The docVars element contains three child elements each defining a single document variable in this document. end example]

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

<complexType name="CT_DocVars">

<sequence>

<element name="docVar" type="CT_DocVar" minOccurs="0" maxOccurs="unbounded"/>

</sequence>

</complexType>

2.15.1.32 doNotAutoCompressPictures (Do Not Automatically Compress Images)

This element specifies that pictures in this document shall not automatically be compressed when saving the document in order to reduce the overall size of the resulting WordprocessingML document.

If this element is omitted, applications may perform basic compression on images before saving the contents of the document.

[Example: Consider a WordprocessingML document which should never have its images compressed before they are saved. This requirement would be specified using the following WordprocessingML:

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

The doNotAutoCompressPictures element's val attribute has a value of true specifying that images shall not be automatically compressed when the document is saved. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.33 doNotDemarcateInvalidXml (Do Not Show Visual Indicator For Invalid Custom XML Markup)

This element specifies whether a visual cue should be displayed around content contained in a WordprocessingML document which is contained with custom XML markup specified via the customXml element when an application determines that the current XML markup (or its contents) violate the constraints of the attached XML schema(s).

If this element is not present in a WordprocessingML document visual cues shall be displayed on content contained in custom XML markup in a WordprocessingML document which is considered to be invalid based on the associated XML schema(s).

[Example: Consider a WordprocessingML document which should show no visual indication of invalid custom XML markup. This requirement would be specified using the following WordprocessingML:

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

The doNotDemarcateInvalidXml element's val attribute has a value of true specifying the display of any visual indication of invalid custom XML markup shall be suppressed for this document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.34 doNotDisplayPageBoundaries (Do Not Display Visual Boundary For Header/Footer or Between Pages)

This element specifies whether applications displaying this document should display the contents of the header and footer when displaying the document in print layout view (§2.15.1.93) or should collapse those areas as well as the whitespace on all displayed pages so that the text extents are directly following one another. [Rationale: Collapsing the ends of pages makes it easier to read the contents of the document, since the text flows between pages without whitespace, while maintaining the WYSIWYG functionality of print layout view for the document's main content. end rationale]

If this element is omitted, then all pages should be shown at their full size (including whitespace and headers/footers) when they are displayed in print layout view.

[Example: Consider the images below illustrating two pages in a WordprocessingML document:

If document shall automatically have whitespace between pages removed when it is displayed, that requirement would be specified using the following WordprocessingML in the document settings:

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

The resulting output might look like the following:

The doNotDisplayPageBoundaries element has its val attribute equal to true, therefore the document is automatically displayed with whitespace between text extents on following pages compressed, allowing the pages to be viewed more easily. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.35 doNotEmbedSmartTags (Remove Smart Tags When Saving)

This element specifies if any smart tags specified using the smartTag element shall be removed from the contents of this document before it is resaved. This setting shall also prevent the addition of new smart tags to the content of the document.

If this element is omitted, then smart tags shall not be removed from the file when it is saved.

[Example: Consider a WordprocessingML document which should never be saved with smartTag elements in its contents. This requirement is specified using the following WordprocessingML fragment in the document settings:

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

The doNotEmbedSmartTags element's val attribute has a value of true specifying that smart tags shall never be saved in the contents of this document. For example, if a run formerly looked like this:

<w:p>
  <w:r>
    <w:t xml:space="preserve">Hello</w:t>
  </w:r>
  <w:smartTag ... >
    <w:r>
      <w:t>world<w:t>
    </w:r>
  </w:smartTag>
</w:p>

The presence of this element specifies that the SmartTag element shall be removed, and applications may then choose to combine duplicated runs as desired. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.36 doNotHyphenateCaps (Do Not Hyphenate Words in ALL CAPITAL LETTERS)

This element specifies whether or not words comprised of all capital letters shall be hyphenated within a given document when automatic hyphenation is specified via the autoHyphenation element (§2.15.1.10).

If this element is omitted, then words in ALL CAPITAL LETTERS shall be hyphenated when the document is hyphenated.

[Example: Consider a document which is automatically hyphenated containing the following paragraph of content:

If words in ALL CAPITAL LETTERS shall not be hyphenated, this requirement would be specified by adding the following WordprocessingML to the document settings part:

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

The resulting content would not be hyphenated:

The doNotHyphenateCaps element val set to true, specifying that the first line of text to end with the word SHORT as the word HYPHENATION had to be moved to the second line since it could not fit in its entirety on the first line.

Conversely, setting the doNotHyphenateCaps element val set to off (the default) caused the first line of text to contain a hyphenated portion of the word HYPHENATION as hyphenation of words comprised of all capital letters is permitted. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.37 doNotIncludeSubdocsInStats (Do Not Include Content in Text Boxes, Footnotes, and Endnotes in Document Statistics)

This element specifies if document content contained in text boxes, footnotes, and endnotes shall be excluded when an application calculates a given document's statistics when these values are calculated and/or displayed by an application.

[Note: Some examples of document statistics that an application may chose to calculate are: number of words, number of characters, number of paragraphs, number of pages, number of lines, and so on. end note]

[Example: Consider a WordprocessingML that specifies that it shall not include these document stories when its contents are used to calculate document statistics. This requirement would be specified using the following WordprocessingML in the document settings part:

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

The doNotIncludeSubdocsInStats element's val attribute has a value of true specifying that only the contents of the main document story should be used when calculating document statistics. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.38 doNotShadeFormData (Do Not Show Visual Indicator For Form Fields)

This element specifies whether a visual cue should be displayed around form fields contained in a WordprocessingML document specified via the FORMTEXT, FORMCHECKBOX, or FORMDROPDOWN fields.

If this element is not present in a WordprocessingML document visual cues should be displayed on form fields contained in the document.

[Example: Consider a WordprocessingML document which should no visual indication of form fields. This requirement would be specified using the following WordprocessingML:

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

The doNotShadeFormData element's val attribute has a value of true specifying the display of any visual indication of form fields shall be suppressed for this document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.39 doNotTrackFormatting (Do Not Track Formatting Revisions When Tracking Revisions)

This element specifies that applications shall not track revisions made to the formatting of this WordprocessingML document when the trackRevisions element (§2.15.1.90) is turned on.

If this element is omitted, then revisions to formatting shall be generated by changes to the contents of this document when the trackRevisions element is turned on.

[Example: Consider a WordprocessingML document containing the text run Example that shall have revisions tracked. Example WordprocessingML from Document 1 is given below:

<w:document>
  <w:body>
    <w:p>
      <w:r>
        <w:t>Example</w:t>
      </w:r>
    </w:p>
  </w:body>
</w:document>

If the word text was added to the end of this document and bolded, the resulting WordprocessingML would be output as follows:

<w:document>
  <w:body>
    <w:p>
      <w:r>
        <w:t>Example</w:t>
      </w:r>
      <w:ins ... >
        <w:r>
          <w:rPr>
            <w:b/>
            <w:rPrChange ... >
              <w:rPr/>
            <w:rPrChange>
          </w:rPr>
          <w:t>text</w:t>
        </w:r>
      </w:ins>
    </w:p>
  </w:body>
</w:document>

If changes to formatting were turned off using the following WordprocessingML syntax in the document settings:

<w:settings>
  <w:trackRevisions w:val="true" />
  <w:doNotTrackFormatting w:val="true" />
  ...
</w:settings>

The same revision (the word text was added to the end of this document and bolded) would result in the following markup:

<w:document>
  <w:body>
    <w:p>
      <w:r>
        <w:t>Example</w:t>
      </w:r>
      <w:ins ... >
        <w:r>
          <w:rPr>
            <w:b/>
          </w:rPr>
          <w:t>text</w:t>
        </w:r>
      </w:ins>
    </w:p>
  </w:body>
</w:document>

The doNotTrackFormatting element's val attribute was set to true, therefore the changes to the formatting of the document were not tracked as revisions in the document's WordprocessingML. Specifically, applying bold formatting to the text was not tracked as a revision with the rPrChange (§2.13.5.32) element. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.40 doNotTrackMoves (Do Not Use Move Syntax When Tracking Revisions)

This element specifies that applications shall not track revisions made to this WordprocessingML document as moves when the trackRevisions element (§2.15.1.90) is turned on, even when that syntax is appropriate. Instead, applications should use a standard insertion and deletion annotation syntax. Existing moves shall not be modified. [Rationale: This element is provided to enable interoperability with earlier word processing applications which do not understand moves. end rationale]

If this element is omitted, then move annotations may be generated by changes to the contents of this document when the trackRevisions element is turned on as appropriate.

[Example: Consider a WordprocessingML that specifies that it shall not have additional moves added to its contents. This requirement would be specified using the following WordprocessingML in the document settings part:

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

The doNotTrackMoves element's val attribute has a value of true specifying that insertion/deletion annotations shall be used rather than moves when revisions are tracked in this document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.41 doNotUseMarginsForDrawingGridOrigin (Do Not Use Margins for Drawing Grid Origin)

This element specifies that the top-left corner of the page shall not be used as the origin for the drawing grid. The drawing grid is a virtual grid which may be used by applications to specify where drawing objects shall be positioned on a page when inserted (i.e. to ensure objects are aligned, etc.). If this element is present the grid shall start at the top-left edge of the page and not the text extents.

If this element is omitted, then the gridlines shall start at the topmost edge of the text extents.

[Example: Consider a WordprocessingML document whose drawing grid shall begin at the top left edge of the page. This requirement would be specified using the following WordprocessingML markup in the document settings:

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

The doNotUseMarginsForDrawingGridOrigin element's val attribute is equal to true specifying that the document's drawing grid shall begin from the top left corner of the page, rather than the top left corner of the text extents. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.42 doNotValidateAgainstSchema (Do Not Validate Custom XML Markup Against Schemas)

This element specifies that applications shall not validate the custom XML markup in this document against the applicable custom XML schema(s), even when those schemas are available. The application should silently behave as if it was unable to provide this functionality.

If this element is omitted, then applications which support this functionality should attempt to validate the custom XML contents against any available related custom XML schema(s).

[Example: Consider a WordprocessingML document which should not have its custom XML content validated even by applications which support this operation. This requirement is specified using the following WordprocessingML in the document settings:

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

The doNotValidateAgainstSchema element's val attribute has a value of true specifying that the custom XML markup in this document shall not be validated. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.43 drawingGridHorizontalOrigin (Drawing Grid Horizontal Origin Point)

This element specifies the distance from of the left edge of the page which shall be used as the origin for the horizontal gridlines used by the drawing grid. The drawing grid is a virtual grid which may be used by applications to specify where drawing objects shall be positioned on a page when inserted (i.e. to ensure objects are aligned, etc.). Since the grid always covers the entire page when the doNotUseMarginsForDrawingGridOrigin element (§2.15.1.41) is specified, this element shall only affect the starting edge of the first horizontal gridline displayed (i.e. it only adjusts the grid by the modulus of the value against the width of one grid unit).

If this element is omitted, then the gridlines shall start at the leftmost edge of the page. If the doNotUseMarginsForDrawingGridOrigin element is not specified, then this element is ignored.

[Example: Consider a WordprocessingML document whose drawing grid shall begin three inches (4320 twentieths of a point) before the left edge of the page. This requirement would be specified using the following WordprocessingML markup in the document settings:

<w:settings>
  ...
<w:dontuseMarginsForDrawingGridOrigin w:val="true" />
<w:drawingGridHorizontalOrigin w:val="4320" />
  ...
</w:settings>

The drawingGridHorizontalOrigin element's val attribute is equal to 4320 specifying that the horizontal edge of the document's drawing grid shall begin three inches (4320 twentieths of a point) from the left edge of the page, since the dontUseMarginsForDrawingGridOrigin element's val attribute is equal to true. end example]

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

<complexType name="CT_TwipsMeasure">

<attribute name="val" type="ST_TwipsMeasure" use="required"/>

</complexType>

2.15.1.44 drawingGridHorizontalSpacing (Drawing Grid Horizontal Grid Unit Size)

This element specifies the width of horizontal grid units in this document. The drawing grid is a grid which may be used by applications to help position floating objects in the document.

If this element is omitted, then each horizontal grid unit shall be 180 twentieths of a point (0.125") in width.

[Example: Consider the image below illustrating a WordprocessingML document in which all horizontal grid units are each 144 twentieths of a point wide (and all are showing):

If the gridlines in this document shall only be displayed for every half an inch, that requirement would be specified using the following WordprocessingML in the document settings:

<w:drawingGridHorizontalSpacing w:val="720" />

The resulting grid would look like the following:

The drawingGridHorizontalSpacing element has its val attribute equal to 720, therefore every horizontal gridline has a width of one half of an inch (720 twentieths of a point). end example]

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

<complexType name="CT_TwipsMeasure">

<attribute name="val" type="ST_TwipsMeasure" use="required"/>

</complexType>

2.15.1.45 drawingGridVerticalOrigin (Drawing Grid Vertical Origin Point)

This element specifies the distance from of the top edge of the page which shall be used as the origin for the vertical gridlines used by the drawing grid. The drawing grid is a virtual grid which may be used by applications to specify where drawing objects shall be positioned on a page when inserted (i.e. to ensure objects are aligned, etc.). Since the grid always covers the entire page when the doNotUseMarginsForDrawingGridOrigin element (§2.15.1.41) is specified, this element shall only affect the starting edge of the first vertical gridline displayed (i.e. it only adjusts the grid by the modulus of the value against the width of one grid unit).

If this element is omitted, then the gridlines shall start at the topmost edge of the page. If the doNotUseMarginsForDrawingGridOrigin element is not specified, then this element is ignored.

[Example: Consider a WordprocessingML document whose drawing grid shall begin one inch (1440 twentieths of a point) before the top edge of the page. This requirement would be specified using the following WordprocessingML markup in the document settings:

<w:settings>
  ...
<w:dontuseMarginsForDrawingGridOrigin w:val="true" />
<w:drawingGridVerticallOrigin w:val="1440" />
  ...
</w:settings>

The drawingGridVerticalOrigin element's val attribute is equal to 1440 specifying that the vertical edge of the document's drawing grid shall begin one inch (1440 twentieths of a point) from the top edge of the page, since the dontUseMarginsForDrawingGridOrigin element's val attribute is equal to true. end example]

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

<complexType name="CT_TwipsMeasure">

<attribute name="val" type="ST_TwipsMeasure" use="required"/>

</complexType>

2.15.1.46 drawingGridVerticalSpacing (Drawing Grid Vertical Grid Unit Size)

This element specifies the width of vertical grid units in this document. The drawing grid is a grid which may be used by applications to help position floating objects in the document.

If this element is omitted, then each vertical grid unit shall be 180 twentieths of a point (0.125") in width.

[Example: Consider the image below illustrating a WordprocessingML document in which all vertical grid units are each 144 twentieths of a point high (and all are showing):

If the vertical gridlines in this document shall only be displayed for every half an inch, that requirement would be specified using the following WordprocessingML in the document settings:

<w:drawingGridVerticalSpacing w:val="720" />

The resulting grid would look like the following:

The drawingGridVerticalSpacing element has its val attribute equal to 720, therefore every vertical gridline has a height of one half of an inch (720 twentieths of a point). end example]

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

<complexType name="CT_TwipsMeasure">

<attribute name="val" type="ST_TwipsMeasure" use="required"/>

</complexType>

2.15.1.47 forceUpgrade (Upgrade Document on Open)

This element specifies that the contents of this document may be upgraded and that the resulting document shall not have its functionality limited to only those functions compatible with earlier word processing applications. The only actions required as part of upgrading the document are:

• The removal of this and the uiCompat97to2003 element (§2.15.3.54). This is needed in order to prevent future applications from disabling functionality on the resulting 'upgraded' document. If an application does not know how to upgrade a document, this element and the uiCompat97to2003 element should be ignored and persisted.
• The removal of all compatibility options (§2.15.3.9) on the document which maintain compatibility with previous word processing applications. The compatibility settings which simply affect a given behavior shall not be turned off.

[Note: The remaining operations which shall be performed as part of upgrading the document are application-defined and outside the scope of this Office Open XML Standard. end note]

[Example: Consider a WordprocessingML document that specifies that it shall automatically be upgraded when it is opened by an application. This requirement would be specified using the following WordprocessingML in the document settings part:

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

The forceUpgrade element's val attribute has a value of true specifying that this document shall be upgraded by any application which supports this operation. end example]

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

<complexType name="CT_Empty"/>

2.15.1.48 formsDesign (Structured Document Tag Placeholder Text Should be Resaved)

This element specifies that the document was last saved while the placeholder text of all structured document tags in this document were being edited. This means that the placeholder text currently displayed in all structured document tags which are displaying the showingPlcHdr element (§2.5.2.38) shall be committed to the corresponding glossary document entry as specified using the docPart element (§2.12.5) when this document is opened, in order to ensure that the most recent placeholder text is stored in the glossary document entry. If the current placeholder text cannot be saved as a glossary document entry, then it should be modified as needed before saving.

If this element is omitted, then the placeholder text in this document should not automatically be resaved when the document is opened.

[Example: Consider a WordprocessingML document that specifies that its placeholder text should be resaved to the glossary document when the file is opened. This requirement would be specified using the following WordprocessingML in the document settings part:

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

The formsDesign element's val attribute has a value of true specifying that this document should be resaved to its glossary document by any application which supports this operation. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.49 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 (§2.15.1.57), bookFoldPrinting (§2.15.1.11), bookFoldRevPrinting (§2.15.1.13), or printTwoOnOne (§2.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 shall 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:

(missing picture pict-2.15.1.49-22)

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

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.50 hdrShapeDefaults (Default Properties for VML Objects in Header and Footer)

This element specifies the default parameters for object using the ' (§6.1) inserted in the header and footer of a WordprocessingML document. The definition and semantics of these parameters is described in the VML - Office Drawing subclause (§6.2) of this Office Open XML Standard.

If this element is omitted, then no default properties are applied to VML objects in the header and footer of this document.

[Example: Consider a WordprocessingML document whose document settings contain the following markup:

<w:hdrShapeDefaults>
  <o:shapedefaults v:ext="edit" spidmax="2050" fillcolor="none [3207]" strokecolor="none [3041]">
    <v:fill color="none [3207]" />
    <v:stroke color="none [3041]" weight="3pt" />
    <v:shadow on="t" type="perspective" color="none [1607]" opacity=".5" offset="1pt" offset2="1pt" />
  </o:shapedefaults>
  <o:shapelayout v:ext="edit">
    <o:idmap v:ext="edit" data="2" />
  </o:shapelayout>
</w:hdrShapeDefaults>

The hdrShapeDefaults element specifies a set of shape defaults which shall be applied to the set of all shapes present in the header and footer of this document. end example]

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

<complexType name="CT_ShapeDefaults">

<choice maxOccurs="unbounded">

<any processContents="lax" namespace="urn:schemas-microsoft-com:office:office" minOccurs="0" maxOccurs="unbounded"/>

</choice>

</complexType>

2.15.1.51 hideGrammaticalErrors (Do Not Display Visual Indication of Grammatical Errors)

This element specifies whether a visual cue should be displayed around run content contained in a WordprocessingML document which has been flagged as a possible grammatical error using the proofErr element (§2.13.8.1) or via the application's own grammar engine.

If this element is not present in a WordprocessingML document, visual cues shall be displayed on content contained in a WordprocessingML document which is considered to contain grammatical errors.

[Example: Consider a WordprocessingML document which should show no visual indication of grammatical errors. This requirement would be specified using the following WordprocessingML:

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

The hideGrammaticalErrors element's val attribute has a value of true specifying the display of any visual indication of grammatical errors shall be suppressed for this document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.52 hideSpellingErrors (Do Not Display Visual Indication of Spelling Errors)

This element specifies whether a visual cue should be displayed around run content contained in a WordprocessingML document which has been flagged as a possible spelling error using the proofErr element (§2.13.8.1) or via the application's own spelling engine.

If this element is not present in a WordprocessingML document, visual cues shall be displayed on content contained in a WordprocessingML document which is considered to contain spelling errors.

[Example: Consider a WordprocessingML document which should show no visual indication of spelling errors. This requirement would be specified using the following WordprocessingML:

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

The hideSpellingErrors element's val attribute has a value of true specifying the display of any visual indication of spelling errors shall be suppressed for this document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.53 hyphenationZone (Hyphenation Zone)

This element specifies the hyphenation zone which shall be used when automatically or manually hyphenating the contents of this document. The hyphenation zone is the amount of whitespace which may be left at the end of a line (or added to justified lines) before hyphenation should be attempted on the next word in the document (in order to reduce the amount of whitespace on the line). A smaller hyphenation zone should reduce the raggedness of the right edge of a given document's body text, as more words will be hyphenated. Conversely, a larger hyphenation zone should increase the raggedness of the right edge of a given document's text, as fewer words will be hyphenated.

If this element is omitted, then a default hyphenation zone of 360 twentieths of a point (0.25") shall be applied when performing hyphenation on this document.

[Example: Consider the images below illustrating a paragraph of text in a WordprocessingML document which was automatically hyphenated with the default hyphenation zone:

If document shall instead be hyphenated using a hyphenation zone of one-half of an inch, that requirement would be specified using the following WordprocessingML in the document settings:

<w:hyphenationZone w:val="720" />

The resulting output would only hyphenate words when the remaining line whitespace was less than half an inch, and would look like the following:

The hyphenationZone element has its val attribute equal to 720, therefore lines in the document are hyphenated when the remaining line spacing is less than 72o twentieths of a point (0.5"), resulting in fewer hyphens. end example]

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

<complexType name="CT_TwipsMeasure">

<attribute name="val" type="ST_TwipsMeasure" use="required"/>

</complexType>

2.15.1.54 ignoreMixedContent (Ignore Mixed Content When Validating Custom XML Markup)

This element specifies that applications should ignore all text content which is not contained within a leaf custom XML markup element when validating the contents of the custom XML markup in this document against one or more attached custom XML schema(s). A leaf element is a custom XML element which has no child custom XML elements (it is a leaf in the custom XML tree).

If this element is omitted, then text content in leaf elements shall not be ignored when validating the custom XML markup against one or more custom XML schema(s).

[Example: Consider a WordprocessingML document which should not have its custom XML content validated even by applications which support this operation. This requirement is specified using the following WordprocessingML in the document settings:

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

The doNotValidateAgainstSchema element's val attribute has a value of true specifying that the custom XML markup in this document shall not be validated. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.55 linkStyles (Automatically Update Styles From Document Template)

This element specifies that styles in the given document shall be updated to match the styles in the attached template specified using the attachedTemplate element (§2.15.1.6) when the document is opened by a hosting application. This setting enables the styles contained in documents with attached templates to stay synchronized with the styles used in the attached template.

If this element is omitted, then styles shall not be updated based on the document template regardless of its availability. If the attached template cannot be located or is not a valid file, then this setting should be silently ignored.

[Example: Consider a WordprocessingML document which should always update its styles with those defined in the document's attached template. This requirement would be specified using the following WordprocessingML in the document settings:

<w:settings>
  <w:linkStyles w:val="true" />
  <w:attachedTemplate r:id="rId10" />
  ...
</w:settings>

The linkStyles element has a val attribute value of true, specifying that applications should attempt to locate the document template referenced by the relationship specified in the attachedTemplate element and update the document's styles with the styles from that template. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.56 listSeparator (List Separator for Field Code Evaluation)

This element specifies the character that shall be interpreted as a list item separator when evaluating the contents of all fields in the current document.

[Rationale: When evaluating field instructions based on the contents of the current document, it is necessary to know the character which shall be treated as the list separator in order to prevent changes to the calculation of the same field instructions based on the current user's locale. This element stores the list separator which shall be used to evaluate fields in the contents of this document, irrespective of the locale of the application loading the file. end rationale]

If this element is omitted, the application shall use the default list separator of its current locale setting to evaluate field instructions. If this element's attribute value is more than a single character, then the document is non-conformant.

[Example: Consider a WordprocessingML document which should use the semicolon character as the list separator for all field instructions. This requirement is specified using the following WordprocessingML in the document settings:

<w:listSeparator w:val=";" />

The listSeparator element's val attribute has a value of ; specifying that the semicolon character shall be interpreted as a list item separator.

For instance, the string 10;20,5 would be interpreted as having two values - 10 and 20,5. If the listSeparator was a comma, the same string would be interpreted as 10;20 and 5. end example]

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

<complexType name="CT_String">

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.57 mirrorMargins (Mirror Page Margins)

This element specifies that the left and right margins defined in the section properties shall be swapped on facing pages.

[Guidance: This setting is generally used when printing on both sides of pages and binding them like a book. end guidance]

[Example: Consider a graphical representation (below) of a three page WordprocessingML document with a left margin of 1" and a right margin of 2".

If the mirrorMargins element is present in the document settings with its val attribute equal to true, as follows:

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

The resulting pages will have mirrored margins as follows (un this representation, the gray rectangles representing the text extents on each page):

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.58 noLineBreaksAfter (Custom Set of Characters Which Cannot End a Line)

This element specifies the set of characters which shall be restricted from ending a line for runs of text which shall be subject to custom line breaking logic using the kinsoku element (§2.3.1.16) when the contents of the document are displayed. This constraint shall only apply to text which has been flagged in the language of this rule via the lang element (§2.3.2.18) or automatic detection methods outside the scope of this Office Open XML Standard.

If this element is omitted, then no custom set of characters shall be used to restrict the characters which may end a line when using the kinsoku element.

[Example: Consider a paragraph of WordprocessingML text displayed as follows, with the dollar symbol $ was flagged as Japanese content using the following WordprocessingML in the run properties:

<w:r>
  <w:rPr>
    <w:lang w:eastAsia="ja-JP" />
  </w:rPr>
  <w:t>$</w:t>
</w:r>

This text is displayed and the resulting first line ends with the dollar sign symbol. If this character shall not be used to end a line, that requirement would be specified as follows in the document settings:

<w:noLineBreaksAfter w:lang="ja-JP" w:val="$" />

The noLineBreaksAfter element's val attribute has a value of ja-JP, specifying that all dollar signs in this document which are marked as Japanese text shall not be allowed to end a line. This means that the dollar sign character must therefore be moved to the next line as it can no longer be the last character on a line:

end example]

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

<complexType name="CT_Kinsoku">

<attribute name="lang" type="ST_Lang" use="required"/>

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.59 noLineBreaksBefore (Custom Set Of Characters Which Cannot Begin A Line)

This element specifies the set of characters which shall be restricted from beginning a new line for runs of text which shall be subject to custom line breaking logic using the kinsoku element (§2.3.1.16) when the contents of the document are displayed. This constraint shall only apply to text which has been flagged in the language of this rule via the lang element (§2.3.2.18) or automatic detection methods outside the scope of this Office Open XML Standard.

If this element is omitted, then no custom set of characters shall be used to restrict the characters which may end a line when using the kinsoku element.

[Example: Consider a paragraph of WordprocessingML text displayed as follows, with the dollar symbol $ was flagged as Korean content using the following WordprocessingML in the run properties:

<w:r>
  <w:rPr>
    <w:lang w:eastAsia="ko-KR" />
  </w:rPr>
  <w:t>$</w:t>
</w:r>

This text is displayed and the resulting second line begins with the dollar sign symbol. If this character shall not be used to begin a line, that requirement would be specified as follows in the document settings:

<w:noLineBreaksBefore w:lang="ko-KR" w:val="$" />

The noLineBreaksBefore element's val attribute has a value of ko-KR, specifying that all dollar signs in this document which are marked as Korean text shall not be allowed to begin a line. This means that the previous word character must therefore be moved to the next line as the dollar sign can no longer be the first character on a line:

end example]

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

<complexType name="CT_Kinsoku">

<attribute name="lang" type="ST_Lang" use="required"/>

<attribute name="val" type="ST_String" use="required"/>

</complexType>

2.15.1.60 noPunctuationKerning (Never Kern Punctuation Characters)

This element specifies that punctuation characters shall not be kerned in the current document when kerning is enabled on a run using the kern element (§2.3.2.17). Kerning refers to a process by which a hosting application shall reduce the spacing of adjacent characters and/or punctuation to improve the visual appearance of text. Well kerned text has a similar amount of blank space between each pair of characters and/or each set of a character and punctuation symbol. When kerning is enabled, Latin text shall always be kerned, and this option shall control whether punctuation characters are also kerned.

If this element is omitted, then punctuation characters shall be kerned when kerning is enabled on a given run.

[Example: Consider a WordprocessingML document that shall not kern punctuation even when kerning is enabled on a given run. This requirement is specified using the following WordprocessingML in the document settings:

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

The noPunctuationKerning element's val attribute has a value of true, specifying that punctuation characters shall not be kerned in this document. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.61 printFormsData (Only Print Form Field Content)

This element specifies that printing the contents of this document shall only print the contents of WordprocessingML form fields defined using the FORMTEXT, FORMCHECKBOX, and FORMDROPDOWN field codes in their current locations on the page - all other document contents shall be suppressed.

[Rationale: This setting is typically used to allow duplication of paper forms in electronic WordprocessingML document form, allowing the resulting online document to be printed into the correct locations on the existing paper form. end rationale]

If this element is omitted, then the contents of the entire document (not just form fields) should be printed according to the normal print settings.

[Example: Consider a WordprocessingML document which has form fields in the top right and bottom left corners of the first page, as follows (with the text box form fields shaded in grey):

If the only content which shall be printed on the page are the form fields' contents, this requirement is specified using the following WordprocessingML in the document settings:

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

The printFormsData element's val attribute as a value of true, specifying that only form field data shall be printed, resulting in output as follows when printed:

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.62 printFractionalCharacterWidth (Print Fractional Character Widths)

This element specifies the contents of this document shall be printed with fractional character widths. Fractional character widths exist when the spacing between characters is not constant (i.e. a proportional font face is used).

[Note: Fractional character widths are generally used in conjunction with large font sizes to prevent characters from running together or having too much space between one another. end note]

[Example: Consider a WordprocessingML document which should be printed using fractional character widths as needed. This requirement is specified using the following WordprocessingML markup in the document settings:

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

The printFractionalCharacterWidth element's val attribute is equal to true, specifying that fractional character widths may be used as necessary. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.63 printPostScriptOverText (Print PostScript Codes With Document Text)

This element specifies that the PostScript codes specified in WordprocessingML documents containing PRINT fields shall be included in foreground (on the same Z-order as text) with the data printed in the contents of a given WordprocessingML document.

[Note: This setting is maintained to ensure compatibility of legacy word processing documents. The PRINT field should not be used in lieu of newer technologies in this Office Open XML Standard. end note]

If this element is omitted, then the contents of PRINT fields shall be printed behind text (i.e. in the background).

[Example: Consider a WordprocessingML document containing PRINT fields whose PostScript code shall be printed in the foreground of the WordprocessingML document. This requirement is specified using the following WordprocessingML in the document settings:

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

The printPostScriptOverText element's val attribute is equal to true specifying that the PostScript codes shall be treated as results for the main text level of the document (i.e. not behind that text). end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.64 printTwoOnOne (Print Two Pages Per Sheet)

This element specifies whether two pages should be printed on one sheet of paper when this document is printed. Specifically, this element specifies that each page displayed for the contents in a given WordprocessingML document should be the page size specified in the section settings divided in half with two top margins originating from the bisector of the page, and bottom margins instantiated at the top and bottom of each page.

If this element is omitted, then pages should be displayed and printed as one per sheet.

[Example: Consider a one section document with a 2,160 twentieths of a point (one and a half inch) top margin, and 1,440 twentieths of a point (one inch) bottom, right, and left margins surrounding the document editing canvas (represented by the gray shaded area in diagrams below). This page setup is represented in WordprocessingML using the following fragment:

<w:pgMar w:top="2160" w:right="1440" w:bottom="1440" w:left="1440" />

The resulting printed pages would appear as follows:

If a document should be displayed and printed as though two pages were printed on a single sheeting, this requirement would be specified using the following WordprocessingML:

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

The printTwoOnOne element's val attribute is equal to true specifying that pages should be printed two to a sheet, resulting in the following printout given these page margins:

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.65 proofState (Spelling and Grammatical Checking State)

This element specifies if the grammar and spell checking engines of the last application to process this document completed checking the grammar and spelling of a the document before the document was last saved. Applications which modify the document contents without checking spelling or grammar should reset these states as needed.

[Note: If this element specifies that an application's grammar and spell checking engines completed checking the grammar and spelling of the document when the document was last saved, then subsequent applications may elect to not run their grammar and spell checking engines when the given WordprocessingML document is loaded.

This may increase the speed with which the hosting application loads the file, and does not compromise the state of the grammar or spell checking of the document, as all errors have already been found and flagged with the proofErr element (§2.13.8.1) as the document has not been edited, only loaded, since it was last saved. end note]

[Example: Consider a WordprocessingML document that is saved by a hosting application whose spelling and grammar checking engines have completed checking grammar and spelling in the given WordprocessingML document. This state is specified using the following WordprocessingML in the document settings:

<w:proofState w:spelling="clean" w:grammar="clean" />

The proofState element's attributes spelling and grammar attribute both have the value clean specifying that the hosting application's grammar and spell checking engines completed checking both the grammar and spelling of the given document when it was last saved. end example]

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

<complexType name="CT_Proof">

<attribute name="spelling" type="ST_Proof" use="optional"/>

<attribute name="grammar" type="ST_Proof" use="optional"/>

</complexType>

2.15.1.66 readModeInkLockDown (Freeze Document Layout)

This element specifies the exact set of page and text sizing parameters which shall be used to display the contents of a WordprocessingML document. [Rationale: This setting is typically used for documents that have been annotated using ink. This setting freezes the document's presentation such that the ink annotations shall exist at the same position of the WordprocessingML document irrespective of the monitor on which the WordprocessingML document is rendered. end rationale]

This element shall only affect the display of WordprocessingML documents as follows:

• When the actualPage attribute is specified with a value of true, the given WordprocessingML document's pages shall be rendered as they would normally be displayed. The resulting pages may have their magnification setting changed as desired. All other attributes shall be ignored.
• When the actualPage attribute is specified with a value of false, the given WordprocessingML document's pages shall be rendered as virtual pages when loaded by a conforming hosting application irrespective of the given WordprocessingML document's view (§2.15.1.93). Virtual pages are pages with no correlation with the printed layout of a given WordprocessingML document that have been scaled by a conforming hosting application to improve the readability of a given WordprocessingML document when it is displayed. Specifically, the w and h attributes specify the width and height of the virtual pages, and the fontSz attribute specifies the scaling to be applied to text within the given WordprocessingML document.

[Example: Consider a WordprocessingML document that shall be displayed using virtual pages when its contents are displayed. This state is specified using the following WordprocessingML in the document settings:

<w:readModeInkLockDown w:w="692" w:h="986" w:fontSz="95" w:actualPg="0"/> 

The readModeInkLockDown element has w and h attribute values which specify the width and height of the virtual pages to be used to render the given WordprocessingML document. Finally, the fontSz attribute specifies the scaling to be applied to text within the given WordprocessingML document. end example]

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

<complexType name="CT_ReadingModeInkLockDown">

<attribute name="actualPg" type="ST_OnOff" use="required"/>

<attribute name="w" type="ST_PixelsMeasure" use="required"/>

<attribute name="h" type="ST_PixelsMeasure" use="required"/>

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

</complexType>

2.15.1.67 removeDateAndTime (Remove Date and Time from Annotations)

This element specifies that the date and time information shall be removed from all annotations which are present in the current document when it is saved. Annotations store this information in the date attribute on the annotation's XML element.

If this element is omitted, then date information shall not be removed when the document is saved. If the removePersonalInformation element is not turned on, then this setting shall be ignored.

[Example: Consider a WordprocessingML document that shall not save date and time information on annotations in the document content. This state is specified using the following WordprocessingML in the document settings:

<w:settings>
  ...
  <w:removePersonalInformation w:val="true" />
  <w:removeDateAndTime w:val="true" />
  ...
</w:settings>

The removeDateAndTime element's val attribute has a value of true specifying that all annotations in the document shall have and date and time information removed before they are saved by omitting their date attributes. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.68 removePersonalInformation (Remove Personal Information from Document Properties)

This element specifies that hosting applications shall remove all personal information of document authors upon saving a given WordprocessingML document. The definition and extent of personal information is not defined by this Office Open XML Standard.

If this element is omitted, then personal information shall not be removed when the document is saved.

[Example: Consider a WordprocessingML document that shall not save personal information in the document. This state is specified using the following WordprocessingML in the document settings:

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

The removePersonalInformation element's val attribute has a value of true specifying that applications shall remove any personal information when saving this file. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.69 revisionView (Visibility of Annotation Types)

This element specifies which forms of annotations shall be visible for a WordprocessingML document when it is displayed. This setting shall not affect whether annotations are added or persisted, it shall only affect the display of the annotations which exist in the document's contents (persisted or in memory).

If this element is omitted, then all forms of annotations shall be visible.

[Example: Consider the WordprocessingML below specifying that only formatting and ink annotations within a given WordprocessingML document shall be displayed when the document is opened:

<w:revisionView w:markup="false" w:comments="false" w:insDel="false" />

The revisionView element specifies that the visibility of the markup region, comments and content additions/deletions shall be suppressed by setting a value of false. Since the formatting and inkAnnotation attributes are omitted, they inherit the default of true and shall be displayed. end example]

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

<complexType name="CT_TrackChangesView">

<attribute name="markup" type="ST_OnOff" use="optional"/>

<attribute name="comments" type="ST_OnOff" use="optional"/>

<attribute name="insDel" type="ST_OnOff" use="optional"/>

<attribute name="formatting" type="ST_OnOff" use="optional"/>

<attribute name="inkAnnotations" type="ST_OnOff" use="optional"/>

</complexType>

2.15.1.70 rsid (Single Session Revision Save ID)

This element specifies the revision save ID that was associated with a single editing session for a document. An editing session is a span of time that begins and ends with any event that produces an editable file, such as a save or an e-mail send, and contains no such event. When revision save IDs are added to a document, they shall follow these rules:

• Every editing session shall be assigned a revision save ID that is larger than all earlier ones in the same file
• Revision save IDs should be randomly generated based on the current time (to minimize the chance that two disparate editing sessions starting with the same immediate predecessor are assigned the same revision save ID)
• Changes to document content in an editing session shall be stamped with the current revision save ID using the appropriate rsid* attributes
• An identical rsid value between two documents with the same rsidRoot (§2.15.1.71) shall indicate the same editing sessions

[Note: A revision save ID should be treated as unique within the context of all documents with the same rsidRoot value. Although in practice it is possible for two independent sessions to result in the same value, this outcome is extremely rare as the values are based on the current time. However, the meaning of two revision save IDs is not defined for documents with a different rsidRoot. Applications may use this information as desired. end note]

[Example: Consider the following fragments from two WordprocessingML documents' document settings:

The rsid elements are identical for the first three editing sessions for both documents, indicating that these documents, although they are now separate, originated from the same document. The documents were then separated and the first was saved once afterwards; and the second, twice. end example]

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

<complexType name="CT_LongHexNumber">

<attribute name="val" type="ST_LongHexNumber" use="required"/>

</complexType>

2.15.1.71 rsidRoot (Original Document Revision Save ID)

This element specifies the revision save ID which was associated with the first editing session for this document. [Note: This information shall be identical between any number of copies of the same document, as they all originate from the same original editing session. Applications may use this information as desired. end note]

If this element is omitted, then the original document revision save ID is unknown.

[Example: Consider the following fragments from two WordprocessingML documents' document settings:

The rsidRoot element's val attribute has a value of 00464813 for both documents, indicating that these documents, although they are now separate, originated from the same document. This information may be used as desired. end example]

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

<complexType name="CT_LongHexNumber">

<attribute name="val" type="ST_LongHexNumber" use="required"/>

</complexType>

2.15.1.72 rsids (Listing of All Revision Save ID Values)

This element specifies the set of revision save ID values for the current document. Revision save ID values refer to four digit hexadecimal values which uniquely identify an editing session in the life of the current document. An editing session is the period of time between two subsequent save operations by an application.

[Guidance: The set of revision save IDs stored with a document only supplies information about the editing session in which document components were last saved, which may be used by applications in any manner desired. end guidance]

If this element is omitted, then no information is available about the set of revision save ID values for this document.

[Example: Consider a WordprocessingML document with the following information present in its document settings:

<w:rsids>
  <w:rsidRoot w:val="00464813" />
  <w:rsid w:val="00455AAB" />
  <w:rsid w:val="00464813" />
  <w:rsid w:val="00473403" />
</w:rsids>

The rsids element contains four child elements, specifying that the document was edited over four distinct editing sessions (i.e. it was saved three times). end example]

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

<complexType name="CT_DocRsids">

<sequence>

<element name="rsidRoot" type="CT_LongHexNumber" minOccurs="0" maxOccurs="1"/>

<element name="rsid" type="CT_LongHexNumber" minOccurs="0" maxOccurs="unbounded"/>

</sequence>

</complexType>

2.15.1.73 saveFormsData (Only Save Form Field Content)

This element specifies that saving the contents of this document shall only save the contents of WordprocessingML form fields defined using the FORMTEXT, FORMCHECKBOX, and FORMDROPDOWN field codes in a comma-delimited text format which does not conform to this Office Open XML Standard (i.e. it is a one-way export from a WordprocessingML document).

[Rationale: This setting is typically used to allow duplication of paper forms in electronic WordprocessingML document form, allowing the resulting content to be extracted as a comma-delimited text file. end rationale]

If this element is omitted, then the contents of the entire document (not just form fields) should be saved according to the definition of WordprocessingML in this Office Open XML Standard.

[Example: Consider a WordprocessingML document which has form fields in the top right and bottom left corners of the first page, as follows (with the text box form fields shaded in grey):

If the only content which shall be saved are the form fields' contents, this requirement is specified using the following WordprocessingML in the document settings:

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

The saveFormsData element's val attribute as a value of true, specifying that only form field data shall be saved, resulting in output as follows in a text file:

one,two

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.74 saveInvalidXml (Allow Saving Document As XML File When Custom XML Markup Is Invalid)

This element specifies that this document should be capable of being saved into a format consisting of a single XML file (not defined by this Office Open XML Standard) when its contents are invalid based on the custom XML markup contained in the document. This setting has no effect on documents that do not contain custom XML markup, or that do contain custom XML markup but do not have a schema attached. [Guidance: Because this setting specifies behavior when saving to an alternative file format not defined by this Office Open XML Standard, this behavior is optional. end guidance]

If this element is omitted, then applications should not allow this document to be saved into a single XML file when its contents are invalid based on the custom XML markup contained in the document. If the doNotValidateAgainstSchema element (§2.15.1.42) is set, then the XML is never "invalid" and this property is ignored.

[Example: Consider a WordprocessingML document which should be saved into a single XML file even when its custom XML content is marked invalid by applications which support this operation. This requirement is specified using the following WordprocessingML in the document settings:

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

The saveInvalidXml element's val attribute has a value of true specifying that the content in this document can be saved regardless of its validation status. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.75 savePreviewPicture (Generate Thumbnail For Document On Save)

This element specifies if a document's Thumbnail part should be generated for the contents of the first page of this document when saved by application which support document thumbnail generation.

If this element is omitted, then applications may choose to save a thumbnail, however, that behavior is not required. If this element is specified, a thumbnail must be produced if that functionality is supported.

[Example: Consider a WordprocessingML document that specifies that a document thumbnail shall always be created when it is saved. This requirement would be specified using the following WordprocessingML in the document settings part:

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

The savePreviewPicture element's val attribute has a value of true specifying that a document thumbnail should be generated each time this document is saved. end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.76 saveThroughXslt (Custom XSL Transform To Use When Saving As XML File)

This element specifies the location of a custom XSL transform which shall be used when this document is saved as a single XML file (in a format not defined by this Office Open XML Standard). [Guidance: Because this setting specifies behavior when saving to an alternative file format not defined by this Office Open XML Standard, this behavior is optional. end guidance]

If this element is omitted, then no custom XSL transform shall be used when saving this file as a single XML file. If the useXSLTWhenSaving element (§2.15.1.92) is omitted or set to false, then this transform shall not be applied when the document is saved as a single XML file.

[Example: Consider a XML document that shall have the XSL transform applied when the document is saved as a single XML file. This requirement would be specified using the following WordprocessingML in the document settings:

<w:useXSLTWhenSaving w:val="on"/> 

<w:saveThroughXslt r:id="rId5" />

The useXSLTWhenSaving element's val is set to on indicating that applications shall apply the XSLT specified by the relationship targeted by the id attribute of the saveThroughXslt element, located at rId5, when saving as a single XML file. end example]

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

<complexType name="CT_SaveThroughXslt">

<attribute ref="r:id" use="optional"/>

<attribute name="solutionID" type="ST_String" use="optional"/>

</complexType>

2.15.1.77 saveXmlDataOnly (Only Save Custom XML Markup)

This element specifies that the contents of this document shall be saved as an XML file containing only the custom XML markup in this document in its regular form. The resulting document will not conform to this Office Open XML Standard (i.e. this is an export-only save option for a WordprocessingML document).

[Rationale: This setting is typically used to extract custom XML markup from a WordprocessingML document for further processing by XML-enabled applications. end rationale]

If this element is omitted, then the contents of the entire document (not just custom XML markup) should be saved according to the definition of WordprocessingML in this Office Open XML Standard.

[Example: Consider a WordprocessingML document which should be saved as an XML file containing only its custom XML markup. This requirement is specified using the following WordprocessingML fragment in the document settings:

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

The saveXmlDataOnly element's val attribute has a value of true specifying that only custom XML shall be saved into a regular XML file when saving this document. For example, the document body formerly looked like this:

<w:body>
  <w:p>
    <w:customXml w:element="root" w:namespaceuri="urn:example">
      <w:r>
        <w:t>Hello world<w:t>
      </w:r>
    </w:customXml>
  </w:p>
</w:body>

The presence of this element specifies that the resulting document only contains the custom Xml markup, resulting in the following:

<ns0:root xmlns:ns0="urn:example">Hello world</ns0:root>

end example]

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

<complexType name="CT_OnOff">

<attribute name="val" type="ST_OnOff"/>

</complexType>

2.15.1.78 settings (Document Settings)

This element specifies the settings that are applied to a WordprocessingML document. This element is the root element of the Document Settings part in a WordprocessingML document.

[Example: Consider the following WordprocessingML fragment for the settings part of a document:

<w:settings>
  <w:defaultTabStop w:val="720" />
  <w:characterSpacingControl w:val="dontCompress" />
</w:settings>

The settings element contains all of the settings for this document. In this case, the two settings applied are automatic tab stop increments of 0.5" using the defaultTabStop element, and no character level whitespace compression using the characterSpacingControl element. end example]