Office Open XML

Part 4: Markup Language Reference

December 2006

Table of Contents

Forewordvi

Introductionvii

1.Part Overview1

1.1WordprocessingML Part Summary1

1.2SpreadsheetML Part Summary1

1.3PresentationML Part Summary2

1.4DrawingML Part Summary2

1.5Shared Part Summary3

2.WordprocessingML Reference Material5

2.1Table of Contents5

2.2Main Document Story26

2.3Paragraphs and Rich Formatting33

2.4Tables279

2.5Custom Markup513

2.6Sections594

2.7Styles659

2.8Fonts736

2.9Numbering763

2.10Headers and Footers817

2.11Footnotes and Endnotes833

2.12Glossary Document872

2.13Annotations894

2.14Mail Merge1055

2.15Settings1104

2.16Fields & Hyperlinks1487

2.17Miscellaneous Topics1615

2.18Simple Types1629

3.SpreadsheetML Reference Material1855

3.1Table of Contents1855

3.2Workbook1874

3.3Worksheets1926

3.4Shared String Table2053

3.5Tables2065

3.6Calculation Chain2084

3.7Comments2087

3.8Styles2092

3.9Metadata2213

3.10Pivot Tables2232

3.11Shared Workbook Data2400

3.12QueryTable Data2440

3.13External Data Connections2452

3.14Supplementary Workbook Data2478

3.15Volatile Dependencies2492

3.16Custom XML Mappings2499

3.17Formulas2507

3.18Simple Types2831

4.PresentationML Reference Material2945

4.1Table of Contents2945

4.2Basics2951

4.3Presentation2957

4.4Slides3008

4.5Comments3065

4.6Animation3071

4.7Slide Synchronization Data3163

4.8Simple Types3165

5.DrawingML Reference Material3211

5.1DrawingML - Main3211

5.2DrawingML - Picture3885

5.3DrawingML - Legacy Compatibility3895

5.4DrawingML - Locked Canvas3896

5.5DrawingML - WordprocessingML Drawing3897

5.6DrawingML - SpreadsheetML Drawing3948

5.7DrawingML - Charts3983

5.8DrawingML - Chart Drawings4162

5.9DrawingML - Diagrams4193

6.VML Reference Material4343

6.1VML4343

6.2VML - Office Drawing4753

6.3VML - WordprocessingML Drawing4902

6.4VML - SpreadsheetML Drawing4920

6.5VML - PresentationML Drawing4958

7.Shared MLs Reference Material4961

7.1Math4961

7.2Extended Properties5103

7.3Custom Properties5113

7.4Variant Types5117

7.5Custom XML Data Properties5139

7.6Bibliography5144

7.7Additional Characteristics5192

7.8Office Document Relationships5196

8.Custom XML Schema References5199

8.1Table of Contents5199

8.2Elements5199

Annex A.Office Schemas – XML Schema5203

Annex B.Schemas – RELAX NG5204

Annex C.Additional Syntax Constraints5205

Annex D.Predefined SpreadsheetML Style Definitions5206

Annex E.Example Predefined DrawingML Shape and Text Geometries5207

Annex F.Root Element Locations5208

F.1Grouped by Part Name5208

F.2Grouped by Schema Name5210

Foreword

This multi-part Standard deals with Office Open XML Format-related technology, and consists of the following parts:

Part 1: "Fundamentals"

Part 2: "Open Packaging Conventions"

Part 3: "Primer"

Part 4: "Markup Language Reference" (this document)

Part 5: "Markup Compatibility and Extensibility"

This part, Part 4, includes a number of annexes that refer to data files provided in electronic form only.

Introduction

This Part is one piece of a Standard that describes a family of XML schemas, collectively called Office Open XML, which define the XML vocabularies for word-processing, spreadsheet, and presentation documents, as well as the packaging of documents that conform to these schemas.

The goal is to enable the implementation of the Office Open XML formats by the widest set of tools and platforms, fostering interoperability across office productivity applications and line-of-business systems, as well as to support and strengthen document archival and preservation, all in a way that is fully compatible with the large existing investments in Microsoft Office documents.

Part Overview

This clause is informative.

For convenience, the following subclauses specify the root elements for each part. Full discussion of the use of each part can be found in Part 1 of this Office Open XML Standard.

WordprocessingML Part Summary

Part

Root Element

Ref.

Alternative Format Import

Not applicable

n/a

Comments

comments

§2.13.4.6

Document Settings

settings

§2.15.1.78

Endnotes

endnotes

§2.11.8

Font Table

fonts

§2.8.2.11

Footer

ftr

§2.10.3

Footnotes

footnotes

§2.11.15

Glossary Document

glossaryDocument

§2.12.10

Header

hdr

§2.10.4

Mail Merge Recipient Data

recipients

§2.14.29

Main Document

document

§2.2.3

Numbering Definitions

numbering

§2.9.17

Style Definitions

styles

§2.7.3.18

Web Settings

webSettings

§2.15.2.44

SpreadsheetML Part Summary

Part

Root Element

Ref.

Calculation Chain

calcChain

§3.6.2

Chartsheet

chartsheet

§3.3.1.11

Comments

comments

§3.7.5

Connections

connections

§3.13.2

Custom Property

Not applicable

n/a

Custom XML Mappings

mapInfo

§3.16.3

Dialogsheet

dialogSheet

§3.3.1.32

Drawing

wsDr

§5.6.2.34

External Workbook References

externalLink

§3.14.8

Metadata

metadata

§3.9.8

Pivot Table

pivotTableDefinition

§3.10.1.73

Pivot Table Cache Definition

pivotCacheDefinition

§3.10.1.67

Pivot Table Cache Records

pivotCacheRecords

§3.10.1.68

Query Table

queryTable

§3.12.2

Shared String Table

sst

§3.4.9

Shared Workbook Revision Headers

headers

§3.11.1.1

Shared Workbook Revision Log

revisions

§3.11.1.16

Shared Workbook User Data

users

§3.11.2.2

Single Cell Table Definitions

singleCells

§3.5.2.2

Styles

styleSheet

§3.8.39

Table Definition

table

§3.5.1.2

Volatile Dependencies

volTypes

§3.15.6

Workbook

workbook

§3.2.27

Worksheet

worksheet

§3.3.1.96

PresentationML Part Summary

Part

Root Element

Ref.

Comment Authors

cmAuthorLst

§4.5.3

Comments

cmLst

§4.5.4

Handout Master

handoutMaster

§4.4.1.21

Notes Master

notesMaster

§4.4.1.24

Notes Slide

notes

§4.4.1.23

Presentation

presentation

§4.3.1.24

Presentation Properties

presentationPr

§4.3.1.25

Slide

sld

§4.4.1.35

Slide Layout

sldLayout

§4.4.1.36

Slide Master

sldMaster

§4.4.1.39

Slide Synchronization Data

sldSyncPr

§4.7.1

User-Defined Tags

tagLst

§4.4.3.2

View Properties

viewPr

§4.3.2.18

DrawingML Part Summary

Part

Root Element

Ref.

Chart

chartSpace

§5.7.2.29

Chart Drawing

userShapes

§5.7.2.221

Diagram Colors

colorsDef

§5.9.4.3

Diagram Data

dataModel

§5.9.2.10

Diagram Layout Definition

layoutDef

§5.9.2.16

Diagram Style

styleDef

§5.9.5.7

Theme

officeStyleSheet

§5.1.8.9

Theme Override

themeOverride

§5.1.8.12

Table Styles

tblStyleLst

§5.1.4.2.27

Shared Part Summary

Part

Root Element

Ref.

Additional Characteristics

additionalCharacteristics

§7.7.2.1

Audio

Not applicable

n/a

Bibliography

Sources

§7.6.2.60

Custom XML Data Storage

Not applicable

n/a

Custom XML Data Storage Properties

datastoreItem

§7.5.2.1

Digital Signature Origin

Not applicable

n/a

Digital Signature XML Signature

Signature

Defined in Part 2

Embedded Control Persistence

Not applicable

n/a

Embedded Object

Not applicable

n/a

Embedded Package

Not applicable

n/a

File Properties, Core

coreProperties

Defined in Part 2

File Properties, Custom

Properties

§7.3.2.1

File Properties, Extended

Properties

§7.2.2.21

Font

Not applicable

n/a

Image

Not applicable

n/a

Printer Settings

Not applicable

n/a

Thumbnail

Not applicable

n/a

Video

Not applicable

n/a

End of informative text.

WordprocessingML Reference Material

The subordinate subclauses specify the semantics for the XML markup comprising a WordprocessingML document, as defined by Part 1 of this Standard.

Table of Contents

This subclause is informative.

2.2Main Document Story26

2.2.1background (Document Background)27

2.2.2body (Document Body)31

2.2.3document (Document)33

2.3Paragraphs and Rich Formatting33

2.3.1Paragraphs34

2.3.1.1adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)34

2.3.1.2autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)36

2.3.1.3autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)37

2.3.1.4bar (Paragraph Border Between Facing Pages)38

2.3.1.5between (Paragraph Border Between Identical Paragraphs)44

2.3.1.6bidi (Right to Left Paragraph Layout)51

2.3.1.7bottom (Paragraph Border Between Identical Paragraphs)52

2.3.1.8cnfStyle (Paragraph Conditional Formatting)59

2.3.1.9contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)61

2.3.1.10divId (Associated HTML div ID)63

2.3.1.11framePr (Text Frame Properties)64

2.3.1.12ind (Paragraph Indentation)75

2.3.1.13jc (Paragraph Alignment)81

2.3.1.14keepLines (Keep All Lines On One Page)82

2.3.1.15keepNext (Keep Paragraph With Next Paragraph)83

2.3.1.16kinsoku (Use East Asian Typography Rules for First and Last Character per Line)85

2.3.1.17left (Left Paragraph Border)87

2.3.1.18mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)94

2.3.1.19numPr (Numbering Definition Instance Reference)95

2.3.1.20outlineLvl (Associated Outline Level)96

2.3.1.21overflowPunct (Allow Punctuation to Extent Past Text Extents)97

2.3.1.22p (Paragraph)99

2.3.1.23pageBreakBefore (Start Paragraph on Next Page)102

2.3.1.24pBdr (Paragraph Borders)104

2.3.1.25pPr (Previous Paragraph Properties)105

2.3.1.26pPr (Paragraph Properties)108

2.3.1.27pStyle (Referenced Paragraph Style)110

2.3.1.28right (Right Paragraph Border)112

2.3.1.29rPr (Run Properties for the Paragraph Mark)119

2.3.1.30rPr (Previous Run Properties for the Paragraph Mark)121

2.3.1.31shd (Paragraph Shading)123

2.3.1.32snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)131

2.3.1.33spacing (Spacing Between Lines and Above/Below Paragraph)132

2.3.1.34suppressAutoHyphens (Suppress Hyphenation for Paragraph)138

2.3.1.35suppressLineNumbers (Suppress Line Numbers for Paragraph)139

2.3.1.36suppressOverlap (Prevent Text Frames From Overlapping)140

2.3.1.37tab (Custom Tab Stop)141

2.3.1.38tabs (Set of Custom Tab Stops)143

2.3.1.39textAlignment (Vertical Character Alignment on Line)144

2.3.1.40textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)145

2.3.1.41textDirection (Paragraph Text Flow Direction)147

2.3.1.42top (Paragraph Border Above Identical Paragraphs)148

2.3.1.43topLinePunct (Compress Punctuation at Start of a Line)155

2.3.1.44widowControl (Allow First/Last Line to Display on a Separate Page)156

2.3.1.45wordWrap (Allow Line Breaking At Character Level)158

2.3.2Run159

2.3.2.1b (Bold)160

2.3.2.2bCs (Complex Script Bold)161

2.3.2.3bdr (Text Border)162

2.3.2.4caps (Display All Characters As Capital Letters)169

2.3.2.5color (Run Content Color)170

2.3.2.6cs (Use Complex Script Formatting on Run)173

2.3.2.7dstrike (Double Strikethrough)174

2.3.2.8eastAsianLayout (East Asian Typography Settings)175

2.3.2.9effect (Animated Text Effect)180

2.3.2.10em (Emphasis Mark)181

2.3.2.11emboss (Embossing)182

2.3.2.12fitText (Manual Run Width)183

2.3.2.13highlight (Text Highlighting)185

2.3.2.14i (Italics)186

2.3.2.15iCs (Complex Script Italics)187

2.3.2.16imprint (Imprinting)188

2.3.2.17kern (Font Kerning)190

2.3.2.18lang (Languages for Run Content)191

2.3.2.19noProof (Do Not Check Spelling or Grammar)194

2.3.2.20oMath (Office Open XML Math)195

2.3.2.21outline (Display Character Outline)196

2.3.2.22position (Vertically Raised or Lowered Text)197

2.3.2.23r (Text Run)199

2.3.2.24rFonts (Run Fonts)201

2.3.2.25rPr (Run Properties)208

2.3.2.26rPr (Previous Run Properties)210

2.3.2.27rStyle (Referenced Character Style)212

2.3.2.28rtl (Right To Left Text)213

2.3.2.29shadow (Shadow)214

2.3.2.30shd (Run Shading)216

2.3.2.31smallCaps (Small Caps)223

2.3.2.32snapToGrid (Use Document Grid Settings For Inter-Character Spacing)225

2.3.2.33spacing (Character Spacing Adjustment)226

2.3.2.34specVanish (Paragraph Mark Is Always Hidden)227

2.3.2.35strike (Single Strikethrough)228

2.3.2.36sz (Font Size)229

2.3.2.37szCs (Complex Script Font Size)231

2.3.2.38u (Underline)232

2.3.2.39vanish (Hidden Text)236

2.3.2.40vertAlign (Subscript/Superscript Text)237

2.3.2.41w (Expanded/Compressed Text)238

2.3.2.42webHidden (Web Hidden Text)239

2.3.3Run Content240

2.3.3.1br (Break)241

2.3.3.2control (Floating Embedded Control)243

2.3.3.3control (Inline Embedded Control)245

2.3.3.4cr (Carriage Return)247

2.3.3.5dayLong (Date Block - Long Day Format)248

2.3.3.6dayShort (Date Block - Short Day Format)249

2.3.3.7delText (Deleted Text)250

2.3.3.8dirty (Invalidated Field Cache)251

2.3.3.9drawing (DrawingML Object)251

2.3.3.10hps (Phonetic Guide Text Font Size)252

2.3.3.11hpsBaseText (Phonetic Guide Base Text Font Size)253

2.3.3.12hpsRaise (Distance Between Phonetic Guide Text and Phonetic Guide Base Text)255

2.3.3.13lastRenderedPageBreak (Position of Last Calculated Page Break)256

2.3.3.14lid (Language ID for Phonetic Guide)256

2.3.3.15monthLong (Date Block - Long Month Format)257

2.3.3.16monthShort (Date Block - Short Month Format)258

2.3.3.17movie (Embedded Video)259

2.3.3.18noBreakHyphen (Non Breaking Hyphen Character)260

2.3.3.19object (Inline Embedded Object)261

2.3.3.20pgNum (Page Number Block)263

2.3.3.21pict (VML Object)264

2.3.3.22ptab (Absolute Position Tab Character)265

2.3.3.23rt (Phonetic Guide Text)267

2.3.3.24ruby (Phonetic Guide)268

2.3.3.25rubyAlign (Phonetic Guide Text Alignment)270

2.3.3.26rubyBase (Phonetic Guide Base Text)271

2.3.3.27rubyPr (Phonetic Guide Properties)272

2.3.3.28softHyphen (Optional Hyphen Character)273

2.3.3.29sym (Symbol Character)274

2.3.3.30t (Text)276

2.3.3.31tab (Tab Character)277

2.3.3.32yearLong (Date Block - Long Year Format)278

2.3.3.33yearShort (Date Block - Short Year Format)279

2.4Tables279

2.4.1bidiVisual (Visually Right to Left Table)281

2.4.2bottom (Table Cell Bottom Margin Exception)283

2.4.3bottom (Table Cell Bottom Border)284

2.4.4bottom (Table Bottom Border)291

2.4.5bottom (Table Cell Bottom Margin Default)297

2.4.6cantSplit (Table Row Cannot Break Across Pages)299

2.4.7cnfStyle (Table Cell Conditional Formatting)302

2.4.8cnfStyle (Table Row Conditional Formatting)303

2.4.9divId (Associated HTML div ID)305

2.4.10gridAfter (Grid Columns After Last Cell)307

2.4.11gridBefore (Grid Columns Before First Cell)308

2.4.12gridCol (Grid Column Definition)309

2.4.13gridSpan (Grid Columns Spanned by Current Table Cell)311

2.4.14hidden (Hidden Table Row Marker)313

2.4.15hideMark (Ignore End Of Cell Marker In Row Height Calculation)314

2.4.16hMerge (Horizontally Merged Cell)316

2.4.17insideH (Table Inside Horizontal Edges Border)317

2.4.18insideH (Table Cell Inside Horizontal Edges Border)324

2.4.19insideV (Table Cell Inside Vertical Edges Border)330

2.4.20insideV (Table Inside Vertical Edges Border)336

2.4.21jc (Table Alignment Exception)343

2.4.22jc (Table Row Alignment)344

2.4.23jc (Table Alignment)345

2.4.24left (Table Cell Left Border)347

2.4.25left (Table Cell Left Margin Exception)353

2.4.26left (Table Cell Left Margin Default)355

2.4.27left (Table Left Border)357

2.4.28noWrap (Don't Wrap Cell Content)363

2.4.29right (Table Cell Right Margin Default)365

2.4.30right (Table Cell Right Border)366

2.4.31right (Table Cell Right Margin Exception)373

2.4.32right (Table Right Border)375

2.4.33shd (Table Cell Shading)381

2.4.34shd (Table Shading Exception)389

2.4.35shd (Table Shading)396

2.4.36tbl (Table)404

2.4.37tblBorders (Table Borders Exceptions)406

2.4.38tblBorders (Table Borders)408

2.4.39tblCellMar (Table Cell Margin Defaults)410

2.4.40tblCellMar (Table Cell Margin Exceptions)411

2.4.41tblCellSpacing (Table Cell Spacing Exception)413

2.4.42tblCellSpacing (Table Row Cell Spacing)415

2.4.43tblCellSpacing (Table Cell Spacing Default)417

2.4.44tblGrid (Table Grid)419

2.4.45tblGrid (Previous Table Grid)420

2.4.46tblHeader (Repeat Table Row on Every New Page)421

2.4.47tblInd (Table Indent from Leading Margin Exception)423

2.4.48tblInd (Table Indent from Leading Margin)425

2.4.49tblLayout (Table Layout)426

2.4.50tblLayout (Table Layout Exception)427

2.4.51tblLook (Table Style Conditional Formatting Settings)428

2.4.52tblLook (Table Style Conditional Formatting Settings Exception)430

2.4.53tblOverlap (Floating Table Allows Other Tables to Overlap)431

2.4.54tblpPr (Floating Table Positioning)433

2.4.55tblPr (Table Properties)440

2.4.56tblPr (Previous Table Properties)441

2.4.57tblPrEx (Table-Level Property Exceptions)443

2.4.58tblPrEx (Previous Table-Level Property Exceptions)445

2.4.59tblStyle (Referenced Table Style)448

2.4.60tblW (Preferred Table Width Exception)450

2.4.61tblW (Preferred Table Width)452

2.4.62tc (Table Cell)454

2.4.63tcBorders (Table Cell Borders)456

2.4.64tcFitText (Fit Text Within Cell)460

2.4.65tcMar (Single Table Cell Margins)461

2.4.66tcPr (Previous Table Cell Properties)462

2.4.67tcPr (Table Cell Properties)464

2.4.68tcW (Preferred Table Cell Width)465

2.4.69textDirection (Table Cell Text Flow Direction)468

2.4.70tl2br (Table Cell Top Left to Bottom Right Diagonal Border)469

2.4.71top (Table Top Border)475

2.4.72top (Table Cell Top Margin Default)481

2.4.73top (Table Cell Top Margin Exception)483

2.4.74top (Table Cell Top Border)485

2.4.75tr (Table Row)491

2.4.76tr2bl (Table Cell Top Right to Bottom Left Diagonal Border)494

2.4.77trHeight (Table Row Height)501

2.4.78trPr (Table Row Properties)503

2.4.79trPr (Previous Table Row Properties)504

2.4.80vAlign (Table Cell Vertical Alignment)506

2.4.81vMerge (Vertically Merged Cell)507

2.4.82wAfter (Preferred Width After Table Row)510

2.4.83wBefore (Preferred Width Before Table Row)512

2.5Custom Markup513

2.5.1Custom XML and Smart Tags514

2.5.1.1attr (Custom XML Attribute)515

2.5.1.2attr (Smart Tag Property)517

2.5.1.3customXml (Cell-Level Custom XML Element)519

2.5.1.4customXml (Row-Level Custom XML Element)521

2.5.1.5customXml (Inline-Level Custom XML Element)523

2.5.1.6customXml (Block-Level Custom XML Element)526

2.5.1.7customXmlPr (Custom XML Element Properties)528

2.5.1.8placeholder (Custom XML Element Placeholder Text)529

2.5.1.9smartTag (Inline-Level Smart Tag)531

2.5.1.10smartTagPr (Smart Tag Properties)533

2.5.2Structured Document Tags534

2.5.2.1alias (Friendly Name)535

2.5.2.2bibliography (Bibliography Structured Document Tag)537

2.5.2.3calendar (Date Picker Calendar Type)537

2.5.2.4citation (Citation Structured Document Tag)538

2.5.2.5comboBox (Combo Box Structured Document Tag)539

2.5.2.6dataBinding (XML Mapping)541

2.5.2.7date (Date Structured Document Tag)544

2.5.2.8dateFormat (Date Display Mask)545

2.5.2.9docPart (Document Part Reference)547

2.5.2.10docPartCategory (Document Part Category Filter)548

2.5.2.11docPartGallery (Document Part Gallery Filter)550

2.5.2.12docPartList (Document Part Gallery Structured Document Tag)551

2.5.2.13docPartObj (Built-In Document Part Structured Document Tag)552

2.5.2.14docPartUnique (Built-In Document Part)553

2.5.2.15dropDownList (Drop-Down List Structured Document Tag)554

2.5.2.16equation (Equation Structured Document Tag)556

2.5.2.17group (Group Structured Document Tag)557

2.5.2.18id (Unique ID)557

2.5.2.19lid (Date Picker Language ID)558

2.5.2.20listItem (Combo Box List Item)559

2.5.2.21listItem (Drop-Down List Item)561

2.5.2.22lock (Locking Setting)563

2.5.2.23picture (Picture Structured Document Tag)565

2.5.2.24placeholder (Structured Document Tag Placeholder Text)566

2.5.2.25richText (Rich Text Structured Document Tag)566

2.5.2.26rPr (Run Properties For Structured Document Tag Contents)567

2.5.2.27rPr (Structured Document Tag End Character Run Properties)570

2.5.2.28sdt (Cell-Level Structured Document Tag)572

2.5.2.29sdt (Inline-Level Structured Document Tag)573

2.5.2.30sdt (Block-Level Structured Document Tag)574

2.5.2.31sdt (Row-Level Structured Document Tag)575

2.5.2.32sdtContent (Block-Level Structured Document Tag Content)576

2.5.2.33sdtContent (Cell-Level Structured Document Tag Content)578

2.5.2.34sdtContent (Row-Level Structured Document Tag Content)580

2.5.2.35sdtContent (Inline-Level Structured Document Tag Content)582

2.5.2.36sdtEndPr (Structured Document Tag End Character Properties)584

2.5.2.37sdtPr (Structured Document Tag Properties)585

2.5.2.38showingPlcHdr (Current Contents Are Placeholder Text)587

2.5.2.39storeMappedDataAs (Custom XML Data Date Storage Format)589

2.5.2.40tag (Programmatic Tag)590

2.5.2.41temporary (Remove Structured Document Tag When Contents Are Edited)591

2.5.2.42text (Plain Text Structured Document Tag)592

2.6Sections594

2.6.1bidi (Right to Left Section Layout)595

2.6.2bottom (Bottom Border)596

2.6.3col (Single Column Definition)603

2.6.4cols (Column Definitions)604

2.6.5docGrid (Document Grid)607

2.6.6formProt (Only Allow Editing of Form Fields)610

2.6.7left (Left Border)611

2.6.8lnNumType (Line Numbering Settings)618

2.6.9paperSrc (Paper Source Information)620

2.6.10pgBorders (Page Borders)621

2.6.11pgMar (Page Margins)624

2.6.12pgNumType (Page Numbering Settings)629

2.6.13pgSz (Page Size)631

2.6.14printerSettings (Reference to Printer Settings Data)632

2.6.15right (Right Border)634

2.6.16rtlGutter (Gutter on Right Side of Page)640

2.6.17sectPr (Previous Section Properties)642

2.6.18sectPr (Document Final Section Properties)644

2.6.19sectPr (Section Properties)647

2.6.20textDirection (Text Flow Direction)650

2.6.21top (Top Border)651

2.6.22type (Section Type)657

2.6.23vAlign (Vertical Text Alignment on Page)658

2.7Styles659

2.7.1Style Inheritance660

2.7.2Style Hierarchy661

2.7.3General Style Properties662

2.7.3.1aliases (Alternate Style Names)662

2.7.3.2autoRedefine (Automatically Merge User Formatting Into Style Definition)664

2.7.3.3basedOn (Parent Style ID)666

2.7.3.4hidden (Hide Style From User Interface)668

2.7.3.5latentStyles (Latent Style Information)670

2.7.3.6link (Linked Style Reference)674

2.7.3.7locked (Style Cannot Be Applied)675

2.7.3.8lsdException (Latent Style Exception)676

2.7.3.9name (Primary Style Name)680

2.7.3.10next (Style For Next Paragraph)681

2.7.3.11personal (E-Mail Message Text Style)682

2.7.3.12personalCompose (E-Mail Message Composition Style)684

2.7.3.13personalReply (E-Mail Message Reply Style)685

2.7.3.14qFormat (Primary Style)686

2.7.3.15rsid (Revision Identifier for Style Definition)687

2.7.3.16semiHidden (Hide Style From Main User Interface)688

2.7.3.17style (Style Definition)689

2.7.3.18styles (Style Definitions)696

2.7.3.19uiPriority (Optional User Interface Sorting Order)697

2.7.3.20unhideWhenUsed (Remove Semi-Hidden Property When Style Is Used)698

2.7.4Document Defaults699

2.7.4.1docDefaults (Document Default Paragraph and Run Properties)700

2.7.4.2pPr (Paragraph Properties)701

2.7.4.3pPrDefault (Default Paragraph Properties)703

2.7.4.4rPr (Run Properties)704

2.7.4.5rPrDefault (Default Run Properties)706

2.7.5Table Styles707

2.7.5.1pPr (Table Style Conditional Formatting Paragraph Properties)710

2.7.5.2rPr (Table Style Conditional Formatting Run Properties)712

2.7.5.3tblPr (Table Style Conditional Formatting Table Properties)714

2.7.5.4tblPr (Style Table Properties)716

2.7.5.5tblStyleColBandSize (Number of Columns in Column Band)717

2.7.5.6tblStylePr (Style Conditional Table Formatting Properties)718

2.7.5.7tblStyleRowBandSize (Number of Rows in Row Band)721

2.7.5.8tcPr (Style Table Cell Properties)722

2.7.5.9tcPr (Table Style Conditional Formatting Table Cell Properties)723

2.7.5.10trPr (Table Style Conditional Formatting Table Row Properties)725

2.7.5.11trPr (Style Table Row Properties)726

2.7.6Numbering Styles728

2.7.7Paragraph Styles728

2.7.7.1Numbering in Paragraph Styles730

2.7.7.2pPr (Style Paragraph Properties)731

2.7.8Run (Character) Styles733

2.7.8.1rPr (Run Properties)734

2.8Fonts736

2.8.1Font Embedding737

2.8.2Elements738

2.8.2.1altName (Alternate Names for Font)738

2.8.2.2charset (Character Set Supported By Font)739

2.8.2.3embedBold (Bold Style Font Style Embedding)741

2.8.2.4embedBoldItalic (Bold Italic Font Style Embedding)743

2.8.2.5embedItalic (Italic Font Style Embedding)745

2.8.2.6embedRegular (Regular Font Style Embedding)747

2.8.2.7embedSystemFonts (Embed Common System Fonts)749

2.8.2.8embedTrueTypeFonts (Embed TrueType Fonts)750

2.8.2.9family (Font Family)751

2.8.2.10font (Properties for a Single Font)752

2.8.2.11fonts (Font Table Root Element)754

2.8.2.12notTrueType (Raster or Vector Font)755

2.8.2.13panose1 (Pansose-1 Typeface Classification Number)756

2.8.2.14pitch (Font Pitch)757

2.8.2.15saveSubsetFonts (Subset Fonts When Embedding)757

2.8.2.16sig (Supported Unicode Subranges and Code Pages)758

2.9Numbering763

2.9.1abstractNum (Abstract Numbering Definition)765

2.9.2abstractNumId (Abstract Numbering Definition Reference)767

2.9.3ilvl (Numbering Level Reference)768

2.9.4isLgl (Display All Levels Using Arabic Numerals)770

2.9.5legacy (Legacy Numbering Level Properties)772

2.9.6lvl (Numbering Level Override Definition)774

2.9.7lvl (Numbering Level Definition)778

2.9.8lvlJc (Justification)781

2.9.9lvlOverride (Numbering Level Definition Override)782

2.9.10lvlPicBulletId (Picture Numbering Symbol Definition Reference)785

2.9.11lvlRestart (Restart Numbering Level Symbol)786

2.9.12lvlText (Numbering Level Text)789

2.9.13multiLevelType (Abstract Numbering Definition Type)791

2.9.14name (Abstract Numbering Definition Name)792

2.9.15nsid (Abstract Numbering Definition Identifier)793

2.9.16num (Numbering Definition Instance)794

2.9.17numbering (Numbering Definitions)797

2.9.18numFmt (Numbering Format)797

2.9.19numId (Numbering Definition Instance Reference)798

2.9.20numIdMacAtCleanup (Last Reviewed Abstract Numbering Definition)800

2.9.21numPicBullet (Picture Numbering Symbol Definition)801

2.9.22numStyleLink (Numbering Style Reference)802

2.9.23pict (Picture Numbering Symbol Properties)804

2.9.24pPr (Numbering Level Associated Paragraph Properties)805

2.9.25pStyle (Paragraph Style's Associated Numbering Level)807

2.9.26rPr (Numbering Symbol Run Properties)809

2.9.27start (Starting Value)811

2.9.28startOverride (Numbering Level Starting Value Override)812

2.9.29styleLink (Numbering Style Definition)813

2.9.30suff (Content Between Numbering Symbol and Paragraph Text)815

2.9.31tmpl (Numbering Template Code)816

2.10Headers and Footers817

2.10.1evenAndOddHeaders (Different Even/Odd Page Headers and Footers)818

2.10.2footerReference (Footer Reference)819

2.10.3ftr (Footer)822

2.10.4hdr (Header)825

2.10.5headerReference (Header Reference)828

2.10.6titlePg (Different First Page Headers and Footers)832

2.11Footnotes and Endnotes833

2.11.1continuationSeparator (Continuation Separator Mark)834

2.11.2endnote (Endnote Content)835

2.11.3endnote (Special Endnote List)839

2.11.4endnotePr (Document-Wide Endnote Properties)840

2.11.5endnotePr (Section-Wide Endnote Properties)842

2.11.6endnoteRef (Endnote Reference Mark)843

2.11.7endnoteReference (Endnote Reference)845

2.11.8endnotes (Document Endnotes)848

2.11.9footnote (Special Footnote List)849

2.11.10footnote (Footnote Content)851

2.11.11footnotePr (Document-Wide Footnote Properties)854

2.11.12footnotePr (Section-Wide Footnote Properties)855

2.11.13footnoteRef (Footnote Reference Mark)857

2.11.14footnoteReference (Footnote Reference)858

2.11.15footnotes (Document Footnotes)861

2.11.16noEndnote (Suppress Endnotes In Document)861

2.11.17numFmt (Footnote Numbering Format)862

2.11.18numFmt (Endnote Numbering Format)863

2.11.19numRestart (Footnote and Endnote Numbering Restart Location)865

2.11.20numStart (Footnote and Endnote Numbering Starting Value)866

2.11.21pos (Footnote Placement)867

2.11.22pos (Endnote Placement)869

2.11.23separator (Footnote/Endnote Separator Mark)871

2.12Glossary Document872

2.12.1behavior (Entry Insertion Behavior)873

2.12.2behaviors (Entry Insertion Behaviors)876

2.12.3category (Entry Categorization)877

2.12.4description (Description for Entry)878

2.12.5docPart (Glossary Document Entry)879

2.12.6docPartBody (Contents of Glossary Document Entry)880

2.12.7docPartPr (Glossary Document Entry Properties)883

2.12.8docParts (List of Glossary Document Entries)884

2.12.9gallery (Gallery Associated With Entry)885

2.12.10glossaryDocument (Glossary Document Root Element)886

2.12.11guid (Entry ID)887

2.12.12name (Category Associated With Entry)888

2.12.13name (Entry Name)889

2.12.14style (Associated Paragraph Style Name)891

2.12.15type (Entry Type)892

2.12.16types (Entry Types)893

2.13Annotations894

2.13.1Inline Annotations895

2.13.2"Cross Structure" Annotations895

2.13.3Property Annotations896

2.13.4Comments897

2.13.4.1annotationRef (Comment Information Block)899

2.13.4.2comment (Comment Content)899

2.13.4.3commentRangeEnd (Comment Anchor Range End)903

2.13.4.4commentRangeStart (Comment Anchor Range Start)906

2.13.4.5commentReference (Comment Content Reference Mark)908

2.13.4.6comments (Comments Collection)910

2.13.5Revisions911

2.13.5.1cellDel (Table Cell Deletion)912

2.13.5.2cellIns (Table Cell Insertion)915

2.13.5.3cellMerge (Vertically Merged/Split Table Cells)918

2.13.5.4customXmlDelRangeEnd (Custom XML Markup Deletion End)922

2.13.5.5customXmlDelRangeStart (Custom XML Markup Deletion Start)924

2.13.5.6customXmlInsRangeEnd (Custom XML Markup Insertion End)928

2.13.5.7customXmlInsRangeStart (Custom XML Markup Insertion Start)930

2.13.5.8customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)934

2.13.5.9customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)936

2.13.5.10customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)939

2.13.5.11customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)941

2.13.5.12del (Deleted Run Content)944

2.13.5.13del (Deleted Paragraph)948

2.13.5.14del (Deleted Table Row)950

2.13.5.15del (Deleted Math Control Character)953

2.13.5.16ins (Inserted Table Row)955

2.13.5.17ins (Inserted Math Control Character)958

2.13.5.18ins (Inserted Paragraph)960

2.13.5.19ins (Inserted Numbering Properties)962

2.13.5.20ins (Inserted Run Content)965

2.13.5.21moveFrom (Move Source Run Content)968

2.13.5.22moveFrom (Move Source Paragraph)973

2.13.5.23moveFromRangeEnd (Move Source Location Container - End)975

2.13.5.24moveFromRangeStart (Move Source Location Container - Start)978

2.13.5.25moveTo (Move Destination Paragraph)986

2.13.5.26moveTo (Move Destination Run Content)988

2.13.5.27moveToRangeEnd (Move Destination Location Container - End)992

2.13.5.28moveToRangeStart (Move Destination Location Container - Start)995

2.13.5.29numberingChange (Previous Numbering Field Properties)1003

2.13.5.30numberingChange (Previous Paragraph Numbering Properties)1007

2.13.5.31pPrChange (Revision Information for Paragraph Properties)1013

2.13.5.32rPrChange (Revision Information for Run Properties)1015

2.13.5.33rPrChange (Revision Information for Run Properties on the Paragraph Mark)1017

2.13.5.34sectPrChange (Revision Information for Section Properties)1019

2.13.5.35tblGridChange (Revision Information for Table Grid Column Definitions)1021

2.13.5.36tblPrChange (Revision Information for Table Properties)1023

2.13.5.37tblPrExChange (Revision Information for Table-Level Property Exceptions)1025

2.13.5.38tcPrChange (Revision Information for Table Cell Properties)1027

2.13.5.39trPrChange (Revision Information for Table Row Properties)1030

2.13.6Bookmarks1032

2.13.6.1bookmarkEnd (Bookmark End)1033

2.13.6.2bookmarkStart (Bookmark Start)1036

2.13.7Range Permissions1042

2.13.7.1permEnd (Range Permission End)1043

2.13.7.2permStart (Range Permission Start)1046

2.13.8Spelling & Grammar1053

2.13.8.1proofErr (Proofing Error Anchor)1054

2.14Mail Merge1055

2.14.1active (Record Is Included in Mail Merge)1057

2.14.2activeRecord (Record Currently Displayed In Merged Document)1058

2.14.3addressFieldName (Column Containing E-mail Address)1060

2.14.4checkErrors (Mail Merge Error Reporting Setting)1061

2.14.5colDelim (Column Delimiter for Data Source)1062

2.14.6column (Index of Column Containing Unique Values for Record)1063

2.14.7column (Index of Column Being Mapped)1065

2.14.8connectString (Data Source Connection String)1066

2.14.9dataSource (Data Source File Path)1067

2.14.10dataType (Data Source Type)1069

2.14.11destination (Merged Document Destination)1070

2.14.12doNotSuppressBlankLines (Remove Blank Lines from Merged Documents)1071

2.14.13dynamicAddress (Use Country-Based Address Field Ordering)1072

2.14.14fHdr (First Row of Data Source Contains Column Names)1074

2.14.15fieldMapData (External Data Source to Merge Field Mapping)1075

2.14.16headerSource (Header Definition File Path)1076

2.14.17lid (Merge Field Name Language ID)1077

2.14.18linkToQuery (Query Contains Link to External Query File)1078

2.14.19mailAsAttachment (Merged Document To E-Mail Attachment)1079

2.14.20mailMerge (Mail Merge Settings)1080

2.14.21mailSubject (Merged E-mail or Fax Subject Line)1082

2.14.22mainDocumentType (Source Document Type)1084

2.14.23mappedName (Predefined Merge Field Name)1085

2.14.24name (Data Source Name for Column)1086

2.14.25odso (Office Data Source Object Settings)1088

2.14.26query (Query For Data Source Records To Merge)1090

2.14.27recipientData (Reference to Inclusion/Exclusion Data for Data Source)1091

2.14.28recipientData (Data About Single Data Source Record)1093

2.14.29recipients (Inclusion/Exclusion Data for Data Source)1095

2.14.30src (ODSO Data Source File Path)1096

2.14.31table (Data Source Table Name)1097

2.14.32type (Merge Field Mapping)1099

2.14.33type (ODSO Data Source Type)1100

2.14.34udl (UDL Connection String)1100

2.14.35uniqueTag (Unique Value for Record)1102

2.14.36viewMergedData (View Merged Data Within Document)1103

2.15Settings1104

2.15.1Document Settings1105

2.15.1.1activeWritingStyle (Grammar Checking Settings)1105

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

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

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

2.15.1.5attachedSchema (Attached Custom XML Schema)1111

2.15.1.6attachedTemplate (Attached Document Template)1113

2.15.1.7autoCaption (Single Automatic Captioning Setting)1114

2.15.1.8autoCaptions (Automatic Captioning Settings)1116

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

2.15.1.10autoHyphenation (Automatically Hyphenate Document Contents When Displayed)1118

2.15.1.11bookFoldPrinting (Book Fold Printing)1119

2.15.1.12bookFoldPrintingSheets (Number of Pages Per Booklet)1121

2.15.1.13bookFoldRevPrinting (Reverse Book Fold Printing)1123

2.15.1.14bordersDoNotSurroundFooter (Page Border Excludes Footer)1126

2.15.1.15bordersDoNotSurroundHeader (Page Border Excludes Header)1127

2.15.1.16caption (Single Caption Type Definition)1129

2.15.1.17captions (Caption Settings)1138

2.15.1.18characterSpacingControl (Character-Level Whitespace Compression)1140

2.15.1.19clickAndTypeStyle (Paragraph Style Applied to Automatically Generated Paragraphs)1141

2.15.1.20clrSchemeMapping (Theme Color Mappings)1142

2.15.1.21consecutiveHyphenLimit (Maximum Number of Consecutively Hyphenated Lines)1148

2.15.1.22decimalSymbol (Radix Point for Field Code Evaluation)1149

2.15.1.23defaultTableStyle (Default Table Style for Newly Inserted Tables)1150

2.15.1.24defaultTabStop (Distance Between Automatic Tab Stops)1152

2.15.1.25displayBackgroundShape (Display Background Objects When Displaying Document)1153

2.15.1.26displayHorizontalDrawingGridEvery (Distance between Horizontal Gridlines)1155

2.15.1.27displayVerticalDrawingGridEvery (Distance between Vertical Gridlines)1156

2.15.1.28documentProtection (Document Editing Restrictions)1158

2.15.1.29documentType (Document Classification)1172

2.15.1.30docVar (Single Document Variable)1173

2.15.1.31docVars (Document Variables)1175

2.15.1.32doNotAutoCompressPictures (Do Not Automatically Compress Images)1175

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

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

2.15.1.35doNotEmbedSmartTags (Remove Smart Tags When Saving)1179

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

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

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

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

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

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

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

2.15.1.43drawingGridHorizontalOrigin (Drawing Grid Horizontal Origin Point)1190

2.15.1.44drawingGridHorizontalSpacing (Drawing Grid Horizontal Grid Unit Size)1191

2.15.1.45drawingGridVerticalOrigin (Drawing Grid Vertical Origin Point)1193

2.15.1.46drawingGridVerticalSpacing (Drawing Grid Vertical Grid Unit Size)1194

2.15.1.47forceUpgrade (Upgrade Document on Open)1196

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

2.15.1.49gutterAtTop (Position Gutter At Top of Page)1197

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

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

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

2.15.1.53hyphenationZone (Hyphenation Zone)1202

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

2.15.1.55linkStyles (Automatically Update Styles From Document Template)1204

2.15.1.56listSeparator (List Separator for Field Code Evaluation)1205

2.15.1.57mirrorMargins (Mirror Page Margins)1206

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

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

2.15.1.60noPunctuationKerning (Never Kern Punctuation Characters)1211

2.15.1.61printFormsData (Only Print Form Field Content)1212

2.15.1.62printFractionalCharacterWidth (Print Fractional Character Widths)1214

2.15.1.63printPostScriptOverText (Print PostScript Codes With Document Text)1215

2.15.1.64printTwoOnOne (Print Two Pages Per Sheet)1216

2.15.1.65proofState (Spelling and Grammatical Checking State)1219

2.15.1.66readModeInkLockDown (Freeze Document Layout)1220

2.15.1.67removeDateAndTime (Remove Date and Time from Annotations)1223

2.15.1.68removePersonalInformation (Remove Personal Information from Document Properties)1224

2.15.1.69revisionView (Visibility of Annotation Types)1225

2.15.1.70rsid (Single Session Revision Save ID)1227

2.15.1.71rsidRoot (Original Document Revision Save ID)1229

2.15.1.72rsids (Listing of All Revision Save ID Values)1230

2.15.1.73saveFormsData (Only Save Form Field Content)1231

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

2.15.1.75savePreviewPicture (Generate Thumbnail For Document On Save)1233

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

2.15.1.77saveXmlDataOnly (Only Save Custom XML Markup)1236

2.15.1.78settings (Document Settings)1237

2.15.1.79shapeDefaults (Default Properties for VML Objects in Main Document)1244

2.15.1.80showEnvelope (Show E-Mail Message Header)1244

2.15.1.81showXMLTags (Show Visual Indicators for Custom XML Markup Start/End Locations)1245

2.15.1.82smartTagType (Supplementary Smart Tag Information)1246

2.15.1.83strictFirstAndLastChars (Use Strict Kinsoku Rules for Japanese Text)1248

2.15.1.84styleLockQFSet (Prevent Replacement of Styles Part)1249

2.15.1.85styleLockTheme (Prevent Modification of Themes Part)1250

2.15.1.86stylePaneFormatFilter (Suggested Filtering for List of Document Styles)1251

2.15.1.87stylePaneSortMethod (Suggested Sorting for List of Document Styles)1253

2.15.1.88summaryLength (Percentage of Document to Use When Generating Summary)1254

2.15.1.89themeFontLang (Theme Font Languages)1255

2.15.1.90trackRevisions (Track Revisions to Document)1258

2.15.1.91updateFields (Automatically Recalculate Fields on Open)1261

2.15.1.92useXSLTWhenSaving (Save Document as XML File through Custom XSL Transform)1262

2.15.1.93view (Document View Setting)1263

2.15.1.94writeProtection (Write Protection)1264

2.15.1.95zoom (Magnification Setting)1271

2.15.2Web Page Settings1273

2.15.2.1allowPNG (Allow PNG as Graphic Format)1273

2.15.2.2blockQuote (Data for HTML blockquote Element)1275

2.15.2.3bodyDiv (Data for HTML body Element)1276

2.15.2.4bottom (Bottom Border for HTML div)1277

2.15.2.5color (Frameset Splitter Color)1284

2.15.2.6div (Information About Single HTML div Element)1288

2.15.2.7divBdr (Set of Borders for HTML div)1292

2.15.2.8divs (Information about HTML div Elements)1293

2.15.2.9divsChild (Child div Elements Contained within Current div)1295

2.15.2.10doNotOrganizeInFolder (Do Not Place Supporting Files in Subdirectory)1297

2.15.2.11doNotRelyOnCSS (Do Not Rely on CSS for Font Face Formatting)1298

2.15.2.12doNotSaveAsSingleFile (Recommend Web Page Format over Single File Web Page Format)1300

2.15.2.13doNotUseLongFileNames (Do Not Use File Names Longer than 8.3 Characters)1301

2.15.2.14encoding (Output Encoding When Saving as Web Page)1302

2.15.2.15flatBorders (Frameset Splitter Border Style)1303

2.15.2.16frame (Single Frame Properties)1304

2.15.2.17frameLayout (Frameset Layout)1306

2.15.2.18frameset (Root Frameset Definition)1308

2.15.2.19frameset (Nested Frameset Definition)1310

2.15.2.20framesetSplitbar (Frameset Splitter Properties)1312

2.15.2.21left (Left Border for HTML div)1313

2.15.2.22linkedToFile (Maintain Link to Existing File)1320

2.15.2.23marBottom (Bottom Margin for HTML div)1322

2.15.2.24marH (Top and Bottom Margin for Frame)1323

2.15.2.25marLeft (Left Margin for HTML div)1325

2.15.2.26marRight (Right Margin for HTML div)1327

2.15.2.27marTop (Top Margin for HTML div)1328

2.15.2.28marW (Left and Right Margin for Frame)1330

2.15.2.29name (Frame Name)1331

2.15.2.30noBorder (Do Not Display Frameset Splitters)1333

2.15.2.31noResizeAllowed (Frame Cannot Be Resized)1336

2.15.2.32optimizeForBrowser (Disable Features Not Supported by Target Web Browser)1337

2.15.2.33pixelsPerInch (Pixels per Inch for Graphics/Images)1339

2.15.2.34relyOnVML (Utilize VML When Saving as Web Page)1340

2.15.2.35right (Right Border for HTML div)1341

2.15.2.36saveSmartTagsAsXml (Save Smart Tag Data in XML Property Bag)1348

2.15.2.37scrollbar (Scrollbar Display Option)1350

2.15.2.38sourceFileName (Source File for Frame)1351

2.15.2.39sz (Frame Size)1353

2.15.2.40sz (Nested Frameset Size)1355

2.15.2.41targetScreenSz (Target Screen Size for Web Page)1357

2.15.2.42top (Top Border for HTML div)1358

2.15.2.43w (Frameset Splitter Width)1365

2.15.2.44webSettings (Web Page Settings)1366

2.15.3Compatibility Settings1368

2.15.3.1adjustLineHeightInTable (Add Document Grid Line Pitch To Lines in Table Cells)1369

2.15.3.2alignTablesRowByRow (Align Table Rows Independently)1371

2.15.3.3allowSpaceOfSameStyleInTable (Allow Contextual Spacing of Paragraphs in Tables)1372

2.15.3.4applyBreakingRules (Use Legacy Ethiopic and Amharic Line Breaking Rules)1375

2.15.3.5autofitToFirstFixedWidthCell (Allow Table Columns To Exceed Preferred Widths of Constituent Cells)1376

2.15.3.6autoSpaceLikeWord95 (Emulate Word 95 Full-Width Character Spacing)1378

2.15.3.7balanceSingleByteDoubleByteWidth (Balance Single Byte and Double Byte Characters)1379

2.15.3.8cachedColBalance (Use Cached Paragraph Information for Column Balancing)1381

2.15.3.9compat (Compatibility Settings)1382

2.15.3.10convMailMergeEsc (Treat Backslash Quotation Delimiter as Two Quotation Marks)1387

2.15.3.11displayHangulFixedWidth (Always Use Fixed Width for Hangul Characters)1388

2.15.3.12doNotAutofitConstrainedTables (Do Not AutoFit Tables To Fit Next To Wrapped Objects)1390

2.15.3.13doNotBreakConstrainedForcedTable (Don't Break Table Rows Around Floating Tables)1392

2.15.3.14doNotBreakWrappedTables (Do Not Allow Floating Tables To Break Across Pages)1394

2.15.3.15doNotExpandShiftReturn (Don't Justify Lines Ending in Soft Line Break)1396

2.15.3.16doNotLeaveBackslashAlone (Convert Backslash To Yen Sign When Entered)1397

2.15.3.17doNotSnapToGridInCell (Do Not Snap to Document Grid in Table Cells with Objects)1398

2.15.3.18doNotSuppressIndentation (Do Not Ignore Floating Objects When Calculating Paragraph Indentation)1400

2.15.3.19doNotSuppressParagraphBorders (Do Not Suppress Paragraph Borders Next To Frames)1402

2.15.3.20doNotUseEastAsianBreakRules (Do Not Compress Compressible Characters When Using Document Grid)1404

2.15.3.21doNotUseHTMLParagraphAutoSpacing (Use Fixed Paragraph Spacing for HTML Auto Setting)1406

2.15.3.22doNotUseIndentAsNumberingTabStop (Ignore Hanging Indent When Creating Tab Stop After Numbering)1408

2.15.3.23doNotVertAlignCellWithSp (Don't Vertically Align Cells Containing Floating Objects)1410

2.15.3.24doNotVertAlignInTxbx (Ignore Vertical Alignment in Textboxes)1413

2.15.3.25doNotWrapTextWithPunct (Do Not Allow Hanging Punctuation With Character Grid)1415

2.15.3.26footnoteLayoutLikeWW8 (Emulate Word 6.x/95/97 Footnote Placement)1416

2.15.3.27forgetLastTabAlignment (Ignore Width of Last Tab Stop When Aligning Paragraph If It Is Not Left Aligned)1418

2.15.3.28growAutofit (Allow Tables to AutoFit Into Page Margins)1420

2.15.3.29layoutRawTableWidth (Ignore Space Before Table When Deciding If Table Should Wrap Floating Object)1422

2.15.3.30layoutTableRowsApart (Allow Table Rows to Wrap Inline Objects Independently)1424

2.15.3.31lineWrapLikeWord6 (Emulate Word 6.0 Line Wrapping for East Asian Text)1426

2.15.3.32mwSmallCaps (Emulate Word 5.x for the Macintosh Small Caps Formatting)1427

2.15.3.33noColumnBalance (Do Not Balance Text Columns within a Section)1429

2.15.3.34noExtraLineSpacing (Do Not Center Content on Lines With Exact Line Height)1432

2.15.3.35noLeading (Do Not Add Leading Between Lines of Text)1433

2.15.3.36noSpaceRaiseLower (Do Not Increase Line Height for Raised/Lowered Text)1435

2.15.3.37noTabHangInd (Do Not Create Custom Tab Stop for Hanging Indent)1436

2.15.3.38printBodyTextBeforeHeader (Print Body Text before Header/Footer Contents)1439

2.15.3.39printColBlack (Print Colors as Black And White without Dithering)1440

2.15.3.40selectFldWithFirstOrLastChar (Select Field When First or Last Character Is Selected)1441

2.15.3.41shapeLayoutLikeWW8 (Emulate Word 97 Text Wrapping Around Floating Objects)1442

2.15.3.42showBreaksInFrames (Display Page/Column Breaks Present in Frames)1443

2.15.3.43spaceForUL (Add Additional Space Below Baseline For Underlined East Asian Text)1446

2.15.3.44spacingInWholePoints (Only Expand/Condense Text By Whole Points)1448

2.15.3.45splitPgBreakAndParaMark (Always Move Paragraph Mark to Page after a Page Break)1450

2.15.3.46subFontBySize (Increase Priority Of Font Size During Font Substitution)1452

2.15.3.47suppressBottomSpacing (Ignore Exact Line Height for Last Line on Page)1453

2.15.3.48suppressSpacingAtTopOfPage (Ignore Minimum Line Height for First Line on Page)1456

2.15.3.49suppressSpBfAfterPgBrk (Do Not Use Space Before On First Line After a Page Break)1458

2.15.3.50suppressTopSpacing (Ignore Minimum and Exact Line Height for First Line on Page)1460

2.15.3.51suppressTopSpacingWP (Emulate WordPerfect 5.x Line Spacing)1462

2.15.3.52swapBordersFacingPages (Swap Paragraph Borders on Odd Numbered Pages)1464

2.15.3.53truncateFontHeightsLikeWP6 (Emulate WordPerfect 6.x Font Height Calculation)1467

2.15.3.54uiCompat97To2003 (Disable Features Incompatible With Earlier Word Processing Formats)1469

2.15.3.55ulTrailSpace (Underline All Trailing Spaces)1469

2.15.3.56underlineTabInNumList (Underline Following Character Following Numbering)1471

2.15.3.57useAltKinsokuLineBreakRules (Use Alternate Set of East Asian Line Breaking Rules)1472

2.15.3.58useAnsiKerningPairs (Use ANSI Kerning Pairs from Fonts)1474

2.15.3.59useFELayout (Do Not Bypass East Asian/Complex Script Layout Code)1475

2.15.3.60useNormalStyleForList (Do Not Automatically Apply List Paragraph Style To Bulleted/Numbered Text)1476

2.15.3.61usePrinterMetrics (Use Printer Metrics To Display Documents)1478

2.15.3.62useSingleBorderforContiguousCells (Use Simplified Rules For Table Border Conflicts)1479

2.15.3.63useWord2002TableStyleRules (Emulate Word 2002 Table Style Rules)1481

2.15.3.64useWord97LineBreakRules (Emulate Word 97 East Asian Line Breaking)1482

2.15.3.65wpJustification (Emulate WordPerfect 6.x Paragraph Justification)1483

2.15.3.66wpSpaceWidth (Space width)1485

2.15.3.67wrapTrailSpaces (Line Wrap Trailing Spaces)1485

2.16Fields & Hyperlinks1487

2.16.1Syntax1487

2.16.2XML representation1490

2.16.3Formulas and expressions1492

2.16.3.1Constants1493

2.16.3.2Bookmarks1493

2.16.3.3Operators1493

2.16.3.4Functions1494

2.16.3.5Table cell references1495

2.16.4Field formatting1497

2.16.4.1Date and time formatting1497

2.16.4.2Numeric formatting1499

2.16.4.3General formatting1500

2.16.5Field definitions1507

2.16.5.1ADDRESSBLOCK1509

2.16.5.2ADVANCE1509

2.16.5.3ASK1510

2.16.5.4AUTHOR1511

2.16.5.5AUTONUM1512

2.16.5.6AUTONUMLGL1513

2.16.5.7AUTONUMOUT1514

2.16.5.8AUTOTEXT1515

2.16.5.9AUTOTEXTLIST1515

2.16.5.10BARCODE1516

2.16.5.11BIBLIOGRAPHY1517

2.16.5.12BIDIOUTLINE1518

2.16.5.13CITATION1518

2.16.5.14COMMENTS1520

2.16.5.15COMPARE1520

2.16.5.16CREATEDATE1521

2.16.5.17DATABASE1522

2.16.5.18DATE1523

2.16.5.19DOCPROPERTY1524

2.16.5.20DOCVARIABLE1526

2.16.5.21EDITTIME1527

2.16.5.22EQ1527

2.16.5.23FILENAME1531

2.16.5.24FILESIZE1531

2.16.5.25FILLIN1532

2.16.5.26FORMCHECKBOX1533

2.16.5.27FORMDROPDOWN1533

2.16.5.28FORMTEXT1533

2.16.5.29GOTOBUTTON1534

2.16.5.30GREETINGLINE1535

2.16.5.31HYPERLINK1535

2.16.5.32IF1536

2.16.5.33INCLUDEPICTURE1537

2.16.5.34INCLUDETEXT1537

2.16.5.35INDEX1538

2.16.5.36INFO1541

2.16.5.37KEYWORDS1541

2.16.5.38LASTSAVEDBY1542

2.16.5.39LINK1542

2.16.5.40LISTNUM1543

2.16.5.41MACROBUTTON1545

2.16.5.42MERGEFIELD1545

2.16.5.43MERGEREC1546

2.16.5.44MERGESEQ1547

2.16.5.45NEXT1547

2.16.5.46NEXTIF1548

2.16.5.47NOTEREF1548

2.16.5.48NUMCHARS1549

2.16.5.49NUMPAGES1549

2.16.5.50NUMWORDS1550

2.16.5.51PAGE1550

2.16.5.52PAGEREF1551

2.16.5.53PRINT1551

2.16.5.54PRINTDATE1552

2.16.5.55PRIVATE1553

2.16.5.56QUOTE1553

2.16.5.57RD1554

2.16.5.58REF1554

2.16.5.59REVNUM1555

2.16.5.60SAVEDATE1556

2.16.5.61SECTION1557

2.16.5.62SECTIONPAGES1557

2.16.5.63SEQ1558

2.16.5.64SET1559

2.16.5.65SKIPIF1560

2.16.5.66STYLEREF1560

2.16.5.67SUBJECT1562

2.16.5.68SYMBOL1562

2.16.5.69TA1563

2.16.5.70TC1564

2.16.5.71TEMPLATE1565

2.16.5.72TIME1565

2.16.5.73TITLE1566

2.16.5.74TOA1567

2.16.5.75TOC1568

2.16.5.76USERADDRESS1570

2.16.5.77USERINITIALS1570

2.16.5.78USERNAME1571

2.16.5.79XE1571

2.16.6calcOnExit (Recalculate Fields When Current Field Is Modified)1573

2.16.7checkBox (Checkbox Form Field Properties)1574

2.16.8checked (Checkbox Form Field State)1575

2.16.9ddList (Drop-Down List Form Field Properties)1576

2.16.10default (Default Text Box Form Field String)1577

2.16.11default (Default Drop-Down List Item Index)1578

2.16.12default (Default Checkbox Form Field State)1580

2.16.13delInstrText (Deleted Field Code)1581

2.16.14enabled (Form Field Enabled)1582

2.16.15entryMacro (Script Function to Execute on Form Field Entry)1583

2.16.16exitMacro (Script Function to Execute on Form Field Exit)1584

2.16.17ffData (Form Field Properties)1585

2.16.18fldChar (Complex Field Character)1587

2.16.19fldData (Custom Field Data)1590

2.16.20fldData (Custom Field Data)1591

2.16.21fldSimple (Simple Field)1592

2.16.22format (Text Box Form Field Formatting)1595

2.16.23helpText (Associated Help Text)1597

2.16.24hyperlink (Hyperlink)1599

2.16.25instrText (Field Code)1604

2.16.26listEntry (Drop-Down List Entry)1605

2.16.27maxLength (Text Box Form Field Maximum Length)1606

2.16.28name (Form Field Name)1607

2.16.29result (Drop-Down List Selection)1608

2.16.30size (Checkbox Form Field Size)1609

2.16.31sizeAuto (Automatically Size Form Field)1610

2.16.32statusText (Associated Status Text)1612

2.16.33textInput (Text Box Form Field Properties)1613

2.16.34type (Text Box Form Field Type)1614

2.17Miscellaneous Topics1615

2.17.1Text Box Content1615

2.17.1.1txbxContent (Rich Text Box Content Container)1615

2.17.2Subdocuments1618

2.17.2.1subDoc (Anchor for Subdocument Location)1619

2.17.3External Content Import1622

2.17.3.1altChunk (Anchor for Imported External Content)1622

2.17.3.2altChunkPr (External Content Import Properties)1624

2.17.3.3matchSrc (Keep Source Formatting on Import)1625

2.17.4Roundtripping Alternate Content1627

2.18Simple Types1629

2.18.1ST_AlgClass (Cryptographic Algorithm Classes)1629

2.18.2ST_AlgType (Cryptographic Algorithm Types)1629

2.18.3ST_AnnotationVMerge (Table Cell Vertical Merge Revision Type)1630

2.18.4ST_Border (Border Styles)1631

2.18.5ST_BrClear (Line Break Text Wrapping Restart Location)1686

2.18.6ST_BrType (Break Types)1688

2.18.7ST_CalendarType (Calendar Types)1690

2.18.8ST_CaptionPos (Automatic Caption Positioning Values)1691

2.18.9ST_ChapterSep (Chapter Separator Types)1692

2.18.10ST_CharacterSpacing (Character-Level Whitespace Compression Settings)1694

2.18.11ST_Cnf (Conditional Formatting Bitmask)1695

2.18.12ST_ColorSchemeIndex (Theme Color Reference)1696

2.18.13ST_CombineBrackets (Two Lines in One Enclosing Character Type)1698

2.18.14ST_CryptProv (Cryptographic Provider Types)1699

2.18.15ST_DateTime (Standard Date and Time Storage Format)1700

2.18.16ST_DecimalNumber (Decimal Number Value)1701

2.18.17ST_DisplacedByCustomXml (Location of Custom XML Markup Displacing an Annotation)1702

2.18.18ST_DocGrid (Document Grid Types)1704

2.18.19ST_DocPartBehavior (Insertion Behavior Types)1706

2.18.20ST_DocPartGallery (Entry Gallery Types)1707

2.18.21ST_DocPartType (Entry Types)1711

2.18.22ST_DocProtect (Document Protection Types)1713

2.18.23ST_DocType (Document Classification Values)1714

2.18.24ST_DropCap (Text Frame Drop Cap Location)1715

2.18.25ST_EdGrp (Range Permision Editing Group)1716

2.18.26ST_EdnPos (Endnote Positioning Location)1718

2.18.27ST_EighthPointMeasure (Measurement in Eighths of a Point)1718

2.18.28ST_Em (Emphasis Mark Type)1719

2.18.29ST_FFHelpTextVal (Help Text Value)1720

2.18.30ST_FFName (Form Field Name Value)1721

2.18.31ST_FFStatusTextVal (Status Text Value)1722

2.18.32ST_FFTextType (Text Box Form Field Type Values)1723

2.18.33ST_FldCharType (Complex Field Character Type)1724

2.18.34ST_FontFamily (Font Family Value)1725

2.18.35ST_FrameLayout (Frameset Layout Order)1726

2.18.36ST_FrameScrollbar (Frame Scrollbar Visibility)1727

2.18.37ST_FtnEdn (Footnote or Endnote Type)1729

2.18.38ST_FtnPos (Footnote Positioning Location)1731

2.18.39ST_Guid (128-Bit GUID)1732

2.18.40ST_HAnchor (Horizontal Anchor Location)1733

2.18.41ST_HdrFtr (Header or Footer Type)1734

2.18.42ST_HeightRule (Height Rule)1735

2.18.43ST_HexColor (Color Value)1736

2.18.44ST_HexColorAuto (‘Automatic’ Color Value)1737

2.18.45ST_HexColorRGB (Hexadecimal Color Value)1737

2.18.46ST_HighlightColor (Text Highlight Colors)1738

2.18.47ST_Hint (Font Type Hint)1741

2.18.48ST_HpsMeasure (Measurement in Half-Points)1742

2.18.49ST_InfoTextType (Help or Status Text Type)1743

2.18.50ST_Jc (Horizontal Alignment Type)1743

2.18.51ST_Lang (Language Reference)1747

2.18.52ST_LangCode (Two Digit Hexadecimal Language Code)1748

2.18.53ST_LevelSuffix (Content Between Numbering Symbol and Paragraph Text)1755

2.18.54ST_LineNumberRestart (Line Numbering Restart Position)1756

2.18.55ST_LineSpacingRule (Line Spacing Rule)1757

2.18.56ST_Lock (Locking Types)1758

2.18.57ST_LongHexNumber (Four Digit Hexadecimal Number Value)1759

2.18.58ST_MacroName (Script Subroutine Name Value)1760

2.18.59ST_MailMergeDataType (Mail Merge Data Source Type Values)1761

2.18.60ST_MailMergeDest (Merged Document Destination Types)1762

2.18.61ST_MailMergeDocType (Source Document Types)1763

2.18.62ST_MailMergeOdsoFMDFieldType (Merge Field Mapping Types)1764

2.18.63ST_MailMergeSourceType (Mail Merge ODSO Data Source Types)1765

2.18.64ST_Merge (Merged Cell Type)1767

2.18.65ST_MultiLevelType (Numbering Definition Type)1770

2.18.66ST_NumberFormat (Numbering Format)1771

2.18.67ST_OnOff (On/Off Value)1779

2.18.68ST_PageBorderDisplay (Page Border Display Options)1782

2.18.69ST_PageBorderOffset (Page Border Positioning Base)1783

2.18.70ST_PageBorderZOrder (Page Border Z-Order)1784

2.18.71ST_PageOrientation (Page Orientation)1785

2.18.72ST_Panose (Panose-1 Number)1786

2.18.73ST_Pitch (Font Pitch Value)1787

2.18.74ST_PixelsMeasure (Measurement in Pixels)1787

2.18.75ST_PointMeasure (Measurement in Points)1788

2.18.76ST_Proof (Proofing State Values)1788

2.18.77ST_ProofErr (Proofing Error Type)1789

2.18.78ST_PTabAlignment (Absolute Position Tab Alignment)1791

2.18.79ST_PTabLeader (Absolute Position Tab Leader Character)1792

2.18.80ST_PTabRelativeTo (Absolute Position Tab Positioning Base)1793

2.18.81ST_RestartNumber (Footnote/Endnote Numbering Restart Locations)1794

2.18.82ST_RubyAlign (Phonetic Guide Text Alignment)1795

2.18.83ST_SdtDateMappingType (Date Storage Format Types)1798

2.18.84ST_SectionMark (Section Type)1799

2.18.85ST_Shd (Shading Patterns)1800

2.18.86ST_ShortHexNumber (Two Digit Hexadecimal Number Value)1808

2.18.87ST_SignedHpsMeasure (Signed Measurement in Half-Points)1809

2.18.88ST_SignedTwipsMeasure (Signed Measurement in Twentieths of a Point)1809

2.18.89ST_String (String)1810

2.18.90ST_StyleType (Style Types)1812

2.18.91ST_TabJc (Custom Tab Stop Type)1813

2.18.92ST_TabTlc (Custom Tab Stop Leader Character)1815

2.18.93ST_TargetScreenSz (Target Screen Sizes for Generated Web Pages)1817

2.18.94ST_TblLayoutType (Table Layout Type)1818

2.18.95ST_TblOverlap (Table Overlap Setting)1822

2.18.96ST_TblStyleOverrideType (Conditional Table Style Formatting Types)1824

2.18.97ST_TblWidth (Table Width Units)1825

2.18.98ST_TextAlignment (Vertical Text Alignment Types)1827

2.18.99ST_TextboxTightWrap (Lines To Tight Wrap Within Text Box)1828

2.18.100ST_TextDirection (Text Flow Direction)1829

2.18.101ST_TextEffect (Animated Text Effects)1831

2.18.102ST_TextScale (Text Expansion/Compression Percentage)1832

2.18.103ST_Theme (Theme Font)1833

2.18.104ST_ThemeColor (Theme Color)1834

2.18.105ST_TwipsMeasure (Measurement in Twentieths of a Point)1836

2.18.106ST_UcharHexNumber (Two Digit Hexadecimal Number Value)1837

2.18.107ST_Underline (Underline Patterns)1838

2.18.108ST_UnsignedDecimalNumber (Unsigned Decimal Number Value)1843

2.18.109ST_VAnchor (Vertical Anchor Location)1843

2.18.110ST_VerticalAlignRun (Vertical Positioning Location)1844

2.18.111ST_VerticalJc (Vertical Alignment Type)1845

2.18.112ST_View (Document View Values)1847

2.18.113ST_Wrap (Text Wrapping around Text Frame Type)1848

2.18.114ST_XAlign (Horizontal Alignment Location)1850

2.18.115ST_YAlign (Vertical Alignment Location)1851

2.18.116ST_Zoom (Magnification Preset Values)1853

End of informative text.

Main Document Story

A WordprocessingML document consists of a compilation of two types of information:

Properties [Example: styles, numbering definitions, etc. end example]

Stories [Example: main document, comments, headers, etc. end example]

In WordprocessingML, stories are defined as each unique region of content within a document into which the user can type. The most important story in a WordprocessingML document is the main document story, which contains the primary contents of the document. The main document story in WordprocessingML is stored inside the body element.

[Example: Consider a document with a single paragraph in the main document story. This document would require the following WordprocessingML in its main document part:

<w:document>

<w:body>

<w:p/>

</w:body>

</w:document>

The fact that the paragraph is inside the body element makes it part of the main document story. end example]

background (Document Background)

This element specifies the background information for this document. This background shall be displayed on all pages of the document, behind all other document content.

The child elements of the background element are in the Vector Markup Language (VML) namespace, which allows any valid VML effect to be applied to the document's background.

For solid color fill backgrounds, however, the attributes on this element allow for the specification of use of any valid RGB or theme color value (the latter a reference to the document's themes part).

[Example: Consider a document which utilizes a gradient fill background moving between black and the accent5 theme color, as follows:

This background would require the following WordprocessingML markup:

<w:background w:color="9BBB59" w:themeColor="accent3">

<v:background id="_x0000_s1025" o:bwmode="white" fillcolor="#9bbb59 [3206]" o:targetscreensize="800,600">

<v:fill color2="fill darken(118)" method="linear sigma" focus="100%" type="gradientRadial">

<o:fill v:ext="view" type="gradientCenter" />

</v:fill>

</v:background>

</w:background>

The resulting background consists of a single color fill of the accent3 theme color from the themeColor attribute, layered under a gradientCenter fill from the fill attribute. end example]

Parent Elements

document (§2.2.3); glossaryDocument (§2.12.10)

Child Elements

Subclause

Any element from the urn:schemas-microsoft-com:vml namespace

§6.1

Any element from the urn:schemas-microsoft-com:office:office namespace

§6.2

Attributes

Description

color (Background Color)

Specifies the color for the background of the document.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the background color as appropriate.

If the background specifies the use of a theme color via the themeColor attribute, this value is superseded by the theme color value.

[Example: Consider a border color with value 2C34FF, as follows:

<w:background … w:color="2C34FF"/>

The background color shall therefore be the color with an RGB value of 44,52,255 (the decimal decoding of the hex value above). end example]

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

themeColor (Background Theme Color)

Specifies a theme color to be applied to the current background.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part, which allows color information to be set centrally in the document.

If the color attribute is specified, its value shall be ignored in favor of the color resulting from the use of this attribute with any appropriate themeTint and themeShade attribute value calculations applied.

[Example: Consider a background configured to use the accent5 theme color, resulting in the following WordprocessingML markup:

<w:background w:color="FFA8A0" w:themeColor="accent5" />

The background has a color with an RGB value of FFA8A0, however, because the themeColor attribute is specified, the RGB color value is ignored in favor of the accent5 theme color specified for this document. end example]

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this background.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 60% applied to a background in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:background w:color="943634"w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this background.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to the document's background.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:background w:color="95B3D7"w:themeColor="accent2" w:themeTint="99"/>

end example]

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

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

</extension>

</complexContent>

</complexType>

body (Document Body)

This element specifies the contents of the body of the document - the main document editing surface.

The document body contains what is referred to as block-level markup - markup which can exist as a sibling element to paragraphs in a WordprocessingML document.

[Example: Consider a document with a single paragraph in the main document story. This document would require the following WordprocessingML in its main document part:

<w:document>

<w:body>

<w:p/>

</w:body>

</w:document>

The fact that the paragraph is inside the body element makes it part of the main document story. end example]

Parent Elements

document (§2.2.3)

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

sectPr (Document Final Section Properties)

§2.6.18

tbl (Table)

§2.4.36

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

</sequence>

</complexType>

document (Document)

This element specifies the contents of a main document part in a WordprocessingML document.

[Example: Consider the basic structure of the main document part in a basic WordprocessingML document, as follows:

<w:document>

<w:body>

<w:p/>

</w:body>

</w:document>

All of the contents of the main document part are contained beneath the document element. end example]

Parent Elements

Root element of WordprocessingML Main Document part

Child Elements

Subclause

background (Document Background)

§2.2.1

body (Document Body)

§2.2.2

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

</sequence>

</extension>

</complexContent>

</complexType>

Paragraphs and Rich Formatting

The basis of a WordprocessingML document is its actual text contents. Those text contents can be stored in many contexts (tables, text boxes, etc.), but the most basic form of text contents in WordprocessingML is the paragraph, specified using the p element (§2.3.1.22).

Within the paragraph, all rich formatting at the paragraph level is stored within the pPr element (§2.3.1.25; §2.3.1.26). [Note: Some examples of paragraph properties are alignment, border, hyphenation override, indentation, line spacing, shading, text direction, and widow/orphan control. end note]

Within the paragraph, text is grouped into one or more runs, represented by the r element (§2.3.2.23), which define a region of text with a common set of properties.

Just as a paragraph can have rich formatting, so too can a run. All of the elements inside an r element have their properties controlled by a corresponding optional rPr run properties element (§2.7.8.1; §2.3.2.26). [Note: Some examples of run properties are bold, underlined, or visible. end note]

Within runs, run content is the set of possible objects and characters which can be displayed in the document.

Paragraphs

The most basic unit of block-level content within a WordprocessingML document, paragraphs are stored using the p element (§2.3.1.22). A paragraph defines a distinct division of content with a WordprocessingML document which begins on a new line.

[Example: Consider the paragraph fragment "The quick brown fox jumped … " which is centered on a paragraph. The justification property is a paragraph level property, and therefore is expressed on the paragraph properties as follows:

<w:p> <w:pPr> <w:jc w:val="center"/> <w:rPr> <w:i/> </w:rPr> </w:pPr>

<w:r> <w:rPr> <w:i/> </w:rPr> <w:t xml:space="preserve">The quick brown fox jumped … </w:t> </w:r></w:p>

Notice that each run specifies the character formatting information for its contents, and the paragraph specifies the paragraph level formatting (the center-justification). It is also notable that since leading and trailing whitespace is not normally significant in XML; some runs require a designating specifying that their whitespace is significant via the xml:space element. end example]

A paragraph's properties are specified via the pPr element (§2.3.1.25; §2.3.1.26). [Note: Some examples of paragraph properties are alignment, border, hyphenation override, indentation, line spacing, shading, text direction, and widow/orphan control. end note]

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

This element specifies whether the right indent shall be automatically adjusted for the given paragraph when a document grid has been defined for the current section using the docGrid element (§2.6.5), modifying of the current right indent used on this paragraph.

[Note: This setting is used in order to ensure that the line breaking for that paragraph is not determined by the width of the final character on the line. end note]

[Example: Consider a paragraph in which the right indent on the current paragraph should not be automatically determined based on the character pitch set in the document grid. This setting would be specified using the following WordprocessingML:

<w:p>

<w:pPr>

…

<w:adjustRightInd w:val="false" />

</w:pPr>

…

</w:p>

By explicitly setting the val to false, this paragraph will use its specified right indent settings regardless of the presence of the document grid for the parent section. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of on, 1, or true specifies that the property shall be explicitly applied. This is the default value for this attribute, and is implied when the parent element is present, but this attribute is omitted.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

This element specifies whether inter-character spacing shall automatically be adjusted between regions of Latin text and regions of East Asian text in the current paragraph. These regions shall be determined by the Unicode character values of the text content within the paragraph.

[Note: This property is used to ensure that the spacing between regions of Latin text and adjoining East Asian text is sufficient on each side such that the Latin text can be easily read within the East Asian text. end note]

[Example: Consider a paragraph in which the spacing should not be automatically adjusted based on the presence of Latin and East Asian text. This setting would be specified using the following WordprocessingML:

<w:p>

<w:pPr>

…

<w:autoSpaceDE w:val="false" />

</w:pPr>

…

</w:p>

By explicitly setting the val to false, this paragraph shall not automatically adjust the spacing of adjoining Latin and East Asian text. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

This element specifies whether inter-character spacing shall automatically be adjusted between regions of numbers and regions of East Asian text in the current paragraph. These regions shall be determined by the Unicode character values of the text content within the paragraph.

[Note: This property is used to ensure that the spacing between regions of numbers and adjoining East Asian text is sufficient on each side such that the numbers can be easily read within the East Asian text. end note]

[Example: Consider a paragraph in which the spacing should not be automatically adjusted based on the presence of numbers and East Asian text. This setting would be specified using the following WordprocessingML:

<w:p>

<w:pPr>

…

<w:autoSpaceDN w:val="false" />

</w:pPr>

…

</w:p>

By explicitly setting the val to false, this paragraph will not automatically adjust the spacing of adjoining numbers and East Asian text. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

bar (Paragraph Border Between Facing Pages)

This element specifies the border which may be displayed on the inside edge of the paragraph when the parent's section settings specify that the section shall be printed using mirrored margins using the mirrorMargins element (§2.15.1.57). [Note: This information is present in the WordprocessingML for the purposes of legacy document format compatibility, and it may be removed and/or ignored as required. end note]

[Example: Consider the following paragraph's WordprocessingML definition for its paragraph borders:

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:bar w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>Sample paragraph.</w:t>

</w:r>

</w:p>

This paragraph has a single line bar border as defined by the bar element. end example]

Parent Elements

pBdr (§2.3.1.24)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

This color therefore may be automatically be modified by a consumer as appropriate, for example, in order to ensure that the border can be distinguished against the page's background color. end example]

If the border style (the val attribute) specifies the use of an art border, this attribute is ignored. As well, if the border specifies the use of a theme color via the themeColor attribute, this value is superseded by the theme color value.

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

For the right and bottom borders, this is accomplished by duplicating the border below and right of the normal border location. For the right and top borders, this is accomplished by moving the order down and to the right of its original location.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

When a document has a page border that is relative to the page edges (using a value of page in the offsetFrom attribute on pgBorders (§2.6.10)), it shall specify the distance between the edge of the page and the beginning of this border in points.

When a document has a page border that is relative to the text extents (using a value of text in the offsetFrom attribute on pgBorders (§2.6.10)), or any other border type, it shall specify the distance between the edge of the object and the beginning of this border in points.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

The offsetFrom attribute specifies that the space value will provide the offset of the page border from the page edge, and the value of the space attribute specifies that the page offset shall be 24 points. end example]

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

sz (Border Width)

Specifies the width of the current border.

If the border style (val attribute) specifies a line border, the width of this border is specified in measurements of eighths of a point, with a minimum value of two (one-fourth of a point) and a maximum value of 96 (twelve points). Any values outside this range may be reassigned to a more appropriate value.

If the border style (val attribute) specifies an art border, the width of this border is specified in measurements of points, with a minimum value of one and a maximum value of 31. Any values outside this range may be reassigned to a more appropriate value.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

The border style is specified using the val attribute, and because that border style is a line border (dashed), the sz attribute specifies the size in eighths of a point (24 eighths of a point = 3 points). end example]

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

<w:top … w:color="FFA8A0" w:themeColor="accent2" w:themeTint="99" /><w:bottom … w:color="FFA8A0" w:themeColor="accent2" w:themeTint="99" /><w:left … w:color="FFA8A0" w:themeColor="accent2" w:themeTint="99" /><w:right … w:color="FFA8A0" w:themeColor="accent2" w:themeTint="99" />

The borders have a color with an RGB value of FFA8A0, however, because the themeColor attribute is specified, that value is ignored in favor of the accent2 theme color specified for this document. end example]

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

This border can either be an art border (a repeated image along the borders - only valid for page borders) or a line border (a line format repeated along the borders) - see the simple type definition for a description of each border style.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

between (Paragraph Border Between Identical Paragraphs)

This element specifies the border which shall be displayed between each paragraph in a set of paragraphs which have the same set of paragraph border settings.

To determine if any two adjoining paragraphs should have a between border or an individual top and bottom border, the set of borders on the two adjoining paragraphs are compared. If the border information on those two paragraphs is identical for all possible paragraphs borders, then the between border is displayed. Otherwise, each paragraph shall use its bottom and top border, respectively. If this border specifies a space attribute, that value is ignored - this border is always located at the bottom of each paragraph with an identical following paragraph, taking into account any space after the line pitch.

[Example: Consider the following two paragraphs' WordprocessingML definition:

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>First paragraph.</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="0" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>Second paragraph.</w:t>

</w:r>

</w:p>

Since the bottom paragraph border is different between the two paragraphs (the bottom space value goes from 1 to 0), these paragraphs do not use the between border, and instead paragraph one uses its bottom border, and paragraph two uses its top border. If those values were identical, then paragraph one would have a between brder below it, and paragraph two would have no top border. end example]

Parent Elements

pBdr (§2.3.1.24)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

bidi (Right to Left Paragraph Layout)

This element specifies that this paragraph shall be presented using a right to left direction. This property only affects the set of paragraph-level properties, and shall not affect the layout of text within the contents of this paragraph.

[Example: Consider a paragraph with the bidi property set as follows:

<w:p>

<w:pPr>

<w:bidi/>

</w:pPr>

...

</w:p>

This paragraph direction is now right to left, which means that all paragraph properties are displayed right to left (e.g. the paragraph marker glyph (if any) is displayed on the right, and indentation for the first line of the paragraph occurs on the right side of the page). end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

bottom (Paragraph Border Between Identical Paragraphs)

This element specifies the border which shall be displayed below a set of paragraphs which have the same set of paragraph border settings.

To determine if any two adjoining paragraphs shall have an individual top and bottom border or a between border, the set of borders on the two adjoining paragraphs are compared. If the border information on those two paragraphs is identical for all possible paragraphs borders, then the between border is displayed. Otherwise, the final paragraph shall use its bottom border and the following paragraph shall use its top border, respectively. If this border specifies a space attribute, that value determines the space after the bottom of the text (ignoring any space below) which should be left before this border is drawn, specified in points.

[Example: Consider the following two paragraphs' WordprocessingML definition:

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>First paragraph.</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="0" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>Second paragraph.</w:t>

</w:r>

</w:p>

Since the paragraph border is different between the two paragraphs (the bottom space value goes from 1 to 0), paragraph one uses its bottom border, which is located one point below the text in that paragraph. end example]

Parent Elements

pBdr (§2.3.1.24)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

cnfStyle (Paragraph Conditional Formatting)

This element specifies the set of conditional table style formatting properties which have been applied to this paragraph, if this paragraph is contained within a table cell. [Note: This property is an optimization which may be used by consumers to determine if a given property on a paragraph is the result of the table style properties vs. direct formatting on the paragraph itself. end note]

If this property is specified on a paragraph which is not contained within a table cell, then its contents shall be ignored when reading the contents of the document.

[Example: Consider a paragraph in the top right corner of a table with a table style applied. This paragraph would need to specify the following WordprocessingML:

<w:p>

<w:pPr>

<w:cnfStyle w:val="101000000100" />

...

<//w:pPr>

...

</w:p>

This paragraph specifies that it has the conditional properties from the table style for the first column, first row, and the NW corner of the parent table by setting the appropriate bits in the val attribute. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Conditional Formatting Bit Mask)

Specifies the set of conditional formatting properties that have been applied to this object.

These properties are expressed using a string serialization of a binary bitmask for each of the following properties (reading from the first character position right):

First Row - Is this the first row of the table?

Last Row - Is this the last row of the table?

First Column - Does this belong to the first column of the table?

Last Column - Does this belong to the last column of the table?

Band 1 Vertical - Does this belong to a column which should receive band 1 formatting? This property specifies whether the cell should receive the formatting specified for odd-numbered columns (e.g. 1,3,5,...)

Band 2 Vertical - Does this belong to a column which should receive band 2 formatting? This property specifies whether the cell should receive the formatting specified for even-numbered columns (e.g. 2,4,6...)

Band 1 Horizontal - Does this receive band 1 formatting? This property specifies whether the cell should receive the formatting specified for odd-numbered rows (e.g. 1,3,5,...)

Band 2 Horizontal - Does this receive band 2 formatting? This property specifies whether the cell should receive the formatting specified for even-numbered rows (e.g. 2,4,6...)

NE Cell - Is this part of the top-right corner of the table?

NW Cell - Is this part of the top-left corner of the table?

SE Cell - Is this part of the bottom-right corner of the table?

SW Cell - Is this part of the bottom-left corner of the table?

For each of these properties, a value of 1 in the specified character position in the string means that the value is true, a value of 0 means false. All values must be specified.

[Example: Consider a paragraph in the top right corner of a table with a table style applied. This paragraph would need to specify the following WordprocessingML:

<w:p>

<w:pPr>

<w:cnfStyle w:val="101000000100" />

...

</w:pPr>

...

</w:p>

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

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

</complexType>

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

This element specifies that any space specified before or after this paragraph, specified using the spacing element (§2.3.1.33), should not be applied when the preceding and following paragraphs are of the same paragraph style, affecting the top and bottom spacing respectively. [Example: This value is typically used for paragraphs in lists, in which any space between subsequent list items, even if inherited from another style, is not desirable. end example]

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then spacing is not ignored. If it is present, then the spacing above or below on this paragraph is subtracted from the spacing which would have been present if contextual spacing was off, never going below zero.

[Example: Consider two paragraphs defined as follows:

<w:p>

<w:pPr>

<w:pStyle w:val="TestParagraphStyle" />

<w:spacing w:after="200"/>

<w:contextualSpacing/>

</w:pPr>

…

</w:p>

<w:p>

<w:pPr>

<w:pStyle w:val="TestParagraphStyle" />

<w:spacing w:before="240"/>

</w:pPr>

…

</w:p>

The first paragraph specifies a spacing after of 10 points, and the second paragraph specifies a spacing before of 12 points, therefore according to the rules on the spacing element, the net paragraph spacing should be 12 points. However, since the first paragraph specifies that its spacing should be omitted between paragraphs of the same style, and the two paragraphs use the same TestParagraphStyle, that value is subtracted from the total, therefore the paragraphs are spaced by 2 points. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

divId (Associated HTML div ID)

This element specifies that this paragraph should be located within the specified HTML div tag when this document is saved in HTML format. This ID is then used to look up the associated div stored in the divs (§2.15.2.8) element. [Note: This element is used to preserve the fidelity of existing HTML documents when saved in the WordprocessingML format. end note].

If the paragraph does not specify this element, then any div referenced by the previous paragraph is closed, and this paragraph shall not belong to any div when saved as HTML. If this specified id does not exist in the collection of divs the current document, then any div referenced by the previous paragraph is closed, and this paragraph shall not belong to any div when saved as HTML.

[Example: Consider the following WordprocessingML paragraph fragment:

<w:p>

<w:pPr>

<w:divId w:val="1512645511" />

</w:pPr>

</w:p>

This paragraph specifies that it belongs to the HTML div with id 1512645511, stored in the divs element. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

framePr (Text Frame Properties)

This element specifies information about the current paragraph with regard to text frames. Text frames are paragraphs of text in a document which are positioned in a separate region or frame in the document, and can be positioned with a specific size and position relative to non-frame paragraphs in the current document.

The first piece of information specified by the framePr element is that the current paragraph is actually part of a text frame in the document. This information is specified simply by the presence of the framePr element in paragraph's properties. If the framePr element is omitted, the paragraph shall not be part of any text frame in the document.

The second piece of information concerns the set of paragraphs which are part of the current text frame in the document. This is determined based on the attributes on the framePr element. If the set of attribute values specified on two adjacent paragraphs is identical, then those two paragraphs shall be considered to be part of the same text frame and rendered within the same frame in the document.

[Example: Consider a document in which the following two paragraphs are located adjacent to one another:

<w:p>

<w:pPr>

<w:framePr w:w="2191" w:h="811" w:hRule="exact" w:hSpace="180" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1921"/>

</w:pPr>

<w:r>

<w:t>Paragraph One</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:framePr w:w="2191" w:h="810" w:hRule="exact" w:hSpace="180" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1921"/>

</w:pPr>

<w:r>

<w:t>Paragraph Two.</w:t>

</w:r>

</w:p>

These two paragraphs, although each is a part of a text frame due to the presence of the framePr element, are different text frames because of the differing h value - 810 vs. 811. end example]

The positioning of the frame relative to the properties stored on its attribute values shall be calculated relative to the next paragraphs in the document which is itself not part of a text frame.

[Example: Consider a document in which the following three paragraphs are located adjacent to one another:

<w:p>

<w:pPr>

<w:framePr w:w="2191" w:h="811" w:hRule="exact" w:hSpace="180" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1921"/>

</w:pPr>

<w:r>

<w:t>Paragraph One</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:framePr w:w="2191" w:h="811" w:hRule="exact" w:hSpace="180" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1921"/>

</w:pPr>

<w:r>

<w:t>Paragraph Two.</w:t>

</w:r>

</w:p>

<w:p/>

The first two paragraphs form a single text frame, which is anchored using its attribute values relative to the first non-frame paragraph following it (the third paragraph in the example). end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

anchorLock (Lock Frame Anchor to Paragraph)

Specifies that the frame shall always remain in the same logical position relative to the non-frame paragraphs which precede and follow it in this document.

This means that consumers which modify this document shall ensure that this text frame remains directly above the non-frame paragraph which it is currently above, by adjusting the frame's positioning properties as needed as the paragraph is moved throughout the document rather than moving the frame's logical location within the paragraphs in the document, if that would be more appropriate.

If this attribute is omitted, then this frame shall not have a locked anchor position.

[Example: Consider the following WordprocessingML paragraph contained in a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="exact" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:y="73" w:anchorLock="1"/>

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame has a locked anchor using the anchorLock attribute. If the text frame is moved down in the document, the text frame properties must be adjusted to be relative to the parent paragraph's same logical position - the paragraph cannot be relocated in the document, which results in changes to the frame's properties as follows:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="exact" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:y="-5247" w:anchorLock="1"/>

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

The non-frame paragraph was relocated 5320 twentieths of a point below its original location in the document, and the frame's vertical positioning properties were adjusted to ensure its logical location within the paragraph ordering was constant while its visual location was changed. end example]

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

dropCap (Drop Cap Frame)

Specifies that the current frame contains a drop cap to be located at the beginning of the next non-frame paragraph in the document. Its contents shall be used to specify how that drop cap should be positioned relative to that paragraph.

If this attribute is omitted, then this frame shall not be considered a drop cap frame.

[Note: Although a drop cap is simply a text frame, this element is used to determine how the cap should be positioned relative to the following non-frame paragraph in relative terms (see possible values), rather than relying on absolute sizing. end note]

[Example: Consider the following paragraph containing a text frame which should be positioned as a drop cap:

<w:p>

<w:pPr>

<w:framePr w:dropCap="margin" w:lines="3" w:hSpace="432" w:wrap="around" w:vAnchor="text" w:hAnchor="page" />

</w:pPr>

<w:r>

<w:t>A</w:t>

</w:r>

</w:p>

The dropCap attribute specifies a value of margin, so this drop cap will be placed outside of the text margin before the start of the current text. end example]

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

h (Frame Height)

Specifies the frame's height.

This height is expressed in twentieths of a point.

If this attribute is omitted, then its value shall be assumed to be 0.

The meaning of the value of the h attribute is defined based on the value of the hRule attribute for this text frame as follows:

If the value of hRule is auto, then the frame's height should be automatically determined based on the height of its contents. This value is ignored.

If the value of hRule is atLeast, then the frame's height should be at least the value of this attribute.

If the value of hRule is exact, then the frame's height should be exactly the value of this attribute.

[Example: Consider the following paragraph containing a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hspace="187" w:wrap="around" w:vanchor="text" w:hanchor="page" w:x="1643" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

The h attribute specifies a value of 2189 twentieths of a point, so this text frame will be a minimum of 2189 twentieths of a point high regardless of its contents, since its hRule value is set to atLeast. end example]

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

hAnchor (Frame Horizontal Positioning Base)

Specifies the base object from which the horizontal positioning in the x attribute should be calculated.

A text frame may be horizontally positioned relative to:

The vertical edge of the page before any runs of text (the left edge for left-to-right paragraphs, the right edge for right-to-left paragraphs)

The vertical edge of the text margin before any runs of text (the left edge for left-to-right paragraphs, the right edge for right-to-left paragraphs)

The vertical edge of the text margin for the column in which the anchor paragraph is located

If this attribute is omitted, then its value shall be assumed to be page.

[Example: Consider a text frame which should be positioned one inch to the right of its column in a left-to-right document. This text frame would be specified using the following WordprocessingML:

<w:pPr>

<w:framePr … w:x="1440" w:hAnchor="column" />

</w:pPr>

These frame properties specify that they are relative to the anchor paragraph's column, and that relative to that column, the frame should be 1440 twentieths of a point in the direction of the flow of text (right, in this case). end example]

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

hRule (Frame Height Type)

Specifies the meaning of the height specified for this frame.

The meaning of the value of the h attribute is defined based on the value of the hRule attribute for this text frame as follows:

If the value of hRule is auto, then the frame's height should be automatically determined based on the height of its contents. The h value is ignored.

If the value of hRule is atLeast, then the frame's height should be at least the value the h attribute.

If the value of hRule is exact, then the frame's height should be exactly the value of the h attribute.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider the following paragraph containing a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

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

hSpace (Horizontal Frame Padding)

Specifies the minimum distance which shall be maintained between the current text frame and any non-frame text which has been allowed to flow around this object when the wrap attribute on this text frame is set to around.

This distance is expressed in twentieths of a point.

If the wrap value is not set to around, this value shall be ignored. If this attribute is omitted, its value shall be assumed to be 0.

[Example: Consider a text frame which should have a minimum of a one-half inch spacing from any non-frame text on its left and right sides. This constraint would be specified using the following WordprocessingML:

<w:pPr>

<w:framePr ...w:hSpace="720" w:wrap="around" />

</w:pPr>

The wrap value of around allows text to wrap around this text frame, and the hSpace attribute specifies that the spacing between text and this frame shall be a minimum of 720 twentieths of a point. end example]

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

lines (Drop Cap Vertical Height in Lines)

Specifies the number of lines in the non-frame paragraph to which this text frame is anchored which should be used to calculate the drop cap's height.

If the current frame is not a drop cap (the parent framePr element does not have the dropCap attribute), this value is ignored. If the current text frame is a dropped cap and this attribute is present, then any other vertical positioning information shall be ignored.

If this attribute is omitted, then its value shall be considered to be 1.

[Example: Consider the following paragraph containing a text frame which should be positioned as a drop cap:

<w:p>

<w:pPr>

<w:framePr w:dropCap="margin" w:lines="3" w:hSpace="432" w:wrap="around" w:vAnchor="text" w:hAnchor="page" W:y="400" w:yAlign="text" />

</w:pPr>

<w:r>

<w:t>O</w:t>

</w:r>

</w:p>

Since this frame is being used as a dropped cap, the y and yAlign attributes are ignored and the height of the drop cap is the first three lines of the anchor paragraph. end example]

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

vAnchor (Frame Vertical Positioning Base)

Specifies the base object from which the horizontal positioning in the y attribute should be calculated.

A text frame may be horizontally positioned relative to:

The horizontal edge of the page before any runs of text (the top edge for top-to-bottom sections, the bottom for bottom-to-top sections)

The horizontal edge of the text margin before any runs of text (the top edge for top-to-bottom sections, the bottom for bottom-to-top sections)

The horizontal edge of the page before any runs of text (the top edge for top-to-bottom sections, the bottom for bottom-to-top sections)

If this attribute is omitted, then its value shall be assumed to be page.

[Example: Consider a text frame which should be positioned two inches below the page top in a top-to-bottom document. This text frame would be specified using the following WordprocessingML:

<w:pPr>

<w:framePr … w:y="2880" w:vAnchor="page" />

</w:pPr>

These frame properties specify that they are relative to the anchor page, and that relative to that column, the frame should be 2880 twentieths of a point in the direction of the flow of text (down, in this case). end example]

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

vSpace (Vertical Frame Padding)

Specifies the minimum distance which shall be maintained between the current text frame and any non-frame text which is above or below this text frame.

This distance is expressed in twentieths of a point.

If this attribute is omitted, its value shall be assumed to be 0.

[Example: Consider a text frame which should have a minimum of a one-half inch spacing from any non-frame text on its top and bottom sides. This constraint would be specified using the following WordprocessingML:

<w:pPr>

<w:framePr … w:vSpace="720" />

</w:pPr>

The vspace attribute specifies that the spacing between text and this frame shall be a minimum of 720 twentieths of a point. end example]

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

w (Frame Width)

Specifies the exact value for this text frame's width.

This value is specified in twentieths of a point.

When this attribute is present, the text frame shall be rendered to the exact width specified. If this attribute is omitted, the text frame width shall be automatically determined by the maximum line width of the content within the text frame.

[Example: Consider the following WordprocessingML fragment specifying a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hspace="187" w:wrap="around" w:vanchor="text" w:hanchor="page" w:x="1643" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame specifies that its width shall be exactly 2419 twips. If this attribute was removed, the text frame would be rendered at the width of the content Text Frame Content. end example]

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

wrap (Text Wrapping Around Frame)

Specifies the type of text wrapping which should be allowed around the contents of this text frame. This attribute determines if non-frame text shall be allowed to flow around the contents of this frame.

If this attribute is omitted, its value shall be assumed to be around.

[Example: Consider the following WordprocessingML fragment specifying a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame specifies that when the frame is rendered on the page, any non-text frame paragraphs which would normally flow onto the same lines shall be allowed to do so. end example]

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

x (Absolute Horizontal Position)

Specifies an absolute horizontal position for the text frame. This absolute position is specified relative to the horizontal anchor specified by the hAnchor attribute for this text frame.

This value is expressed in twentieths of a point. If it is positive, then the text frame is positioned after the anchor object in the direction of horizontal text flow in this document. If it is negative, then the text frame is positioned before the anchor object in the direction of horizontal text flow in this document.

If the xAlign attribute is also specified, then this value is ignored. If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider the following WordprocessingML fragment specifying a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame specifies that it should be located exactly 1643 twentieths of a point after the vertical edge of the page (from the hAnchor attribute). end example]

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

xAlign (Relative Horizontal Position)

Specifies a relative horizontal position for the text frame. This relative position is specified relative to the horizontal anchor specified by the hAnchor attribute for this text frame.

If omitted, this attribute is not specified and the value of the x attribute determines the absolute horizontal position of the text frame. If specified, the position for this attribute supersede any value which is specified in the x attribute, and that value is ignored.

[Example: Consider the following WordprocessingML fragment specifying a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:xAlign="left" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame specifies that it has a horizontal placement of exactly 1643 twentieths of a point relative to the page, but that exact placement is overridden by the presence of the xAlign attribute to place the frame on the left side of the page. end example]

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

y (Absolute Vertical Position)

Specifies an absolute vertical position for the text frame. This absolute position is specified relative to the vertical anchor specified by the vAnchor attribute for this text frame.

This value is expressed in twentieths of a point. If it is positive, then the text frame is positioned after the anchor object in the direction of vertical text flow in this document. If it is negative, then the text frame is positioned before the anchor object in the direction of vertical text flow in this document.

If the yAlign attribute is also specified, then this value is ignored. If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider the following WordprocessingML fragment specifying a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hSpace="187" w:wrap="around" w:vAnchor="text" w:hAnchor="page" w:x="1643" w:y="73" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame specifies that it should be located exactly 79 twentieths of a point below the top vertical edge of the anchor's paragraph's text (from the vAnchor attribute), assuming that the vertical text direction is top to bottom. end example]

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

yAlign (Relative Vertical Position)

Specifies a relative vertical position for the text frame. This relative position is specified relative to the vertical anchor specified by the vAnchor attribute for this text frame.

If omitted, this attribute is not specified and the value of the y attribute determines the absolute horizontal position of the text frame. If specified, the position for this attribute supersedes any value which is specified in the y attribute, and that value is ignored, unless the vAnchor is set to text, in which case any relative positioning is not allowed, and is itself ignored.

[Example: Consider the following WordprocessingML fragment specifying a text frame:

<w:p>

<w:pPr>

<w:framePr w:w="2419" w:h="2189" w:hRule="atLeast" w:hSpace="187" w:wrap="around" w:vAnchor="margin" w:hAnchor="page" w:x="1643" w:y="73" w:yAlign="center" />

</w:pPr>

<w:r>

<w:t>Text Frame Content.</w:t>

</w:r>

</w:p>

This text frame specifies that it has a vertical placement of exactly 73 twentieths of a point relative to the top margin, but that exact placement is overridden by the presence of the yAlign attribute to place the frame in the center of the margin. end example]

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

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

</complexType>

ind (Paragraph Indentation)

This element specifies the set of indentation properties applied to the current paragraph.

Indentation settings are overriden on an individual basis - if any single attribute on this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If any single attribute on this element is never specified in the style hierarchy, then no indentation of that type is applied to the paragraph.

[Example: Consider a paragraph which should have a one inch indentation from the text margins on both the left and the right sides, except for the first line in each paragraph, which should only be indented one quarter of an inch from the text margin (on the side which begins the flow of text for this paragraph). This set of indentations is specified using the following WordprocessingML:

<w:pPr>

<w:ind w:left="1440" w:right="1440" w:hanging="1080" />

</w:pPr>

This set of indentation properties specifies that a 1440 twentieths of a point indentation should be provided on both the left and the right side of the text margins for this paragraph, and that a 1080 twentieths of a point hanging indent (towards the text margin) should be applied to the text in the first paragraph, giving it a net one-quarter inch indent from the text margin. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

firstLine (Additional First Line Indentation)

Specifies the additional indentation which shall be applied to the first line of the parent paragraph. This additional indentation is specified relative to the paragraph indentation which is specified for all other lines in the parent paragraph.

The firstLine and hanging attributes are mutually exclusive, if both are specified, then the firstLine value is ignored. If the firstLineChars attribute is also specified, then this value is ignored. If this attribute is omitted, then its value shall be assumed to be zero (if needed).

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:left="1440" w:right="720" w:firstLine="1440" />

</w:pPr>

This set of indentations specifies that the first line should be indented 1440 twentieths of a point (one inch) from the indentation specified for all remaining paragraphs, which is the 1440 twentieths of a point, as specified by the left attribute. This gives the first line a two inch indentation from the text margin. end example]

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

firstLineChars (Additional First Line Indentation in Character Units)

It is specified in one hundredths of a character unit.

The firstLineChars and hangingChars attributes are mutually exclusive, if both are specified, then the firstLineChars value is ignored. If the firstLine attribute is also specified, then this value supersedes its other value. If this attribute is omitted, then its value shall be assumed to be zero (if needed).

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:left="1440" w:right="720" w:firstLineChars="140" />

</w:pPr>

This set of indentations specifies that the first line should be indented 140 hundredths of a character units from the indentation specified for all remaining paragraphs, which is the 1440 twentieths of a point specified by the left attribute. end example]

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

hanging (Indentation Removed from First Line)

Specifies the indentation which shall be removed from the first line of the parent paragraph, by moving the indentation on the first line back towards the beginning of the direction of text flow.

This indentation is specified relative to the paragraph indentation which is specified for all other lines in the parent paragraph.

The firstLine and hanging attributes are mutually exclusive, if both are specified, then the firstLine value is ignored. If the hangingChars attribute is also specified, then this value is ignored. If this attribute is omitted, its value shall be assumed to be zero (if needed).

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:left="1440" w:right="720" w:hanging="720" />

</w:pPr>

This set of indentations specifies that the first line should be indented 720 twentieths of a point (one inch) towards the text margin from the indentation specified for all remaining paragraphs, which is the 1440 twentieths of a point specified by the left attribute. This gives the first line a one-half inch indentation from the text margin. end example]

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

hangingChars (Indentation Removed From First Line in Character Units)

Specifies the indentation which shall be removed from the first line of the parent paragraph, by moving the indentation on the first line back towards the beginning of the direction of text flow.

This indentation is specified relative to the paragraph indentation which is specified for all other lines in the parent paragraph.

It is specified in one hundredths of a character unit.

The firstLineChars and hangingChars attributes are mutually exclusive, if both are specified, then the firstLine value is ignored. If the hanging attribute is also specified, then its value is superseded by this value. If this attribute is omitted, its value shall be assumed to be zero (if needed).

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:left="1440" w:right="720" w:hangingChars="100" />

</w:pPr>

This set of indentations specifies that the first line should be indented one character unit towards the text margin from the indentation specified for all remaining paragraphs, which is the 1440 twentieths of a point specified by the left attribute. end example]

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

left (Left Indentation)

Specifies the indentation which shall be placed between the left text margin for this paragraph and the left edge of that paragraph's content in a left to right paragraph, and the right text margin and the right edge of that paragraph's text in a right to left paragraph. If the mirrorIndents property (§2.3.1.18) is specified for this paragraph, then this indent is used for the inside page edge - the right page edge for odd numbered pages and the left page edge for even numbered pages.

If this attribute is omitted, its value shall be assumed to be zero.

All other values for this element are relative to the text margin, Negative values are defined such that the text is moved past the text margin, positive values move the text inside the text margin. This value may be superseded for the first line only via use of the firstLine or hanging attributes. As well, if the leftChars attribute is specified, then this value is ignored.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:left="720" w:right="2880" />

</w:pPr>

This set of paragraph indentations specifies that this paragraph's text should be indented 720 twentieths of a point (one half inch) from the left text margin in this document, assuming this is a left to right paragraph. end example]

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

leftChars (Left Indentation in Character Units)

This value is specified in hundredths of a character unit.

If this attribute is omitted, its value shall be assumed to be zero.

All other values for this element are relative to the text margin, Negative values are defined such that the text is moved past the text margin, positive values move the text inside the text margin. This value may be superseded for the first line only via use of the firstLine or hanging attributes. As well, if the left attribute is specified, then its value is ignored, and is superseded by this value.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:leftChars="250" />

</w:pPr>

This set of paragraph indentations specifies that this paragraph's text should be indented two and a half character units from the left text margin in this document. end example]

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

right (Right Indentation)

Specifies the indentation which shall be placed between the right text margin for this paragraph and the right edge of that paragraph's content in a left to right paragraph, and the left text margin and the left edge of that paragraph's text in a right to left paragraph. If the mirrorIndents property (§2.3.1.18) is specified for this paragraph, then this indent is used for the outside page edge - the left page edge for odd numbered pages and the right page edge for even numbered pages.

If this attribute is omitted, its value shall be assumed to be zero.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:left="720" w:right="-1440" />

</w:pPr>

This set of paragraph indentations specifies that this paragraph's text should be indented 1440 twentieths of a point (one inch) into the right text margin in this document, assuming this is a left to right paragraph. end example]

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

rightChars (Right Indentation in Character Units)

This value is specified in hundredths of a character unit.

If this attribute is omitted, its value shall be assumed to be zero.

All other values for this element are relative to the right text margin, Negative values are defined such that the text is moved past the text margin, positive values move the text inside the text margin. As well, if the right attribute is specified, then its value is ignored, and is superseded by this value.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:ind w:rightChars="250" />

</w:pPr>

This set of paragraph indentations specifies that this paragraph's text should be indented two and a half character units from the right text margin in this document, assuming this is a left to right paragraph. end example]

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

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

</complexType>

jc (Paragraph Alignment)

This element specifies the paragraph alignment which shall be applied to text in this paragraph.

[Example: Consider a paragraph which should be right justified to the right page side paragraph extents within a document. This constraint is specified in the following WordprocessingML content:

<w:pPr>

<w:jc w:val="right" />

</w:pPr>

The paragraph is now right justified on the page. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Alignment Type)

Specifies the justification which should be applied to the parent object within a document.

The possible values (see below) for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents.

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

<w:pPr>

<w:jc w:val="right" />

</w:pPr>

This paragraph is now right justified on the page, regardless of the paragraph or section settings. end example]

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

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

</complexType>

keepLines (Keep All Lines On One Page)

This element specifies that when rendering this document in a page view, all lines for this page are maintained on a single page whenever possible.

This means that if the contents of the current paragraph would normally span across two pages due to the placement of the paragraph's text, all lines in this paragraph shall be moved onto the next page to ensure they are displayed together. If this is not possible because all lines in the paragraph would exceed a single page in any case, then lines in this paragraph shall start on a new page, with page breaks as needed afterwards.

[Example: Consider a WordprocessingML document in which a code fragment (such as the schema fragments in this document) are defined such that they should never be broken across a page boundary in order to improve readability. This constraint would be specified using the following paragraph properties in WordprocessingML:

<w:pPr>

<w:keepLines />

...

</w:pPr>

This setting ensures that the schema fragment will be displayed on one page if possible. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

keepNext (Keep Paragraph With Next Paragraph)

This element specifies that when rendering this document in a paginated view, the contents of this paragraph are at least partly rendered on the same page as the following paragraph whenever possible.

This means that if the contents of the current paragraph would normally be completely rendered on a different page than the following paragraph (because only one of the two paragraphs would fit on the remaining space on the first page), then both paragraphs shall be rendered on a single page. This property can be chained between multiple paragraphs to ensure that all paragraphs are rendered on a single page without any intervening page boundaries. If this is not possible the entire set of paragraphs that are grouped together using this property would exceed a single page in any case, then the set of "keep with next" paragraphs shall start on a new page, with page breaks as needed afterwards.

[Example: Consider the following document with three paragraphs:

As shown above, the second paragraph and third paragraph are being rendered on two separate pages. However, a producer can specify that the second paragraph should not be displayed without any part of the third by setting the keepNext element as follows:

<w:pPr>

<w:keepNext/>

...

</w:pPr>

This would ensure that the second paragraph is displayed on the same page as the third paragraph:

However, if the first paragraph was also set to keepNext, then this set of grouped paragraphs would exceed a page, therefore the set of paragraphs would be grouped and start on the first page, resulting in the second paragraph reappearing on page one:

Since the paragraphs cannot all be put on one page, they all start on page one and flow as needed. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

This element specifies whether East Asian typography and line-breaking rules shall be applied to text in this paragraph to determine which characters may begin and end each line. This property only applies to Chinese PRC, Chinese Taiwan, and Japanese text in this paragraph.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then this property shall be applied to Chinese PRC, Chinese Taiwan, and Japanese text in this paragraph.

If these rules are set on the current paragraph, then the following rules are applied to the all first and last characters in the paragraph except the first and last character in the paragraph. By default, the following settings are used for kinsoku paragraphs:

Chinese (Simplified)

Cannot start a line:!%),.:;>?]}¢¨°·ˇˉ―‖’”…‰′″›℃∶、。〃〉》」』】〕〗〞︶︺︾﹀﹄﹚﹜﹞！＂％＇），．：；？］｀｜｝～￠

Cannot end a line:$([{£¥·‘“〈《「『【〔〖〝﹙﹛﹝＄（．［｛￡￥

Chinese (Traditional)

Cannot start a line:!),.:;?]}¢·–—’”•‥…‧′╴、。〉》」』】〕〞︰︱︳︴︶︸︺︼︾﹀﹂﹄﹏﹐﹑﹒﹔﹕﹖﹗﹚﹜﹞！），．：；？］｜｝､

Cannot end a line:([{£¥‘“‵〈《「『【〔〝︵︷︹︻︽︿﹁﹃﹙﹛﹝（｛

Japanese

Cannot start a line:!%),.:;?]}¢°’”‰′″℃、。々〉》」』】〕゛゜ゝゞ・ヽヾ！％），．：；？］｝｡｣､･ﾞﾟ￠

Cannot end a line:$([\{£¥‘“〈《「『【〔＄（［｛｢￡￥

Korean

Cannot start a line:!%),.:;?]}¢°’”′″℃〉》」』】〕！％），．：；？］｝￠

Cannot end a line:$([\{£¥‘“〈《「『【〔＄（［｛￡￥￦

If the strictFirstAndLastChars property (§2.15.1.83) is set in the Document Settings part, then the following settings supersede the defaults for Japanese:

Cannot start a line:!%),.:;?]}¢°’”‰′″℃、。々〉》」』】〕ぁぃぅぇぉっゃゅょゎ゛゜ゝゞァィゥェォッャュョヮヵヶ・ーヽヾ！％），．：；？］｝｡｣､･ｧｨｩｪｫｬｭｮｯｰﾞﾟ￠

Cannot end a line:$([\{£¥‘“〈《「『【〔＄（［｛｢￡￥

If the noLineBreaksBefore property (§2.15.1.59) is set in the Document Settings part, then the characters it specifies cannot begin a line for the specified language. If the noLineBreaksAfter property (§2.15.1.58) is set in the Document Settings part, then the characters it specifies cannot end a line for the specified language. In both cases, those settings shall supersede the defaults specified above.

[Example: Consider a document with a paragraph which should not use the kinsoku line breaking properties. This paragraph would define the following WordprocessingML:

<w:pPr>

<w:kinsoku w:val="off" />

</w:pPr>

This paragraph would now be exempt from any kinsoku line breaking rules, and the characters specified above are allowed to begin and end lines as they normally would. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

left (Left Paragraph Border)

This element specifies the border which shall be displayed on the left side of the page around the specified paragraph.

To determine if any two adjoining paragraphs should have a left border which spans the full line height or not, the left border shall be drawn between the top border or between border at the top (whichever would be rendered for the current paragraph), and the bottom border or between border at the bottom (whichever would be rendered for the current paragraph).

[Example: Consider the following two paragraphs' WordprocessingML definition:

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>First paragraph.</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>Second paragraph.</w:t>

</w:r>

</w:p>

Since the paragraph border set is identical between the two paragraphs, the paragraphs are connected by a between border. These paragraphs will therefore draw the left border between the top and between borders for the first paragraph, and the between and bottom borders for the second paragraph. end example]

Parent Elements

pBdr (§2.3.1.24)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

This element specifies whether the paragraph indents should be interpreted as mirrored indents. When this element is present, the left indent shall become the inside indent and the right indent shall become the outside indent.

If the mirrorIndents property is specified for this paragraph, then the inside page edge is the right page edge for odd numbered pages and the left page edge for even numbered pages. Conversely, the outside page edge is the left page edge for odd numbered pages and the right page edge for even numbered pages.

[Example: Consider a paragraph on the first page of a document which should have a one inch indentation from the text margins on the inside edge when the resulting document is printed and bound. This means that the paragraph will have a one inch right border if it is on an odd numbered page, and a one inch left border if it is on an even numbered page. This set of indentations is specified using the following WordprocessingML:

<w:pPr>

<w:ind w:left="1440" />

<w:mirrorIndents />

</w:pPr>

This set of indentation properties specifies that a 1440 twip indentation should be provided on the left side of the text margins for this paragraph. However, since the mirrorIndents property is set, the left indent is really the inside indent, and if this paragraph is on page one, shall result in a one inch right indent from the text margin. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

numPr (Numbering Definition Instance Reference)

This element specifies that the current paragraph references a numbering definition instance in the current document.

The presence of this element specifies that the paragraph will inherit the properties specified by the numbering definition in the num element (§2.9.16) at the level specified by the level specified in the lvl element (§2.9.7) and shall have an associated number positioned before the beginning of the text flow in this paragraph. When this element appears as part of the paragraph formatting for a paragraph style, then any numbering level defined using the ilvl element shall be ignored, and the pStyle element (§2.9.25) on the associated abstract numbering definition shall be used instead.

[Example: Consider a paragraph in a document which should be associated with level 4 of a numbering definition with ID 0. Associating the paragraph with this numbering definition would be specified using the following WordprocessingML:

<w:pPr>

<w:numPr>

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

<w:numId w:val="0" />

</w:numPr>

</w:pPr>

The numPr element specifies that this paragraph shall contain numbering information, and its children specify that the numbering definition for that numbering information shall have a numId of 0 and an ilvl of 4 within that numbering definition. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Child Elements

Subclause

ilvl (Numbering Level Reference)

§2.9.3

ins (Inserted Numbering Properties)

§2.13.5.19

numberingChange (Previous Paragraph Numbering Properties)

§2.13.5.30

numId (Numbering Definition Instance Reference)

§2.9.19

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

</sequence>

</complexType>

outlineLvl (Associated Outline Level)

This element specifies the outline level which shall be associated with the current paragraph in the document. The outline level specifies an integer which defines the level of the associated text. This level shall not affect the appearance of the text in the document, but shall be used to calculate the TOC field (§2.16.5.75) if the appropriate field switches have been set, and may be used by consumers to provide additional application behavior.

The outline level of text in the document (specified using the val attribute) may be from 0 to 9, where 9 specifically indicates that there is no outline level specifically applied to this paragraph. If this element is omitted, then the outline level of the content is assumed to be 9 (no level).

[Example: Consider a paragraph in a document which has outline level 1 applied to it. This paragraph would specify the following WordprocessingML:

<w:pPr>

<w:outlineLvl w:val="0" />

</w:pPr>

This paragraph is now of outline level 1, and if a table of contents field is inserted that utilizes outlines levels, the text in this paragraph will be at level one in the TOC. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

overflowPunct (Allow Punctuation to Extent Past Text Extents)

This element specifies that punctuation characters which appear at the end of text in any line in this paragraph shall be allowed to extend one character past the text extents (indents/margins) as needed in order to ensure that they are not displayed as hanging punctuation. Hanging punctuation is defined as punctuation which appears on a different line than the text which it logically would appear with.

Omitting this element sets its value to true.

[Example: Consider a WordprocessingML document with the following string at the end of a line:

"This is some text in quotation marks"

Typically, if the text extents would normally fall between the letter s and the closing quotation mark, the quotation mark would be allowed to extend past the end of the line by one character even though the punctuation is not part of the word marks (since the omission of overflowPunct is equivalent to setting its val attribute to true).

However, if this behavior should not be applied to this paragraph, a producer can specify this by setting the property in the WordprocessingML:

<w:pPr>

<w:overflowPunct w:val="0" />

</w:pPr>

The line would now break after the letter s, regardless of the fact that the next character is a quotation mark. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

p (Paragraph)

This element specifies a paragraph of content in the document.

The contents of a paragraph in a WordprocessingML document shall consist of any combination of the following four types of content:

Paragraph properties

Annotations (bookmarks, comments, revisions)

Custom markup

Run level content (fields, hyperlinks, runs)

[Example: Consider a basic WordprocessingML document with a single paragraph. This paragraph would be expressed as follows:

<w:document>

<w:body>

<w:p>

<w:r>

<w:t>Text</w:t>

</w:r>

<w:fldSimple w:instr="AUTHOR">

<w:r>

<w:t>Author Name</w:t>

</w:r>

</w:fldSimple>

</w:p>

</w:body>

</w:document>

The p element is the container for all of the content in the paragraph, which in this example includes both a text run and a simple field. end example]

Parent Elements

body (§2.2.2); comment (§2.13.4.2); customXml (§2.5.1.6); docPartBody (§2.12.6); endnote (§2.11.2); footnote (§2.11.10); ftr (§2.10.3); hdr (§2.10.4); sdtContent (§2.5.2.32); tc (§2.4.62); txbxContent (§2.17.1.1)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

fldSimple (Simple Field)

§2.16.21

hyperlink (Hyperlink)

§2.16.24

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

pPr (Paragraph Properties)

§2.3.1.26

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

subDoc (Anchor for Subdocument Location)

§2.17.2.1

Attributes

Description

rsidDel (Revision Identifier for Paragraph Deletion)

Specifies a unique identifier used to track the editing session when the paragraph was deleted from the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidP (Revision Identifier for Paragraph Properties)

This attribute specifies a unique identifier used to track the editing session when the paragraph's properties were last modified in this document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidR (Revision Identifier for Paragraph)

This attribute specifies a unique identifier used to track the editing session when the paragraph was added to the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidRDefault (Default Revision Identifier for Runs)

This attribute specifies a unique identifier used for all runs in this paragraph which do not explicitly declare an rsidR attribute. This attribute allows consumers to optimize the locations where rsid* values are written in this document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidRPr (Revision Identifier for Paragraph Glyph Formatting)

This attribute specifies a unique identifier used to track the editing session when the glyph character representing the paragraph mark was last modified in the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

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

</sequence>

</complexType>

pageBreakBefore (Start Paragraph on Next Page)

This element specifies that when rendering this document in a paginated view, the contents of this paragraph are rendered on the start of a new page in the document.

This means that if the contents of the current paragraph would normally be rendered on the middle of a page in the host document, then the paragraph shall be rendered on a new page as if the paragraph was preceded by a page break in the WordprocessingML contents of the document. This property supersedes any use of the keepNext property, so that if any paragraph wishes to be on the same page as this paragraph, they will still be separated by a page break.

[Example: Consider the following document with three paragraphs:

As shown above, the second paragraph is rendered at the bottom of page one. However, a producer can specify that the second paragraph should be displayed at the top of a new page by setting the pageBreakBefore element as follows:

<w:pPr>

<w:pageBreakBefore/>

</w:pPr>

This would ensure that the second paragraph is displayed on a new page:

Since the paragraph is specified to start on a new page, it begins page two even though it could have fit on page one. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

pBdr (Paragraph Borders)

This element specifies the borders for the parent paragraph. Each child element shall specify a specific type of border (left, right, bottom, top, and between).

[Example: Consider a pairing of paragraphs which have a three point red border around them, and a six point border between them. These paragraphs would each have the following set of paragraph borders:

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="FF0000" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="FF0000" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="FF0000" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="FF0000" />

<w:between w:val="single" w:sz="48" w:space="1" w:color="4D5D2C" />

</w:pBdr>

The resulting paragraphs have identical pBdr values, therefore they would use the top, left, bottom, and right borders around them as a units, and the between border between each other. This matching heuristic is further discussed in the child elements of the pBdr element. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Child Elements

Subclause

bar (Paragraph Border Between Facing Pages)

§2.3.1.4

between (Paragraph Border Between Identical Paragraphs)

§2.3.1.5

bottom (Paragraph Border Between Identical Paragraphs)

§2.3.1.7

left (Left Paragraph Border)

§2.3.1.17

right (Right Paragraph Border)

§2.3.1.28

top (Paragraph Border Above Identical Paragraphs)

§2.3.1.42

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

</sequence>

</complexType>

pPr (Previous Paragraph Properties)

This element specifies a set of paragraph properties which shall be attributed to a revision by a particular author and at a particular time. This element contains the set of properties which have been tracked as a specific set of revisions by one author.

[Example: Consider a paragraph which should have a set of paragraph formatting properties that were added with revision tracking turned on. This set of revised properties is specified in the paragraph properties as follows:

<w:p>

<w:pPr>

<w:pBdr>

<w:bottom w:val="single" w:sz="8" w:space="4" w:color="4F81BD" />

</w:pBdr>

<w:pPrChange w:author="user1" … >

<w:pPr>

<w:spacing w:after="300" />

<w:contextualSpacing />

</w:pPr>

</w:pPrChange>

</w:pPr>

</w:p>

The pPr element under pPrChange specifies the properties which are applied to the current paragraph with revision tracking turned on - in this case, spacing after the paragraph using the spacing element (§2.3.1.33), and that spacing should be ignored for paragraphs above/below of the same style using the contextualSpacing element (§2.3.1.9). end example]

Parent Elements

pPrChange (§2.13.5.31)

Child Elements

Subclause

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

§2.3.1.1

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

§2.3.1.2

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

§2.3.1.3

bidi (Right to Left Paragraph Layout)

§2.3.1.6

cnfStyle (Paragraph Conditional Formatting)

§2.3.1.8

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

§2.3.1.9

divId (Associated HTML div ID)

§2.3.1.10

framePr (Text Frame Properties)

§2.3.1.11

ind (Paragraph Indentation)

§2.3.1.12

jc (Paragraph Alignment)

§2.3.1.13

keepLines (Keep All Lines On One Page)

§2.3.1.14

keepNext (Keep Paragraph With Next Paragraph)

§2.3.1.15

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

§2.3.1.16

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

§2.3.1.18

numPr (Numbering Definition Instance Reference)

§2.3.1.19

outlineLvl (Associated Outline Level)

§2.3.1.20

overflowPunct (Allow Punctuation to Extent Past Text Extents)

§2.3.1.21

pageBreakBefore (Start Paragraph on Next Page)

§2.3.1.23

pBdr (Paragraph Borders)

§2.3.1.24

pStyle (Referenced Paragraph Style)

§2.3.1.27

shd (Paragraph Shading)

§2.3.1.31

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

§2.3.1.32

spacing (Spacing Between Lines and Above/Below Paragraph)

§2.3.1.33

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

§2.3.1.34

suppressLineNumbers (Suppress Line Numbers for Paragraph)

§2.3.1.35

suppressOverlap (Prevent Text Frames From Overlapping)

§2.3.1.36

tabs (Set of Custom Tab Stops)

§2.3.1.38

textAlignment (Vertical Character Alignment on Line)

§2.3.1.39

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

§2.3.1.40

textDirection (Paragraph Text Flow Direction)

§2.3.1.41

topLinePunct (Compress Punctuation at Start of a Line)

§2.3.1.43

widowControl (Allow First/Last Line to Display on a Separate Page)

§2.3.1.44

wordWrap (Allow Line Breaking At Character Level)

§2.3.1.45

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

</sequence>

</complexType>

pPr (Paragraph Properties)

This element specifies a set of paragraph properties which shall be applied to the contents of the parent paragraph after all style/numbering/table properties have been applied to the text. These properties are defined as direct formatting, since they are directly applied to the paragraph and supersede any formatting from styles.

[Example: Consider a paragraph which should have a set of paragraph formatting properties. This set of properties is specified in the paragraph properties as follows:

<w:p>

<w:pPr>

<w:pBdr>

<w:bottom w:val="single" w:sz="8" w:space="4" w:color="4F81BD" />

</w:pBdr>

<w:spacing w:after="300" />

<w:contextualSpacing />

</w:pPr>

</w:p>

The pPr element specifies the properties which are applied to the current paragraph - in this case, a bottom paragraph border using the bottom element (§2.3.1.7), spacing after the paragraph using the spacing element (§2.3.1.33), and that spacing should be ignored for paragraphs above/below of the same style using the contextualSpacing element (§2.3.1.9). end example]

Parent Elements

p (§2.3.1.22)

Child Elements

Subclause

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

§2.3.1.1

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

§2.3.1.2

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

§2.3.1.3

bidi (Right to Left Paragraph Layout)

§2.3.1.6

cnfStyle (Paragraph Conditional Formatting)

§2.3.1.8

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

§2.3.1.9

divId (Associated HTML div ID)

§2.3.1.10

framePr (Text Frame Properties)

§2.3.1.11

ind (Paragraph Indentation)

§2.3.1.12

jc (Paragraph Alignment)

§2.3.1.13

keepLines (Keep All Lines On One Page)

§2.3.1.14

keepNext (Keep Paragraph With Next Paragraph)

§2.3.1.15

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

§2.3.1.16

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

§2.3.1.18

numPr (Numbering Definition Instance Reference)

§2.3.1.19

outlineLvl (Associated Outline Level)

§2.3.1.20

overflowPunct (Allow Punctuation to Extent Past Text Extents)

§2.3.1.21

pageBreakBefore (Start Paragraph on Next Page)

§2.3.1.23

pBdr (Paragraph Borders)

§2.3.1.24

pPrChange (Revision Information for Paragraph Properties)

§2.13.5.31

pStyle (Referenced Paragraph Style)

§2.3.1.27

rPr (Run Properties for the Paragraph Mark)

§2.3.1.29

sectPr (Section Properties)

§2.6.19

shd (Paragraph Shading)

§2.3.1.31

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

§2.3.1.32

spacing (Spacing Between Lines and Above/Below Paragraph)

§2.3.1.33

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

§2.3.1.34

suppressLineNumbers (Suppress Line Numbers for Paragraph)

§2.3.1.35

suppressOverlap (Prevent Text Frames From Overlapping)

§2.3.1.36

tabs (Set of Custom Tab Stops)

§2.3.1.38

textAlignment (Vertical Character Alignment on Line)

§2.3.1.39

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

§2.3.1.40

textDirection (Paragraph Text Flow Direction)

§2.3.1.41

topLinePunct (Compress Punctuation at Start of a Line)

§2.3.1.43

widowControl (Allow First/Last Line to Display on a Separate Page)

§2.3.1.44

wordWrap (Allow Line Breaking At Character Level)

§2.3.1.45

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

</sequence>

</extension>

</complexContent>

</complexType>

pStyle (Referenced Paragraph Style)

This element specifies the style ID of the paragraph style which shall be used to format the contents of this paragraph.

This formatting is applied at the following location in the style hierarchy:

Document defaults

Table styles

Numbering styles

Paragraph styles (this element)

Character styles

Direct Formatting

This means that all properties specified in the style element (§2.7.3.17) with a styleId which corresponds to the value in this element's val attribute are applied to the paragraph at the appropriate level in the hierarchy.

If this element is omitted, or it references a style which does not exist, then no paragraph style shall be applied to the current paragraph. As well, this property is ignored if the paragraph properties are part of a paragraph style.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val=”TestParagraphStyle” />

<w:ind w:left=”1440” />

</w:pPr>

This paragraph specifies that it will inherit all of the paragraph properties specified by the paragraph style with a styleId of TestParagraphStyle, which will then have any indentation properties overridden with a left indentation of 1440 twentieths of a point, and no indentation for any other value. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

right (Right Paragraph Border)

This element specifies the border which shall be displayed on the right side of the page around the specified paragraph.

To determine if any two adjoining paragraphs should have a right border which spans the full line height or not, the right border shall be drawn between the top border or between border at the top (whichever would be rendered for the current paragraph), and the bottom border or between border at the bottom (whichever would be rendered for the current paragraph).

[Example: Consider the following two paragraphs' WordprocessingML definition:

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>First paragraph.</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>Second paragraph.</w:t>

</w:r>

</w:p>

Since the paragraph border set is identical between the two paragraphs, the paragraphs are connected by a between border. These paragraphs will therefore draw the right border between the top and between borders for the first paragraph, and the between and bottom borders for the second paragraph. end example]

Parent Elements

pBdr (§2.3.1.24)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

rPr (Run Properties for the Paragraph Mark)

This element specifies the set of run properties applied to the glyph used to represent the physical location of the paragraph mark for this paragraph. This paragraph mark, being a physical character in the document, can be formatted, and therefore must be capable of representing this formatting like any other character in the document.

If this element is not present, the paragraph mark is unformatted, as with any other run of text.

[Example: Consider a run of text displayed as follows, including a display format using the pilcrow sign ¶ for the paragraph mark glyph:

This is some text and the paragraph mark.¶

If we format the display formatting for the paragraph mark by making it red and giving it a 72 point font size, then the WordprocessingML shall reflect this formatting on the paragraph as follows:

<w:pPr>

<w:rPr>

<w:color w:val="FF0000" />

<w:sz w:val="144" />

</w:rPr>

</w:pPr>

The paragraph glyph's formatting is stored in the rPr element under the paragraph properties, since there is no run saved for the paragraph mark itself. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

del (Deleted Paragraph)

§2.13.5.13

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

ins (Inserted Paragraph)

§2.13.5.18

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

moveFrom (Move Source Paragraph)

§2.13.5.22

moveTo (Move Destination Paragraph)

§2.13.5.25

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties on the Paragraph Mark)

§2.13.5.33

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

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

</sequence>

</complexType>

rPr (Previous Run Properties for the Paragraph Mark)

This element specifies a set of run properties applied to the glyph used to represent the physical location of the paragraph mark for this paragraph which shall be attributed to a revision by a particular author and at a particular time. This element contains the set of properties which have been tracked as a specific set of revisions by one author.

[Example: Consider a run which has a set of run formatting properties that were added with revision tracking turned on. This set of revised properties is specified in the run properties as follows:

<w:p> <w:pPr> <w:rPr> <w:b /> <w:imprint /> <w:lang w:val="en-ca" /> <w:rPrChange w:author="user1"> <w:rPr> <w:i /> <w:dstrike w:val="false" /> </w:rPr> </w:rPrChange> </w:rPr> </w:pPr></w:p>

The rPr element under rPrChange specifies the properties which are applied to the run representing the paragraph mark before the revision tracking was turned on - in this case, italics using the i element (§2.3.2.14), and that any double strikethrough which was applied based on the style hierarchy shall be turned off using the dstrike element (§2.3.2.7). end example]

Parent Elements

rPrChange (§2.13.5.33)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

del (Deleted Paragraph)

§2.13.5.13

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

ins (Inserted Paragraph)

§2.13.5.18

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

moveFrom (Move Source Paragraph)

§2.13.5.22

moveTo (Move Destination Paragraph)

§2.13.5.25

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

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

</sequence>

</complexType>

shd (Paragraph Shading)

This element specifies the shading applied to the contents of the paragraph.

This shading consists of three components:

Background Color

(optional) Pattern

(optional) Pattern Color

The resulting shading is applied by setting the background color behind the paragraph, then applying the pattern color using the mask supplied by the pattern over that background.

[Example: Consider a paragraph which shall have a background consisting of a theme color accent3 with a theme color accent6 overlaid using a 20% fill pattern. This requirement is specified using the following WordprocessingML:

<w:pPr>

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

</w:pPr>

The resulting paragraph will use the background color accent3 under the foreground pattern color accent6 as specified by the pct20 pattern mask. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

color (Shading Pattern Color)

Specifies the color used for any foreground pattern specified for this shading using the val attribute.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the foreground shading color as appropriate.

If the shading style (the val attribute) specifies the use of no shading format or is omitted, then this property has no effect. Also, if the shading specifies the use of a theme color via the themeColor attribute, then this value is superseded by the theme color value.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading of type pct20 with a foreground color value of auto, as follows:

<w:shd w:val="pct20"... w:color="auto"/>

The foreground color for this shading pattern therefore may be automatically be modified by a consumer as appropriate, for example, in order to ensure that the shading color can be distinguished against the page's background color. end example]

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

fill (Shading Background Color)

Specifies the color used for the background for this shading.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the background shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading using a background color of hex value C3D69B, using the following WordprocessingML:

<w:shd w:fill="C3D69B" />

The background color for this shading therefore will be a color with a hex value of C3D69B. end example]

If the shading specifies the use of a theme color via the themeFill attribute, then this value is superseded by the theme color value.

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

themeColor (Shading Pattern Theme Color)

Specifies a theme color which should be applied to any foreground pattern specified for this shading using the val attribute.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading pattern color.

<w:pPr>

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

</w:pPr>

The resulting paragraph will use the foreground pattern color accent6 in the region specified by the pct20 pattern mask. end example]

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

themeFill (Shading Background Theme Color)

Specifies a theme color which should be applied to the background for this shading.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading background color.

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

The resulting shading will use the background color specified by the accent3 theme color. end example]

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

themeFillShade (Shading Background Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeFillShade is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

The resulting themeFillShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting shading's fill attribute:

<w:shd w:fill="943634" w:themeFill="accent2" w:themeFillShade="BF" />

end example]

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

themeFillTint (Shading Background Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeFillTint is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeFillTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's fill attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:fill="95B3D7" w:themeFillColor="accent2" w:themeFillTint="99" />

end example]

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

themeShade (Shading Pattern Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeShade is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

Te resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:shd w:color="943634" w:themeColor="accent2" w:themeShade="BF" />

end example]

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

themeTint (Shading Pattern Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeTint is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's color attribute:

<w:shd w:color="95B3D7" w:themeColor="accent2" w:themeTint="99" />

end example]

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

val (Shading Pattern)

Specifies the pattern which shall be used to lay the pattern color over the background color for this paragraph shading.

[Example: Consider a shaded paragraph which uses a 10 percent foreground fill, resulting in the following WordprocessingML:

<w:shd w:val="pct10" .../>

This shading val is pct10, indicating that the border style is a 10 percent foreground fill mask. end example]

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

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

</complexType>

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

This element specifies whether the current paragraph should use the document grid lines per page settings defined in the docGrid element (§2.6.5) when laying out the contents in the paragraph. This setting determines whether the additional line pitch specified in the document grid shall be added to each line in this paragraph as specified by the document grid.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the paragraph shall use the document grid to lay out text when a document grid is defined for this document.

[Example: Consider two single-spaced paragraphs in a section with a document grid set to allow 15 lines per page. This document grid would effectively specifies that an additional line pitch of 45.6 points shall be added to each line in order to ensure that the resulting page contains only 15 lines of text.

If this property is set on the first paragraph, but turned off on the second paragraph, as follows:

<w:p>

<w:pPr>

<w:snapToGrid w:val="off" />

</w:pPr>

...

</w:p>

<w:p>

...

</w:p>

The resulting document shall have 45.6 points of additional line pitch added to each line in paragraph two, but zero lines of additional line pitch added to each line in paragraph one, since the snapToGrid property is turned off. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

spacing (Spacing Between Lines and Above/Below Paragraph)

This element specifies the inter-line and inter-paragraph spacing which shall be applied to the contents of this paragraph when it is displayed by a consumer.

If this element is omitted on a given paragraph, each of its values is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the paragraph shall have no spacing applied to its lines, or above and below its contents.

[Example: Consider the following WordprocessingML paragraph:

<w:pPr>

<w:spacing w:after="200" w:line="276" w:lineRule="auto" />

</w:pPr>

This paragraph specifies that it shall have at least 200 twentieths of a point after the last line in each paragraph, and that the spacing in each line should be automatically calculated based on a 1.15 times (276 divided by 240) the normal single spacing calculation. end example]

When determining the spacing between any two paragraphs, a consumer shall use the maximum of the inter-line spacing in each paragraph, the spacing after the first paragraph and the spacing before the second paragraph to determine the net spacing between the paragraphs.

[Example: Consider two consecutive single-spaced paragraphs in a document, the first of which specifies spacing below of 12 points, the second of which specifies spacing above of 4 points. These constraints are expressed using the following WordprocessingML:

<w:p>

<w:pPr>

<w:spacing w:after="240" />

</w:pPr>

…

</w:p>

<w:p>

<w:pPr>

<w:spacing w:before="80" />

</w:pPr>

…

</w:p>

The resulting spacing between the first and second paragraph will be 12 points, since that is the largest spacing requested between the two paragraphs. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

after (Spacing Below Paragraph)

Specifies the spacing that should be added after the last line in this paragraph in the document in absolute units.

If the afterLines attribute or the afterAutoSpacing attribute is also specified, then this attribute value is ignored.

[Example: Consider the following WordprocessingML paragraph:

<w:p>

<w:pPr>

<w:spacing w:after="240" />

</w:pPr>

…

</w:p>

This paragraph shall have a minimum spacing below its final lines of 240 twentieths of a point, although the actual spacing may be determined by the inter-line spacing or the spacing above the following paragraph, if either are greater. end example]

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

afterAutospacing (Automatically Determine Spacing Below Paragraph)

Specifies whether a consumer shall automatically determine the spacing after this paragraph based on its contents.

This automatic spacing shall match the spacing which would be applied to the paragraph in an HTML document where no explicit spacing before/after is specified.

If this attribute is specified, then any value in after or afterLines is ignored, and the spacing is automatically determined by the consumer.

[Example: Consider a paragraph in a document whose spacing below shall automatically be determined by the consumer based on the paragraph's contents. This constraint would be specified by the following WordprocessingML:

<w:pPr>

<w:spacing .. w:afterAutospacing="on" />

</w:pPr>

The resulting paragraph shall have the spacing below its last line determined automatically by the consumer to match an HTML document as specified. end example]

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

afterLines (Spacing Below Paragraph in Line Units)

Specifies the spacing that should be added after the last line in this paragraph in the document in line units.

The value of this attribute is specified in one hundredths of a line.

If the afterAutoSpacing attribute is also specified, then this attribute value is ignored. If this setting is never specified in the style hierarchy, then its value shall be zero (if needed).

[Example: Consider the following WordprocessingML paragraph:

<w:p>

<w:pPr>

<w:spacing w:afterLines="300" />

</w:pPr>

...

</w:p>

This paragraph shall have a minimum spacing below its final lines of 3 lines, although the actual spacing may be determined by the inter-line spacing or the spacing above the following paragraph, if either are greater. end example]

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

before (Spacing Above Paragraph)

Specifies the spacing that should be added above the first line in this paragraph in the document in absolute units.

If the beforeLines attribute or the beforeAutoSpacing attribute is also specified, then this attribute value is ignored.

[Example: Consider the following WordprocessingML paragraph:

<w:p>

<w:pPr>

<w:spacing w:before="80" />

</w:pPr>

...

</w:p>

This paragraph shall have a minimum spacing above its first line of 80 twentieths of a point, although the actual spacing may be determined by the inter-line spacing or the spacing below the last line in the preceding paragraph, if either are greater. end example]

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

beforeAutospacing (Automatically Determine Spacing Above Paragraph)

Specifies whether a consumer shall automatically determine the spacing before this paragraph based on its contents.

This automatic spacing shall match the spacing which would be applied to the paragraph in an HTML document where no explicit spacing before/after is specified.

If this attribute is specified, then any value in before or beforeLines is ignored, and the spacing is automatically determined by the consumer.

[Example: Consider a paragraph in a document whose spacing above shall automatically be determined by the consumer based on the paragraph's contents. This constraint would be specified by the following WordprocessingML:

<w:pPr>

<w:spacing … w:beforeAutospacing="on" />

</w:pPr>

The resulting paragraph shall have the spacing above its first line determined automatically by the consumer to match an HTML document as specified. end example]

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

beforeLines (Spacing Above Paragraph IN Line Units)

Specifies the spacing that should be added before the first line in this paragraph in the document in line units.

The value of this attribute is specified in one hundredths of a line.

If the beforeAutoSpacing attribute is also specified, then this attribute value is ignored. If this setting is never specified in the style hierarchy, then its value shall be zero (if needed).

[Example: Consider the following WordprocessingML paragraph:

<w:p>

<w:pPr>

<w:spacing w:beforeLines="100" />

</w:pPr>

...

</w:p>

This paragraph shall have a minimum spacing above its first line of 1 line, although the actual spacing may be determined by the inter-line spacing or the spacing below the preceding paragraph, if either are greater. end example]

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

line (Spacing Between Lines in Paragraph)

This attribute specifies the amount of vertical spacing between lines of text within this paragraph.

If the value of the lineRule attribute is either atLeast or exactly, then the value of this attribute shall be interpreted as twentieths of a point. When the value of the lineRule attribute is either exactly, the text shall be positioned as follows within that line height:

When the line height is too small, the text shall be positioned at the bottom of the line (i.e. clipped from the top down)

When the line height is too large, the text shall be centered in the available space.

If the value of the lineRule attribute is auto, then the value of the line attribute shall be interpreted as 240ths of a line, in the manner described by the simple type's values.

[Example: Consider the following WordprocessingML paragraph which should have an inter-line spacing of 1.15 times the line height. This constraint would be specified using the following WordprocessingML:

<w:pPr>

<w:spacing w:line="276" w:lineRule="auto" />

</w:pPr>

The lineRule attribute value of auto specifies that the value of the line attribute is to be interpreted in 240ths of a single line height, which means that the net spacing is 276/240ths of a line or 1.15 lines tall. end example]

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

lineRule (Type of Spacing Between Lines)

Specifies how the spacing between lines is calculated as stored in the line attribute.

If this attribute is omitted, then it shall be assumed to be of a value auto if a line attribute value is present.

If the value of this attribute is either atLeast or exactly, then the value of the line attribute shall be interpreted as twentieths of a point, in the manner described by the simple type's values.

If the value of this attribute is auto, then the value of the line attribute shall be interpreted as 240ths of a line, in the manner described by the simple type's values.

<w:pPr>

<w:spacing w:line="276" w:lineRule="auto" />

</w:pPr>

The lineRule attribute value of auto specifies that the value of the line attribute is to be interpreted in 240ths of a single line height. end example]

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

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

</complexType>

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

This element specifies whether any hyphenation shall be performed on this paragraph by the consumer when requested using the autoHyphenation element (§2.15.1.10) in the document's settings. This element specifies whether the current paragraph should be exempted from any hyphenation which is applied by the consumer on this document.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the default hyphenation settings for the document, as specified in the autoHyphenation element, shall apply to the contents of this paragraph.

[Example: Consider a document which shall be hyphenated automatically by a consumer, since it has the autoHyphenation element set to true in its document settings. If this paragraph should be exempted from that hyphenation pass, this requirement would be specified using the following WordprocessingML:

<w:pPr>

<w:suppressAutoHyphens />

</w:pPr>

The paragraph would then be exempted from hyphenation by a consumer at display time, regardless of the hyphenation settings for the document. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

suppressLineNumbers (Suppress Line Numbers for Paragraph)

This element specifies whether line numbers shall be calculated for lines in this paragraph by the consumer when line numbering is requested using the lnNumType element (§2.6.8) in the paragraph's parent section settings. This element specifies whether the current paragraph's lines should be exempted from line numbering which is applied by the consumer on this document, not just suppressing the display of the numbering, but removing these lines from the line numbering calculation.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the default line number settings for the section, as specified in the lnNumType element shall apply to each line of this paragraph.

[Example: Consider a document with three paragraphs, each of which are displayed on five lines , all contained in a section which has the lnNumType element specified. If the second paragraph should be exempted from that line numbering, this requirement would be specified using the following WordprocessingML:

<w:pPr>

<w:suppressLineNumbers />

</w:pPr>

The paragraph would then be exempted from line by a consumer at display time, which would result in paragraph one using line numbers one through five, the second paragraph having no line numbers, and the third paragraph using line numbers six through ten. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

suppressOverlap (Prevent Text Frames From Overlapping)

This element specifies whether a text frame which intersects another text frame at display time shall be allowed to overlap the contents of the other text frame. If a text frame cannot overlap other text frames, it shall be repositioned when displayed to prevent this overlap as needed.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then overlap shall be allowed between a text frame which intersects another text frame displayed at the same location.

[Example: Consider a document with two text frames which are allowed to overlap each other. If the second text frame should overlap the contents of another text frame, that constraint would be specified via the following WordprocessingML:

<w:p>

…

</w:p>

<w:p>

<w:pPr> <w:framePr … />

<w:suppressOverlap />

</w:pPr>

…

</w:p>

The resulting text frame with the suppressOverlap property specified would never overlap any intersecting text frames. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

tab (Custom Tab Stop)

This element specifies a single custom tab stop within a set of custom tab stops applied as part of a set of customized paragraph properties in a document.

[Example: Consider a custom tab stops at 1.5" in a WordprocessingML document. This tab stop would be contained within a tab element defining the tab stop as follows:

<w:tab w:val="left" w:pos="2160" />

The tab element specifies all of the properties for the customized tab stop for the current paragraph property set. end example]

Parent Elements

tabs (§2.3.1.38)

Attributes

Description

leader (Tab Leader Character)

Specifies the character which shall be used to fill in the space created by a tab which ends at this custom tab stop. This character shall be repeated as required to completely fill the tab spacing generated by the tab character.

If this attribute is omitted, then no tab leader character shall be used.

[Example: Consider a tab stop which should be preceded by a sequence of underscore characters, as follows:

______________Text at the tab stop

This tab stop would have a leader attribute value of underscore, indicating that the tab stop shall be preceded by underscore characters as needed to fill the tab spacing. end example]

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

pos (Tab Stop Position)

Specifies the position of the current custom tab stop with respect to the current page margins.

Negative values are valid and move the tab stop into the current page margin the specified amount.

[Example: Consider a custom tab stops at 1.5" in a WordprocessingML document. This tab stop would be contained within a tab element defining the tab stop as follows:

<w:tab w:val="left" w:pos="2160" />

The pos attribute specifies that this custom tab stop shall be located 2160 points (1.5 inches) inside the starting text margin. end example]

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

val (Tab Stop Type)

Specifies the type of custom tab stop, which determines the behavior of the tab stop and the alignment which shall be applied to text entered at the current custom tab stop.

The value of clear is unique and specifies that this tab stop shall be removed when the document is next edited by a consumer which supports rendering the document contents.

[Example: Consider a custom tab stops at 1.5" in a WordprocessingML document. This tab stop would be contained within a tab element defining the tab stop as follows:

<w:tab w:val="left" w:pos="2160" />

The val attribute specifies that this custom tab stop shall align all text entered at its location to its left. end example]

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

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

</complexType>

tabs (Set of Custom Tab Stops)

This element specifies a sequence of custom tab stops which shall be used for any tab characters in the current paragraph.

As well, this property is additive - tab stops at each level in the style hierarchy are added to each other to determine the full set of tab stops for the paragraph. A hanging indent specified via the hanging attribute on the ind element (§2.3.1.12) shall also always implicitly create a custom tab stop at its location.

[Example: Consider a paragraph which contains two custom tab stops at 1.5" and 3.5", respectively. These two tab stops would be contained within a tabs element defining the set of tab stops of the paragraph as follows:

<w:pPr>

<w:tabs>

<w:tab w:val="left" w:pos="2160" />

<w:tab w:val="left" w:pos="5040" />

</w:tabs>

</w:pPr>

The tabs element specifies all of the customized tab stops for the current paragraph. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Child Elements

Subclause

tab (Custom Tab Stop)

§2.3.1.37

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

</sequence>

</complexType>

textAlignment (Vertical Character Alignment on Line)

This element specifies the vertical alignment of all text on each line displayed within a paragraph. If the line height (before any added spacing) is larger than one or more characters on the line, all characters will be aligned to each other as specified by this element.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the vertical alignment of all characters on the line shall be automatically determined by the consumer.

[Example: Consider a paragraph of text of different font sizes, as follows:

If the text on this paragraph shall be aligned based on the top point of the maximum character height, that requirement would be specified as follows in the WordprocessingML:

<w:pPr>

<w:textAlignment w:val="top" />

</w:pPr>

The resulting text would be top aligned, as follows:

The characters are all aligned to the maximum character extent on the line. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Vertical Character Alignment Position)

Specifies the type of vertical alignment which shall be used to align the characters on each line in the current paragraph.

[Example: Consider a paragraph of text of different font sizes which shall be aligned based on the baseline point of each character in each line. This requirement would be specified as follows in the WordprocessingML:

<w:pPr>

<w:textAlignment w:val="baseLine" />

</w:pPr>

The resulting text would be aligned to the baseline for each character on the line. end example]

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

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

</complexType>

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

This element specifies whether, for paragraphs in a text box, the surrounding text shall be allowed to overlap with the empty text box boundaries and tight wrap to the extents of the text within the text box.

This element shall only be read for paragraphs which are contained within a text box (have a txbxContent ancestor), ignored otherwise.

If the parent text box does not meet the following three criteria, then this property has no effect:

The text box wrapping must be set to tight

The text box border must not be set

The text box shading must not be set

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then paragraphs in a text box have no tight wrapping overrides, and text shall wrap to the extents of the text box.

[Example: Consider a document with a tight wrapped text box which extends two-thirds of the way across the page, as follows:

The surrounding text is tightly wrapped to the extents of the text box. If the consumer shall tight wrap to the extents of the text, that requirement would be specified using the following WordprocessingML:

<w:pPr>

<w:textboxTightWrap w:val="all" />

</w:pPr>

This would result in the following display of the content:

The resulting paragraphs within the textbox use the textboxTightWrap element to specify that text should be tightly wrapped to the paragraph's extents. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Lines to Tight Wrap to Paragraph Extents)

Specifies the lines in the parent paragraph which shall allow the text to be tight wrapped to the paragraph (and not the text box) extents when displaying the document.

[Example: Consider a paragraph in a text box which meets the criteria specified above which shall allow wrapping to the text extents on its first line only. That requirement would be specified using the following WordprocessingML:

<w:pPr>

<w:textboxTightWrap w:val="firstLineOnly" />

</w:pPr>

The resulting paragraph would allow text to tightly wrap to the contents of its first line only. All other lines would wrap to the text box's extents. end example]

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

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

</complexType>

textDirection (Paragraph Text Flow Direction)

This element specifies the direction of the text flow for this paragraph.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the paragraph shall inherit the text flow settings from the parent section.

[Example: Consider a document with a paragraph in which text should flow bottom to top vertically, and left to right horizontally. This setting would be specified with the following WordprocessingML:

<w:pPr> <w:textFlow w:val="btLr" /></w:pPr>

The textFlow element specifies via the btLr value in the val attribute that the text flow should go bottom to top, and left to right. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (Direction of Text Flow)

Specifies the direction of the text flow for this object.

[Example: Consider a document with a section in which text shall flow bottom to top vertically, and left to right horizontally. This setting requires the following WordprocessingML:

<w:sectPr> … <w:textDirection w:val="btLr" /></w:sectPr>

The textDirection element specifies via the btLr value in the val attribute that the text flow shall go bottom to top, and left to right. end example]

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

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

</complexType>

top (Paragraph Border Above Identical Paragraphs)

This element specifies the border which shall be displayed above a set of paragraphs which have the same set of paragraph border settings.

To determine if any two adjoining paragraphs shall have an individual top and bottom border or a between border, the set of borders on the two adjoining paragraphs are compared. If the border information on those two paragraphs is identical for all possible paragraphs borders, then the between border is displayed. Otherwise, the final paragraph shall use its bottom border and the following paragraph shall use its top border, respectively. If this border specifies a space attribute, that value determines the space above the text (ignoring any spacing above) which should be left before this border is drawn, specified in points.

[Example: Consider the following two paragraphs' WordprocessingML definition:

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>First paragraph.</w:t>

</w:r>

</w:p>

<w:p>

<w:pPr>

<w:pBdr>

<w:top w:val="single" w:sz="24" w:space="1" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:left w:val="single" w:sz="24" w:space="4" w:color="B97034" w:themeColor="accent6" w:themeShade="BF" />

<w:bottom w:val="single" w:sz="24" w:space="0" w:color="F2DCDB" w:themeColor="accent2" w:themeTint="33" />

<w:right w:val="single" w:sz="24" w:space="4" w:color="C3D69B" w:themeColor="accent3" w:themeTint="99" />

<w:between w:val="single" w:sz="24" w:space="1" w:color="4F81BD" w:themeColor="accent1" />

</w:pBdr>

</w:pPr>

<w:r>

<w:t>Second paragraph.</w:t>

</w:r>

</w:p>

Since the paragraph border is different between the two paragraphs (the bottom space value goes from 1 to 0), paragraph two uses its top border, which is located one point above the text in that paragraph. end example]

Parent Elements

pBdr (§2.3.1.24)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

topLinePunct (Compress Punctuation at Start of a Line)

This element specifies whether punctuation shall be compressed when it appears as the first character in a line, allowing subsequent characters on the line to be move in accordingly.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then punctuation shall not be compressed in this paragraph, even when it appears at the start of a line.

[Example: Consider a paragraph which should allow punctuation at the start of a line to be compressed, in order to prevent it from taking up unnecessary space. This constraint is specified using the following WordprocessingML:

<w:pPr>

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

</w:pPr>

The topLinePunct element specifies that this compression shall be allowed when displaying this paragraph. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

widowControl (Allow First/Last Line to Display on a Separate Page)

This element specifies whether a consumer shall prevent a single line of this paragraph from being displayed on a separate page from the remaining content at display time by moving the line onto the following page.

When displaying a paragraph in a page, it is sometimes the case that the first line of that paragraph would display as the last line on one page, and all subsequent lines would display on the following page. This property ensures that a consumer shall move the single line to the following page as well to prevent having one line on its own page. As well, if a single line appears at the top of a page, a consumer shall move the preceding line onto the following page as well, to prevent a single line from being displayed on a separate page.

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then this paragraph shall prevent a single line from being shown on a separate page whenever it would normally occur.

[Example: Consider a document with a paragraph which shall be shown on four lines at display time. If this paragraph would normally be laid out with its first line at the bottom of one page, and its following lines on the next page, as follows:

This property would ensure that the default behavior for each paragraph prevented this, by moving this line onto the following paragraph as follows:

However, if this default is overridden by specifying the following WordprocessingML:

<w:pPr>

<w:widowControl w:val="off" />

</w:pPr>

The specifying of the widowControl element with value off means that the consumer displaying this document shall not move the first line onto a separate page if it would be separated from all other lines (the first picture above). end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

wordWrap (Allow Line Breaking At Character Level)

This element specifies whether a consumer shall break Latin text which exceeds the text extents of a line by breaking the word across two lines (breaking on the character level) or by moving the word to the following line (breaking on the word level).

If this element is omitted on a given paragraph, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then this paragraph shall break Latin words at the word level, not the character level when it is displayed.

[Example: Consider a paragraph whose first line ends with the word world, where the text extents for that line would normally fall between the letter o and the letter r. If this element is omitted, a producer would normally move the entire word world to the following line, since the word does not fit within the first line's text extents. However, if this document should allow words to be broken at the character level, that constraint would be specified as follows:

<w:pPr>

<w:wordWrap w:val="off" />

</w:pPr>

The resulting paragraph specifies that wordWrap is turned off, therefore the word "world" would be broken into two lines between the exact two characters (o and r) that match the text extents. end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.3.1.25); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

Run

The next level of the document hierarchy is the run, which defines a region of text with a common set of properties, represented by the r element (§2.3.2.23). An r element allows the producer to specify a single set of formatting properties, applying the same information to all the contents of the run.

Just as a paragraph can have properties, so too can a run. All of the elements inside an r element have their properties controlled by a corresponding optional rPr run properties element (§2.7.8.1; §2.3.2.26), which must be the first child of the r element. In turn, the rPr element is a container for a set of property elements that are applied to the rest of the children of the r element. [Note: The elements inside the rPr container element allow the consumer to control whether the content in the following run content is bold, underlined, or visible, for example. end note]

[Example: Consider the following run within a WordprocessingML document:

<w:r> <w:rPr> <w:b/> <w:i/> </w:rPr> <w:t>quick</w:t></w:r>

The run specifies two formatting properties in its run contents: bold and italic. These properties are therefore applied to all content within this run. end example]

b (Bold)

This element specifies whether the bold property shall be applied to all non-complex script characters in the contents of this run when displayed in a document.

This formatting property is a toggle property, which specifies that its behavior differs between its use within a style definition and its use as direct formatting. When used as part of a style definition, setting this property shall toggle the current state of that property as specified up to this point in the hierarchy (i.e. applied to not applied, and vice versa). Setting it to false (or an equivalent) shall result in the current setting remaining unchanged. However, when used as direct formatting, setting this property to true or false shall set the absolute state of the resulting property.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then bold shall not be applied to non-complex script characters.

[Example: Consider a run of text which shall have the b property explicitly turned off for the non complex script contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:b w:val="false"/></w:rPr>

This run explicitly declares that the b property is false for the non-complex script contents of this run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

bCs (Complex Script Bold)

This element specifies whether the bold property shall be applied to all complex script characters in the contents of this run when displayed in a document.

[Example: Consider a run of text which shall have the bCs property (bold) explicitly turned on for the complex script contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:bCs w:val="true"/></w:rPr>

This run explicitly declares that the bCs property is true , so bold is turned on for the complex script contents of this run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

bdr (Text Border)

This element specifies information about the border applied to the text in the current run.

The first piece of information specified by the bdr element is that the current shall have a border when displayed. This information is specified simply by the presence of the bdr element in run's properties.

The second piece of information concerns the set of runs which share the current run border. This is determined based on the attributes on the bdr element. If the set of attribute values specifies on two adjacent runs is identical, then those two runs shall be considered to be part of the same run border group and rendered within the same set of borders in the document.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then no run border shall be applied to the text in this run.

[Example: Consider a document in which the following two runs are located adjacent to one another:

<w:r>

<w:rPr>

<w:bdr w:val="single" w:sz="36" w:space="0" w:color="B8CCE4" w:themeColor="accent1" w:themeTint="66" />

</w:rPr>

<w:t xml:space="preserve">run one</w:t>

</w:r>

<w:r >

<w:rPr>

<w:b />

<w:bdr w:val="single" w:sz="36" w:space="0" w:color="B8CCE4" w:themeColor="accent1" w:themeTint="66" />

</w:rPr>

<w:t>run two</w:t>

</w:r>

These two runs, although each is distinct, are combined when rendering the text border because the bdr elements are identical between the two runs. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

caps (Display All Characters As Capital Letters)

This element specifies that any lowercase characters in this text run shall be formatted for display only as their capital letter character equivalents. This property does not affect any non-alphabetic character in this run, and does not change the Unicode character for lowercase text, only the method in which it is displayed.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the characters are not formatted as capital letters.

This element shall not be present with the smallCaps (§2.3.2.31) property on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider the words Hello World, which shall be displayed in all capital letters in a document. This constraint is specified as follows in the WordprocessingML:

<w:r>

<w:rPr>

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

</w:rPr>

<w:t>Hello World</w:t>

</w:r>

This run will display as HELLO WORLD, even though the lowercase characters are used in the run contents due to the use of the caps element. If this property is removed, the original character forms will be displayed (they are not lost). end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

color (Run Content Color)

This element specifies the color which shall be used to display the contents of this run in the document.

This color may be explicitly specified, or set to allow the consumer to automatically choose an appropriate color based on the background color behind the run's content.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the characters are set to allow the consumer to automatically choose an appropriate color based on the background color behind the run's content.

[Example: Consider a run of text which should be displayed using the accent3 theme color from the document’s Theme part. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:color w:themeColor=”accent3” />

</w:rPr>

The color attribute specifies that the run shall use the accent3 theme color. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

themeColor (Run Content Theme Color)

Specifies a theme color which should be applied to the current run.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows for color information to be set centrally in the document.

If the themeColor attribute is specified, then the val attribute is ignored for this run.

<w:rPr>

<w:color w:themeColor=”accent3” />

</w:rPr>

The color attribute specifies that the run shall use the accent3 theme color. end example]

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

themeShade (Run Content Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this run’s contents.

If the themeShade is supplied, then it is applied to the RGB value of the theme color to determine the final color applied to this run.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a run in a document. This shade is calculated as follows:

Te resulting themeShade value in the file format would be 66. end example]

Given a input red, green, or blue color value C (from 0-255), an output color value of C' (from 0-255), and a shade value S (from 0-100), the shade is applied as follows:

[Example: Consider a document with a run using the accent6 theme color, whose RGB value (in RRGGBB hex format) is F79646.

The hex value for the green component is 96 - 150 in decimal. Applying the shade formula with shade of 50%, the output decimal value of the green component is 75, or a hex value of 4B. This transformed value can be seen in the resulting run color WordprocessingML's val attribute:

<w:color w:val="7B4B23" w:themeColor="accent6" w:themeShade="80" />

end example]

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

themeTint (Run Content Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this run’s contents.

If the themeTint is supplied, then it is applied to the RGB value of the theme color to determine the final color applied to this run.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a run in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given a input red, green, or blue color value C (from 0-255), an output color value of C' (from 0-255), and a tint value T (from 0-100), the tint is applied as follows:

[Example: Consider a document with a run using the accent1 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The hex value for the green component is 50 - 80 in decimal. Applying the tint formula with tint of 60%, the output decimal value of the green component is 150, or a hex value of 96. This transformed value can be seen in the resulting run color's WordprocessingML val attribute:

<w:color w:val="D99694" w:themeColor="accent1" w:themeTint="99" />

end example]

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

val (Run Content Color)

Specifies the color for this run.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the run color as appropriate.

If the run specifies the use of a theme color via the themeColor attribute, then this value is superseded by the theme color value.

[Example: Consider a run color with value auto, as follows:

<w:rPr>

<w:color ... w:val="auto" />

</w:rPr>

This color therefore may be automatically be modified by a consumer as appropriate, for example, in order to ensure that the run contents can be distinguished against the page's background color. end example]

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

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

</complexType>

cs (Use Complex Script Formatting on Run)

This element specifies whether the contents of this run shall be treated as complex script text regardless of their Unicode character values when determining the formatting for this run.

This means that a consumer shall use the complex script formatting applied to the run [Example: The bCs value (§2.3.2.2), not the b value (§2.3.2.1). end example] when determining the resulting formatting properties.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the run contents are set to complex script based on the Unicode character positions of the content.

[Example: Consider the following run of English text in a WordprocessingML document:

<w:r>

<w:rPr>

<w:bCs/>

<w:i/>

<w:cs/>

</w:rPr>

<w:t>some English text</w:t>

</w:r>

This run has bold applied to complex script characters, and italics applied to non-complex script characters. However, since the cs property is set, the text in this run shall be treated as complex script text when determining the resulting formatting. Therefore, the run will have bold formatting, but no italic formatting when displayed. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

dstrike (Double Strikethrough)

This element specifies that the contents of this run shall be displayed with two horizontal lines through each character displayed on the line.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then double strikethrough shall not be applied to the contents of this run.

This element shall not be present with the strike (§2.3.2.35) property on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider a run of text which shall have the dstrike property explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:dstrike w:val="true"/></w:rPr>

This run explicitly declares that the dstrike property is true, so the contents of this run will have two horizontal strikethrough lines. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

eastAsianLayout (East Asian Typography Settings)

This element specifies any East Asian typography settings which shall be applied to the contents of the run.

The specific typography settings represented by this element include the two lines in one and horizontal in vertical text options.

The two lines in one setting specifies that the characters in this run should be written out on a single line in the document by creating two sub-lines within the regular line, and laying out this text equally between those sub lines.

[Example: Consider a paragraph with the text two lines in one, which shall be displayed within a single logical line in the document. This constraint would be specified as follows in the WordprocessingML:

<w:r>

<w:rPr>

<w:eastAsianLayout w:id="1" w:combine="on" />

</w:rPr>

<w:t>two lines in one</w:t>

</w:r>

The resulting text would be displayed on two sub lines within the other text on this line, like this:

end example]

The horizontal in vertical setting specifies that characters in this run should be rendered with a 90 degree rotation to the left from all other contents of the line when displayed in the document, while keeping the text on the same line as all other text in the paragraph.

[Example: Consider a paragraph with the text this word is vertical, of which the word vertical shall be displayed vertically within the document. This constraint would be specified as follows in the WordprocessingML:

<w:r>

<w:rPr>

<w:eastAsianLayout w:id="2" w:vert="on" />

</w:rPr>

<w:t>vertical</w:t>

</w:r>

The resulting text would be displayed with a 90 degree rotation from the other text content. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

combine (Two Lines in One)

Specifies whether the contents of the current run should be combined into one line using the two lines in one logic described above in the parent element.

If this attribute is omitted, then this run shall not be displayed on two sub lines.

<w:r>

<w:rPr>

<w:eastAsianLayout w:id="1" w:combine="on" />

</w:rPr>

<w:t>two lines in one</w:t>

</w:r>

The resulting text would be displayed on two sub lines within the other text on this line. end example]

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

combineBrackets (Display Brackets Around Two Lines in One)

Specifies that the two lines in one text should be enclosed within a pair of brackets when displayed. This attribute's values determine the bracket style to put around combined text.

If this attribute is not specified, then no brackets shall be placed around this content when displayed in the document. If the combine attribute is not specified, then this attribute is ignored.

[Example: Consider a paragraph with the text two lines in one, which shall be displayed within a single logical line in the document and enclosed in curly brackets. This constraint would be specified as follows in the WordprocessingML:

<w:r>

<w:rPr>

<w:eastAsianLayout w:id="1" w:combine="on" w:combineBrackets="curly"/>

</w:rPr>

<w:t>two lines in one</w:t>

</w:r>

The resulting text would be displayed on two sub lines within the other text on this line and enclosed within curly brackets when displayed. end example]

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

id (East Asian Typography Run ID)

Specifies a unique ID which shall b used to link multiple runs containing eastAsianLayout element to each other to ensure that their contents are correctly displayed in the document.

This means that multiple runs which are broken apart due to differences in formatting can be identified as belonging to the same grouping in terms of eastAsianLayout properties, although they are separated into multiple runs of text.

[Example: Consider the following three runs in a document:

<w:r>

<w:rPr>

<w:asianLayout w:id="-1552701694" w:combine="lines" w:combineBrackets="curly" />

</w:rPr>

<w:t>two</w:t>

</w:r>

<w:r>

<w:rPr>

<w:u w:val="single" w:color="4F81BD" w:themeColor="accent1" />

<w:asianLayout w:id="-1552701694" w:combine="lines" w:combineBrackets="curly" />

</w:rPr>

<w:t>lines in</w:t>

</w:r>

<w:r>

<w:rPr>

<w:asianLayout w:id="-1552701694" w:combine="lines" w:combineBrackets="curly" />

</w:rPr>

<w:t>one</w:t>

</w:r>

Although there are three runs of content, all three regions shall be combined into a single two lines in one region based on the identical value used in the id attribute for all three runs. end example]

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

vert (Horizontal in Vertical (Rotate Text))

Specifies that characters in this run should be rendered with a 270 degree rotation to the left from all other contents of the line when displayed in the document as described above.

If this attribute is omitted, then the contents of this run shall not be rotated with respect to the normal text flow.

<w:r>

<w:rPr>

<w:eastAsianLayout w:id="2" w:vert="on" />

</w:rPr>

<w:t>vertical</w:t>

</w:r>

The resulting text would be displayed with a 270 degree rotation from the other text content. end example]

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

vertCompress (Compress Rotated Text to Line Height)

Specifies whether the rotated text shall be compressed at display time in order to ensure that it fits into the existing line height without increasing the overall height of the line.

If the vert attribute is not specified, then this attribute is ignored. If this attribute is omitted, then text shall not be compressed in order to fit into the existing height of the line when it is rotated.

[Example: Consider a paragraph with the text this word is vertical, of which the word vertical shall be displayed vertically within the document but shall not change the height of the line. This constraint would be specified as follows in the WordprocessingML:

<w:r>

<w:rPr>

<w:eastAsianLayout w:id="2" w:vert="true" vertCompress="true" />

</w:rPr>

<w:t>vertical</w:t>

</w:r>

The resulting text would be compressed in order to fit the height of the line as defined by all non-compressed characters. end example]

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

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

</complexType>

effect (Animated Text Effect)

This element specifies an animated text effect which should be displayed when rendering the contents of this run. This effect is rendered around the extents of the text in the run in the same location as a run border with zero pixels of padding would be rendered (if such a run border was present).

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then no text effect shall be applied to the contents of this run.

[Example: Consider a run of text which shall have an animated text effect consisting of multiple colored flashing lights (see possible attribute values for descriptions of each effect). This constraint is specified using the following WordprocessingML:

<w:rPr> <w:effect w:val="lights"/></w:rPr>

This run explicitly declares that the effect property is lights, so the contents of this run will have an animated lights text effect. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Animated Text Effect Type)

Specifies the type of animated text effect which shall be applied to this text run.

[Example: Consider a run of text which shall have an animated text effect consisting of multiple colored flashing lights. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:effect w:val="lights"/></w:rPr>

This run explicitly declares a type of text effect, using the val property, of lights, so the contents of this run will have the animated lights text effect. end example]

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

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

</complexType>

em (Emphasis Mark)

This element specifies the emphasis mark which shall be displayed for each non-space character in this run. An emphasis mark is an additional character that is rendered above or below the main character glyph as specified by the contents of the val attribute.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then no emphasis mark shall be added to each character in the contents of this run.

[Example: Consider a run of text which shall have a dot underneath each character as an emphasis mark. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:em w:val="dot"/></w:rPr>

This run explicitly declares that the emphasis mark type is dot, so the contents of this run will have a dot emphasis mark above each character. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Emphasis Mark Type)

Specifies the emphasis mark type used for each character in this run.

[Example: Consider a run of text which shall have a dot underneath each character as an emphasis mark. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:em w:val="dot"/></w:rPr>

This run explicitly declares that the em type is dot, so the contents of this run will have a dot emphasis mark beneath each character. end example]

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

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

</complexType>

emboss (Embossing)

This element specifies that the contents of this run should be displayed as if embossed, which makes text appear as if it is raised off the page in relief.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then embossing shall not be applied to the contents of this run.

This element shall not be present with either the imprint (§2.3.2.16) or outline (§2.3.2.21) properties on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider a run of text which shall have the emboss property explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:emboss w:val="true"/></w:rPr>

This run explicitly declares that the emboss property is true, so the contents of this run will appear embossed. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

fitText (Manual Run Width)

This element specifies that the contents of this run shall not be automatically displayed based on the width of its contents, rather its contents shall be resized to fit the width specified by the val attribute. This expansion/contraction shall be performed by equally increasing/decreasing the size of each character in this run's contents when displayed.

If this element is omitted, then the contents of this run shall be displayed based on the size of its contents.

[Example: Consider a document with a run which shall be displayed in exactly one-half inch of space, regardless of its contents. This constraint would be specified using the following WordprocessingML:

<w:r>

<w:rPr>

<w:fitText w:id="50" w:val="720" />

</w:rPr>

<w:t>This text shall be displayed in one-half of an inch.</w:t>

</w:r>

The resulting run contents shall be displayed in exactly 720 twentieths of a point (one half of an inch) when displayed in a document. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

id (Fit Text Run ID)

Specifies a unique ID which shall be used to link multiple contiguous runs containing fitText elements to each other to ensure that their contents are correctly merged into the specified width in the document.

This means that multiple runs which are broken apart due to differences in formatting can be identified as belonging to the same grouping in terms of fitText properties, although they are multiple runs of text in the WordprocessingML.

If the runs are not contiguous, then the id attribute is ignored, and the runs are not linked.

If this attribute is omitted, then this run has no id and shall not be linked with any other run in the parent paragraph.

[Example: Consider the following three runs in a document, which should be fit into exactly one inch at display time:

<w:r>

<w:rPr>

<w:fitText w:id="99" w:val="1440" />

</w:rPr>

<w:t>fit this into</w:t>

</w:r>

<w:r>

<w:rPr>

<w:b/>

<w:fitText w:id="99" w:val="1440" />

</w:rPr>

<w:t>one</w:t>

</w:r>

<w:r>

<w:rPr>

<w:fitText w:id="99" w:val="1440" />

</w:rPr>

<w:t>inch</w:t>

</w:r>

Although there are three runs of content, all three regions shall be combined into a single fit text region (e.g. they all fit into one inch, rather than one inch each) based on the identical value used in the id attribute for all three runs. end example]

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

val (Value)

This attribute specifies the exact width of space which this run shall be fit into when displayed in the document.

<w:r>

<w:rPr>

<w:fitText w:id="50" w:val="720" />

</w:rPr>

<w:t>This text shall be displayed in one-half of an inch.</w:t>

</w:r>

The resulting run contents shall be displayed in exactly 720 twentieths of a point (one half of an inch) when displayed in a document. end example]

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

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

</complexType>

highlight (Text Highlighting)

This element specifies a highlighting color which is applied as a background behind the contents of this run.

If this run has any background shading specified using the shd element (§2.3.2.30), then the background shading shall be superseded by the highlighting color when the contents of this run are displayed.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then text highlighting shall not be applied to the contents of this run.

[Example: Consider a run within a paragraph which has run shading applied as well as yellow text highlighting using the highlight element. This formatting is specified using the following WordprocessingML:

<w:rPr>

<w:highlight w:val="yellow" />

<w:shd w:themeFill="accent2" w:themeFillTint="66" />

</w:rPr>

The resulting run would have yellow highlighting visible over its contents, as the highlighting supersedes the shading for the contents of the run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Highlighting Color)

Specifies the color of the text highlighting which shall be applied to the contents of this run.

[Example: Consider a text run which shall be displayed with colored text highlighting. This highlighting would be specified using the following WordprocessingML:

<w:rPr>

<w:highlight w:val="red" />

</w:rPr>

The resulting text highlighting would be red, as this is the color specified by the val attribute. end example]

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

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

</complexType>

i (Italics)

This element specifies whether the italic property should be applied to all non-complex script characters in the contents of this run when displayed in a document.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy .If this element is never applied in the style hierarchy, then italics shall not be applied to non-complex script characters.

[Example: Consider a run of text which shall have the i property explicitly turned on for the non-complex script contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:i /></w:rPr>

This run explicitly declares that the i property is true for the non-complex script contents of this run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

iCs (Complex Script Italics)

This element specifies whether the italic property should be applied to all complex script characters in the contents of this run when displayed in a document.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then italics shall not be applied to complex script characters.

[Example: Consider a run of text which shall have the iCs property explicitly turned on for the complex script contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:iCs w:val="true"/></w:rPr>

This run explicitly declares that the iCs property is true, so italics are turned on for the complex script contents of this run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

imprint (Imprinting)

This element specifies that the contents of this run should be displayed as if imprinted, which makes text appear to be imprinted or pressed into page (also referred to as 'engrave').

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then imprinting shall not be applied to the contents of this run.

This element shall not be present with either the emboss (§2.3.2.11) or outline (§2.3.2.21) properties on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider a run of text which shall have the imprint property explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:imprint w:val="true"/></w:rPr>

This run explicitly declares that the imprint property is true, so the contents of this run will appear imprinted. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

kern (Font Kerning)

This element specifies whether font kerning shall be applied to the contents of this run. If it is specified, then kerning shall be automatically adjusted when displaying characters in this run as needed.

The val attribute specifies the smallest font size which shall have its kerning automatically adjusted if this setting is specified. If the font size in the sz element (§2.3.2.36) is smaller than this value, then no font kerning shall be performed.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then font kerning shall not be applied to the contents of this run.

[Example: Consider the following WordprocessingML run which has font kerning properties specified:

<w:r>

<w:rPr>

<w:sz w:val="22" />

<w:kern w:val="28" />

</w:rPr>

</w:r>

Even though font kerning is turned on via the kern element, the contents of this run shall not be kerned because that settings only applied to font sizes of 14 points (28 half-points) or larger. If the kern element's val attribute was less than or equal to the sz element's val attribute, then kerning would be applied:

<w:r>

<w:rPr>

<w:sz w:val="22" />

<w:kern w:val="22" />

</w:rPr>

</w:r>

end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Half Point Measurement)

Specifies a positive measurement specified in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:sz w:val="28" />

</w:rPr>

The value of the val attribute is the font size of the run's contents.

However, consider the following fragment:

<w:rPr>

<w:kern w:val="30" />

</w:rPr>

In this case, the value in the val attribute is the minimum size for which font characters shall be automatically kerned.

In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

lang (Languages for Run Content)

This element specifies the languages which shall be used to check spelling and grammar (if requested) when processing the contents of this run.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the languages for the contents of this run shall be automatically determined based on their contents using any method desired.

[Example: Consider a run which contains both Latin and complex script characters in its contents. If those contents should be interpreted as French (Canada) and Hebrew, respectively, that requirement would be specified as follows in the resulting WordprocessingML:

<w:r>

<w:rPr>

<w:lang w:val="fr-CA" w:bidi="he-IL" />

</w:rPr>

</w:r>

The resulting run specifies that any complex script contents shall be spell and grammar checked as if they were Hebrew, and any Latin character contents shall be spell and grammar checked as if they were French (Canada). end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

bidi (Complex Script Language)

Specifies the language which shall be used when processing the contents of this run which use complex script characters, as determined by the Unicode character values of the run content.

If this attribute is omitted, then the languages for the contents of this run using complex script characters shall be automatically determined based on their contents using any appropriate method.

[Example: Consider a run which contains complex script characters in its contents. If those contents should be interpreted as Hebrew, that requirement would be specified as follows in the resulting WordprocessingML:

<w:r>

<w:rPr>

<w:lang w:bidi="he-IL" />

</w:rPr>

</w:r>

The resulting run specifies that any complex script contents shall be spell and grammar checked using a Hebrew dictionary and grammar engine, if one is available. end example]

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

eastAsia (East Asian Language)

Specifies the language which shall be used when processing the contents of this run which use East Asian characters, as determined by the Unicode character values of the run content.

If this attribute is omitted, then the languages for the contents of this run using East Asian characters shall be automatically determined based on their contents using any appropriate method.

[Example: Consider a run which contains East Asian characters in its contents. If those contents should be interpreted as Korean, that requirement would be specified as follows in the resulting WordprocessingML:

<w:r>

<w:rPr>

<w:lang w:bidi="ko-KR" />

</w:rPr>

</w:r>

The resulting run specifies that any complex script contents shall be spell and grammar checked using a Korean dictionary and grammar engine, if one is available. end example]

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

val (Latin Language)

Specifies the language which shall be used to check spelling and grammar (if requested) when processing the contents of this run which use Latin characters, as determined by the Unicode character values of the run content.

If this attribute is omitted, then the languages for the contents of this run using Latin characters shall be automatically determined based on their contents using any appropriate method.

[Example: Consider a run which contains Latin characters in its contents. If those contents should be interpreted as English (Canada), that requirement would be specified as follows in the resulting WordprocessingML:

<w:r>

<w:rPr>

<w:lang w:bidi="en-CA" />

</w:rPr>

</w:r>

The resulting run specifies that any complex script contents shall be spell and grammar checked using a English (Canada) dictionary and grammar engine, if one is available. end example]

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

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

</complexType>

noProof (Do Not Check Spelling or Grammar)

This element specifies that the contents of this run shall not report any errors when the document is scanned for spelling and grammar. [Note: It is entirely at the consumer's/producer's discretion whether this is done by not checking the region for spelling and grammar, or simply by suppressing the results. end note]

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then spelling and grammar error shall not be suppressed on the contents of this run.

[Example: Consider a run of text which shall not ever have spelling or grammar errors reported for the contents of the run, for example, the XML fragments included in this Specification. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:noProof w:val="true"/></w:rPr>

This run explicitly declares that the noProof property is true, so the contents of this run will never report spelling or grammar errors. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

oMath (Office Open XML Math)

This element specifies that this run contains WordprocessingML which shall be handled as though it was Office Open XML Math.

[Rationale: Like other run properties may be applied to the glyph representing the paragraph mark, it is possible to create an Office Open XML Math equation on an empty paragraph as well. Since that paragraph mark must be defined by WordprocessingML, it is not possible to store the paragraph using the Office Open XML Math markup. Instead, this run property is stored on the paragraph mark's run properties to indicate that the paragraph mark is part of an Office Open XML Math equation. For example, the first paragraph below is stored as Office Open XML Math:

The paragraph must be a p (§2.3.1.22) element, but that would mean the data loss of the Math markup when saving as a WordprocessingML package. In order to prevent that data loss, this property stores the Math property as a run property. end rationale]

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then this run shall not be treated as Office Open XML Math.

This property may be applied to any run, but that should only introduce the semantic that the run is math in the user interface, and shall not change the appearance of the text.

[Example: Consider a paragraph in WordprocessingML where the paragraph mark glyph (the pilcrow mark - ¶) has been formatted as Math. Since this mark is not an actual run, it cannot be written out in the Office Open XML Math syntax, and must be written out as a property on the actual run as follows:

<w:pPr> <w:rPr> <w:oMath /> </w:rPr></w:pPr>

This property is therefore used to roundtrip the math setting on this paragraph mark character. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

outline (Display Character Outline)

This element specifies that the contents of this run should be displayed as if they have an outline, by drawing a one pixel wide border around the inside and outside borders of each character glyph in the run.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then outline shall not be applied to the contents of this run.

This element shall not be present with either the emboss (§2.3.2.11) or imprint (§2.3.2.16) properties on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider a run of text which shall have the outline property explicitly turned off for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:outline w:val="false"/></w:rPr>

This run explicitly declares that the outline property is false, so the contents of this run will not appear as if they have an exterior outline around them. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

position (Vertically Raised or Lowered Text)

This element specifies the amount by which text shall be raised or lowered for this run in relation to the default baseline of the surrounding non-positioned text. This allows the text to be repositioned without altering the font size of the contents.

If the val attribute is positive, then the parent run shall be raised above the baseline of the surrounding text by the specified number of half-points. If the val attribute is negative, then the parent run shall be lowered below the baseline of the surrounding text by the specified number of half-points.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the text shall not be raised or lowered relative to the default baseline location for the contents of this run.

[Example: Consider a run which shall be positioned 12 points above the default baseline location when displaying its contents. This requirement would be specified using the following WordprocessingML:

<w:rPr>

<w:position w:val="24" />

</w:rPr>

The resulting run is positioned 24 half-points above the default baseline location because the contents of the val attribute are positive. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Signed Half-Point Measurement)

Specifies a positive or negative measurement in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:position w:val="-12" />

</w:rPr>

In this case, the value in the val attribute is amount by which the specified run shall be raised or lowered compared to the baseline of the surrounding text.

In all cases, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

r (Text Run)

This element specifies a run of content in the parent field, hyperlink, custom XML element, structured document tag, smart tag, or paragraph.

The contents of a run in a WordprocessingML document shall consist of any combination of run content.

[Example: Consider a basic WordprocessingML paragraph with a pair of runs. This run would be expressed as follows:

<w:document>

<w:body>

<w:p>

<w:r>

<w:t>Text</w:t>

</w:r>

<w:fldSimple w:instr="AUTHOR">

<w:r>

<w:t>Author Name</w:t>

</w:r>

</w:fldSimple>

</w:p>

</w:body>

</w:document>

The r element is the container for all of the content in the run, which in this example includes both a run in the paragraph and a run within a simple field. end example]

Parent Elements

customXml (§2.5.1.5); del (§2.13.5.12); fldSimple (§2.16.21); hyperlink (§2.16.24); ins (§2.13.5.20); moveFrom (§2.13.5.21); moveTo (§2.13.5.26); p (§2.3.1.22); rt (§2.3.3.23); rubyBase (§2.3.3.26); sdtContent (§2.5.2.35); smartTag (§2.5.1.9)

Child Elements

Subclause

annotationRef (Comment Information Block)

§2.13.4.1

br (Break)

§2.3.3.1

commentReference (Comment Content Reference Mark)

§2.13.4.5

continuationSeparator (Continuation Separator Mark)

§2.11.1

cr (Carriage Return)

§2.3.3.4

dayLong (Date Block - Long Day Format)

§2.3.3.5

dayShort (Date Block - Short Day Format)

§2.3.3.6

delInstrText (Deleted Field Code)

§2.16.13

delText (Deleted Text)

§2.3.3.7

drawing (DrawingML Object)

§2.3.3.9

endnoteRef (Endnote Reference Mark)

§2.11.6

endnoteReference (Endnote Reference)

§2.11.7

fldChar (Complex Field Character)

§2.16.18

footnoteRef (Footnote Reference Mark)

§2.11.13

footnoteReference (Footnote Reference)

§2.11.14

instrText (Field Code)

§2.16.25

lastRenderedPageBreak (Position of Last Calculated Page Break)

§2.3.3.13

monthLong (Date Block - Long Month Format)

§2.3.3.15

monthShort (Date Block - Short Month Format)

§2.3.3.16

noBreakHyphen (Non Breaking Hyphen Character)

§2.3.3.18

object (Inline Embedded Object)

§2.3.3.19

pgNum (Page Number Block)

§2.3.3.20

pict (VML Object)

§2.3.3.21

ptab (Absolute Position Tab Character)

§2.3.3.22

rPr (Run Properties)

§2.3.2.25

ruby (Phonetic Guide)

§2.3.3.24

separator (Footnote/Endnote Separator Mark)

§2.11.23

softHyphen (Optional Hyphen Character)

§2.3.3.28

sym (Symbol Character)

§2.3.3.29

t (Text)

§2.3.3.30

tab (Tab Character)

§2.3.3.31

yearLong (Date Block - Long Year Format)

§2.3.3.32

yearShort (Date Block - Short Year Format)

§2.3.3.33

Attributes

Description

rsidDel (Revision Identifier for Run Deletion)

Specifies a unique identifier used to track the editing session when the run was deleted from the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidR (Revision Identifier for Run)

Specifies a unique identifier used to track the editing session when the run was added to the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidRPr (Revision Identifier for Run Properties)

Specifies a unique identifier used to track the editing session when the run properties were last modified in the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

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

</sequence>

</complexType>

rFonts (Run Fonts)

This element specifies the fonts which shall be used to display the text contents of this run. Within a single run, there may be up to four types of content present which shall each be allowed to use a unique font:

ASCII

High ANSI

Complex Script

East Asian

The use of each of these fonts shall be determined by the Unicode character values of the run content, unless manually overridden via use of the cs element (§2.3.2.6).

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the text shall be displayed in any default font which supports each type of content.

[Example: Consider a single text run with both Arabic and English text, as follows:

English العربية

This content may be expressed in a single WordprocessingML run:

<w:r> <w:t>English العربية</w:t></w:r>

Although it is in the same run, the contents are in different font faces by specifying a different font for ASCII and CS characters in the run:

<w:r> <w:rPr> <w:rFonts w:ascii="Courier New" w:cs="Times New Roman" /> </w:rPr> <w:t>English العربية</w:t></w:r>

This text run shall therefore use the Courier New font for all characters in the ASCII range, and shall use the Times New Roman font for all characters in the Complex Script range. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

ascii (ASCII Font)

Specifies a font which shall be used to format all characters in the ASCII range (0 - 127) within the parent run.

If the asciiTheme attribute is also specified, then this attribute shall be ignored and that value shall be used instead.

If this attribute is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this attribute is never applied in the style hierarchy, then the text shall be displayed in any default font which supports ASCII content.

[Example: Consider a run of ASCII text which shall be displayed using the Courier New font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:rFonts w:ascii=”Courier New” />

</w:rPr>

The ascii attribute specifies that the run shall use the Courier New font for all text in the ASCII range. end example]

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

asciiTheme (ASCII Theme Font)

Specifies a theme font which shall be used to format all characters in the ASCII range (0 - 127) within the parent run. This theme font is a reference to one of the predefined theme fonts, located in the document's Theme part,which allows for font information to be set centrally in the document.

If the ascii attribute is also specified, then that attribute shall be ignored and this value shall be used instead.

[Example: Consider a run of ASCII text which shall be displayed using the majorASCII theme font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:rFonts w:asciiTheme=”majorAscii” />

</w:rPr>

The ascii attribute specifies that the run shall use the majorAscii theme font as defined in the document's themes part for all text in the ASCII range. end example]

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

cs (Complex Script Font)

Specifies a font which shall be used to format all characters in a complex script Unicode range within the parent run.

If the csTheme attribute is also specified, then this attribute shall be ignored and that value shall be used instead.

[Example: Consider a run of Arabic text which shall be displayed using the Arial Unicode MS font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:rFonts w:cs=”Arial Unicode MS” />

</w:rPr>

The cs attribute specifies that the run shall use the Arial Unicode MS font for all text in a complex script range. end example]

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

cstheme (Complex Script Theme Font)

Specifies a theme font which shall be used to format all characters in a complex script Unicode range within the parent run. This theme font is a reference to one of the predefined theme fonts, located in the document's Theme part,which allows for font information to be set centrally in the document.

If the cs attribute is also specified, then that attribute shall be ignored and this value shall be used instead.

[Example: Consider a run of Arabic text which shall be displayed using the majorBidi theme font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:rFonts w:csTheme=”majorBidi” />

</w:rPr>

The csTheme attribute specifies that the run shall use the majorBidi theme font as defined in the document's themes part for all text in a complex script range. end example]

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

eastAsia (East Asian Font)

Specifies a font which shall be used to format all characters in an East Asian Unicode range within the parent run.

If the eastAsiaTheme attribute is also specified, then this attribute shall be ignored and that value shall be used instead.

[Example: Consider a run of Japanese text which shall be displayed using the MS Mincho font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr> <w:rFonts w:eastAsia=”MS Mincho” /></w:rPr>

The eastAsia attribute specifies that the run shall use the MS Mincho font for all text in an East Asian range. end example]

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

eastAsiaTheme (East Asian Theme Font)

Specifies a theme font which shall be used to format all characters in an East Asian Unicode range within the parent run. This theme font is a reference to one of the predefined theme fonts, located in the document's Theme part,which allows for font information to be set centrally in the document.

If the eastAsia attribute is also specified, then that attribute shall be ignored and this value shall be used instead.

[Example: Consider a run of Japanese text which shall be displayed using the minorEastAsia theme font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:rFonts w:eastAsiaTheme=”minorEastAsia” />

</w:rPr>

The eastAsiaTheme attribute specifies that the run shall use the minorEastAsia theme font as defined in the document's themes part for all text in an East Asian range. end example]

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

hAnsi (High ANSI Font)

Specifies a font which shall be used to format all characters in a Unicode range within the parent run which does not fall into one of the three categories defined above, which is called the high ANSI range in WordprocessingML.

If the hAnsiTheme attribute is also specified, then this attribute shall be ignored and that value shall be used instead.

[Example: Consider a run of text which falls into a high ANSI range, and shall be displayed using the Bauhaus 93 font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr> <w:rFonts w:hAnsi=”Bauhaus 93” /></w:rPr>

The hAnsi attribute specifies that the run shall use the Bauhaus 93 font for all text in a high ANSI range. end example]

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

hAnsiTheme (High ANSI Theme Font)

Specifies a theme font which shall be used to format all characters in a Unicode range within the parent run which does not fall into one of the three categories defined above, which is called the high ANSI range in WordprocessingML. This theme font is a reference to one of the predefined theme fonts, located in the document's Theme part,which allows for font information to be set centrally in the document.

If the hAnsi attribute is also specified, then that attribute shall be ignored and this value shall be used instead.

[Example: Consider a run of text which falls into a high ANSI range, and shall be displayed using the minorHAnsi theme font. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:rFonts w:hAnsiTheme="minorHAnsi" />

</w:rPr>

The hAnsiTheme attribute specifies that the run shall use the minorHAnsi theme font as defined in the document's themes part for all text in a high ANSI range. end example]

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

hint (Font Content Type)

Specifies the font type which shall be used to format any ambiguous characters in the current run.

There are certain characters which are not explicitly stored in the document, and may be mapped into multiple categories of the four mentioned above. This attribute shall be used to arbitrate that conflict, and determine how ambiguities in this run shall be handled. [Note: This is primarily used to handle the formatting on the paragraph mark glyph, and other characters that are not stored as text in the WordprocessingML document. end note]

If this attribute is omitted, then this ambiguity may be resolved by any means available.

[Example: Consider the run representing the paragraph mark glyph, which is not stored as a physical character. Since this could therefore be formatted with any of the fonts specified for the run, this ambiguity is resolved using the following WordprocessingML:

<w:pPr> <w:rPr> <w:rFonts w:hint="eastAsia" /> </w:rPr></w:pPr>

The hint attribute specifies that the run shall use the eastAsia font (theme or not, whichever is in use for East Asian text) as defined for this range. end example]

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

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

</complexType>

rPr (Run Properties)

This element specifies a set of run properties which shall be applied to the contents of the parent run after all style formatting has been applied to the text. These properties are defined as direct formatting, since they are directly applied to the run and supersede any formatting from styles.

This formatting is applied at the following location in the style hierarchy:

Document defaults

Table styles

Numbering styles

Paragraph styles

Character styles

Direct formatting (this element)

[Example: Consider a run which should have a set of run formatting properties. This set of properties is specified in the run properties as follows:

<w:r>

<w:rPr>

<w:b />

<w:imprint />

<w:lang w:val="en-ca" />

</w:rPr>

</w:r>

The rPr element specifies the properties which are applied to the current run - in this case, bold formatting on the run contents using the b element (§2.3.2.1), an imprinted (engraved) text effect using the imprint element (§2.3.2.16), and that this text should be interpreted as English (Canada) when spell or grammar checking the run text using the lang element (§2.3.2.18). end example]

Parent Elements

ctrlPr (§7.1.2.23); r (§7.1.2.87); r (§2.3.2.23)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

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

</sequence>

</complexType>

rPr (Previous Run Properties)

This element specifies a set of run properties which shall be attributed to a revision by a particular author and at a particular time. This element contains the set of properties which have been tracked as a specific set of revisions by one author.

[Example: Consider a run which has a set of run formatting properties that were added with revision tracking turned on. This set of revised properties is specified in the run properties as follows:

<w:r>

<w:rPr>

<w:b />

<w:imprint />

<w:lang w:val="en-ca" />

<w:rPrChange w:author="user1">

<w:rPr>

<w:i />

<w:dstrike w:val="false" />

</w:rPr>

</w:rPrChange>

</w:rPr>

</w:r>

The rPr element under rPrChange specifies the properties which were applied to the current run before revision tracking was turned on - in this case, italics using the i element (§2.3.2.14), and that any double strikethrough which was applied based on the style hierarchy shall be turned off using the dstrike element (§2.3.2.7). end example]

Parent Elements

del (§2.13.5.15); ins (§2.13.5.17); rPrChange (§2.13.5.32)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

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

</sequence>

</complexType>

rStyle (Referenced Character Style)

This element specifies the style ID of the character style which shall be used to format the contents of this paragraph.

This formatting is applied at the following location in the style hierarchy:

Document defaults

Table styles

Numbering styles

Paragraph styles

Character styles (this element)

Direct Formatting

This means that all properties specified in the style element (§2.7.3.17) with a styleId which corresponds to the value in this element's val attribute are applied to the run at the appropriate level in the hierarchy.

If this element is omitted, or it references a style which does not exist, then no character style shall be applied to the current paragraph. As well, this property is ignored if the run properties are part of a character style.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:pStyle w:val=”TestCharacterStyle” />

<w:b />

<w:i />

</w:rPr>

This run specifies that it will inherit all of the run properties specified by the paragraph style with a styleId of TestCharacterStyle, which will then have any bold or italics settings overridden and set to be applied to the run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

rtl (Right To Left Text)

This element specifies that the alignment and reading order for this run shall be right to left. This setting determines the way in which the run contents are presented in the document when punctuation characters are part of the run's contents. When this property is specified, each part of the run between a punctuation mark shall be laid out right to left on the line.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then right to left alignment shall not be applied to the contents of this run.

[Example: Consider the following run of English text: This is a list: one, two, three. Typically, each region of text between a punctuation mark is presented in a left to right reading order in the document (as shown above). If the right to left property is set on this text, as follows:

<w:rPr> <w:rtl v:val="on"/></w:rPr>

This run shall now have a right to left reading order, as follows:

.three ,two ,one :This is a list

In a right to left language, this would result in the correct placement of the punctuation with respect to each region of right to left text. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

shadow (Shadow)

This element specifies that the contents of this run shall be displayed as if each character has a shadow, displayed beneath the text and to its right.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then shadowing shall not be applied to the contents of this run.

This element shall not be present with either the emboss (§2.3.2.11) or imprint (§2.3.2.16) properties on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider a run of text which shall have the shadow property explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:shadow w:val="true"/></w:rPr>

This run explicitly declares that the shadow property is true, so the contents of this run will appear with a shadow. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

shd (Run Shading)

Like paragraph shading, this element specifies the shading applied to the contents of the run.

This shading consists of three components:

Background Color

(optional) Pattern

(optional) Pattern Color

The resulting shading is applied by setting the background color behind the paragraph, then applying the pattern color using the mask supplied by the pattern over that background.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then run shading shall not be applied to the contents of this run.

[Example: Consider a run which shall have a background consisting of a theme color accent6 with a theme color text2 overlaid using a 20% fill pattern. This requirement is specified using the following WordprocessingML:

<w:pPr>

<w:shd w:val="pct20" w:themeColor="text2" w:themeFill="accent6" />

</w:pPr>

The resulting run will use the background color accent6 under the foreground pattern color text2 as specified by the pct20 pattern mask. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

color (Shading Pattern Color)

Specifies the color used for any foreground pattern specified for this shading using the val attribute.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the foreground shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading of type pct20 with a foreground color value of auto, as follows:

<w:shd w:val="pct20"... w:color="auto"/>

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

fill (Shading Background Color)

Specifies the color used for the background for this shading.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the background shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading using a background color of hex value C3D69B, using the following WordprocessingML:

<w:shd w:fill="C3D69B" />

The background color for this shading therefore will be a color with a hex value of C3D69B. end example]

If the shading specifies the use of a theme color via the themeFill attribute, then this value is superseded by the theme color value.

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

themeColor (Shading Pattern Theme Color)

Specifies a theme color which should be applied to any foreground pattern specified for this shading using the val attribute.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading pattern color.

<w:pPr>

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

</w:pPr>

The resulting paragraph will use the foreground pattern color accent6 in the region specified by the pct20 pattern mask. end example]

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

themeFill (Shading Background Theme Color)

Specifies a theme color which should be applied to the background for this shading.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading background color.

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

The resulting shading will use the background color specified by the accent3 theme color. end example]

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

themeFillShade (Shading Background Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeFillShade is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

The resulting themeFillShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting shading's fill attribute:

<w:shd w:fill="943634" w:themeFill="accent2" w:themeFillShade="BF" />

end example]

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

themeFillTint (Shading Background Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeFillTint is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeFillTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's fill attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:fill="95B3D7" w:themeFillColor="accent2" w:themeFillTint="99" />

end example]

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

themeShade (Shading Pattern Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeShade is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

Te resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:shd w:color="943634" w:themeColor="accent2" w:themeShade="BF" />

end example]

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

themeTint (Shading Pattern Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeTint is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's color attribute:

<w:shd w:color="95B3D7" w:themeColor="accent2" w:themeTint="99" />

end example]

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

val (Shading Pattern)

Specifies the pattern which shall be used to lay the pattern color over the background color for this paragraph shading.

[Example: Consider a shaded paragraph which uses a 10 percent foreground fill, resulting in the following WordprocessingML:

<w:shd w:val="pct10" .../>

This shading val is pct10, indicating that the border style is a 10 percent foreground fill mask. end example]

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

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

</complexType>

smallCaps (Small Caps)

This element specifies that all small letter characters in this text run shall be formatted for display only as their capital letter character equivalents in a font size two points smaller than the actual font size specified for this text. This property does not affect any non-alphabetic character in this run, and does not change the Unicode character for lowercase text, only the method in which it is displayed. If this font cannot be made two point smaller than the current size, then it shall be displayed as the smallest possible font size in capital letters.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the characters are not formatted as capital letters.

This element shall not be present with the caps (§2.3.2.4) property on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider the words Hello World, which shall be displayed in small capital letters in a document. This constraint is specified as follows in the WordprocessingML:

<w:r>

<w:rPr> <w:sz w:val="24" />

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

</w:rPr>

<w:t>Hello World</w:t>

</w:r>

This run will display using a 12 point capital letter for the capital letter H and W, and a 10 point capital letter for the lowercase letters in the run, even though the lowercase characters are used in actual run contents. If this property is removed, the original character forms will be displayed (they are not lost). end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

This element specifies whether the current run should use the document grid characters per line settings defined in the docGrid element (§2.6.5) when laying out the contents in this run. This setting determines whether the additional character pitch specified in the document grid shall be added to each character in this run as specified by the document grid.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the run shall use the document grid setting to lay out text when a document grid is defined for the parent section.

[Example: Consider two runs in a section with a document grid set to allow 20 characters per line. This document grid would effectively specifies that an additional character pitch shall be added to each line in order to ensure that the resulting line contains only 20 East Asian characters.

If this property is set on the first run, but turned off on the second run, as follows:

<w:r> <w:t>Run One</w:t></w:r><w:r> <w:rPr> <w:snapToGrid w:val="off" /> </w:rPr> <w:t>Run Two</w:t></w:r>

The resulting document shall have the required additional character pitch added to each character in run one, but zero additional character pitch added to each character in run two, since the snapToGrid property is turned off. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

spacing (Character Spacing Adjustment)

This element specifies the amount of character pitch which shall be added or removed after each character in this run before the following character is rendered in the document. This property has an effect equivalent to the additional character pitched added by a document grid applied to the contents of a run.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the run shall not have any additional character pitch applied to any character in its contents.

[Example: Consider a run of text which shall have ten points of additional character spacing explicitly added to each character within the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:spacing w:val="200"/></w:rPr>

This run explicitly declares that the spacing value is 200, so the contents of this run will appear as if they have 10 additional points of spacing added between them. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Positive or Negative Value in Twentieths of a Point)

Specifies a value whose contents shall contain a positive whole number, whose contents consist of a positive or negative measurement in twentieths of a point (equivalent to 1/1440th of an inch).

The contents of this measurement shall be interpreted based on the context of the parent XML element.

[Example: Consider an attribute value of -720 whose type is ST_SignedTwipsMeasure. This attribute value specifies a value of negative one-half of an inch or -36 points (-720 twentieths of a point = -36 points = -0.5 inches). end example]

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

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

</complexType>

specVanish (Paragraph Mark Is Always Hidden)

This element specifies that the given run shall always behave as if it is hidden, even when hidden text is being displayed in the current document.

This property shall only be used to specify that a paragraph mark shall never be used to break the end of a paragraph for display, even if it is being shown on the document, as would be the case if a regularly hidden paragraph was not being displayed in the document. [Note: This property was typically used to ensure that a paragraph style can be applied to a part of a paragraph, and still appear as in the Table of Contents (which in previous word processors would ignore the use of the style if it were being used as a character style. end note] If this element is applied to any other run, it may be ignored.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the run properties for the paragraph mark shall not always be treated as if hidden.

[Example: Consider a paragraph mark which never be used to break the end of the paragraph in the document. This constraint is specified using the following WordprocessingML:

<w:pPr>

<w:rPr>

<w:specVanish />

</w:rPr>

</w:pPr>

The presence of the specVanish element means that this paragraph mark shall always be treated as hidden (shall never be used to end the paragraph for display), but may be used to mark the end of use of a paragraph style. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

strike (Single Strikethrough)

This element specifies that the contents of this run shall be displayed with a single horizontal line through the center of the line.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then strikethrough shall not be applied to the contents of this run.

This element shall not be present with the dstrike (§2.3.2.7) property on the same run, since they are mutually exclusive in terms of appearance.

[Example: Consider a run of text which shall have the strike property explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:strike w:val="true"/></w:rPr>

This run explicitly declares that the strike property is true, so the contents of this run will have a single horizontal strikethrough line. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

sz (Font Size)

This element specifies the font size which shall be applied to all non complex script characters in the contents of this run when displayed.

If this element is not present, the default value is to leave the value applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then any appropriate font size may be used for non complex script characters.

[Example: Consider a run of text which shall have an explicit font size of 13.5 points for the non complex script contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:sz w:val="27"/></w:rPr>

This run explicitly declares that the sz property is 27 half-point for the non-complex script contents of this run, so the text will be displayed in 13.5 point font size. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Half Point Measurement)

Specifies a positive measurement specified in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:sz w:val="28" />

</w:rPr>

The value of the val attribute is the font size of the run's contents.

However, consider the following fragment:

<w:rPr>

<w:kern w:val="30" />

</w:rPr>

In this case, the value in the val attribute is the minimum size for which font characters shall be automatically kerned.

In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

szCs (Complex Script Font Size)

This element specifies the font size which shall be applied to all complex script characters in the contents of this run when displayed.

[Example: Consider a run of text which shall have an explicit font size of 10 points for the complex script contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:szCs w:val="20"/></w:rPr>

This run explicitly declares that the sz property is 20 half-point for the non-complex script contents of this run, so the text will be displayed in 10 point font size. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Half Point Measurement)

Specifies a positive measurement specified in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:sz w:val="28" />

</w:rPr>

The value of the val attribute is the font size of the run's contents.

However, consider the following fragment:

<w:rPr>

<w:kern w:val="30" />

</w:rPr>

In this case, the value in the val attribute is the minimum size for which font characters shall be automatically kerned.

In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

u (Underline)

This element specifies that the contents of this run should be displayed along with an underline appearing directly below the character height (less all spacing above and below the characters on the line).

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then an underline shall not be applied to the contents of this run.

[Example: Consider a run of text which shall have a double underline explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:u w:val="double"/></w:rPr>

This run explicitly declares an underline using the u property. The val of that underline is double, so the style of the underline on this run shall be a double line. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

color (Underline Color)

Specifies the color for the underlining on this run.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the underline color as appropriate.

If the underline specifies the use of a theme color via the themeColor attribute, then this value is superseded by the theme color value.

[Example: Consider a run color with value auto, as follows:

<w:rPr>

<w:un … w:color="auto" />

</w:rPr>

This color therefore may be automatically be modified by a consumer as appropriate, for example, in order to ensure that the underline can be distinguished against the page's background color. end example]

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

themeColor (Underline Theme Color)

Specifies a theme color which should be applied to the current underline.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows for color information to be set centrally in the document.

If the themeColor attribute is specified, then the color attribute is ignored for this underline.

[Example: Consider an underlined run of text whose underline should be displayed using the accent3 theme color from the document’s Theme part. This requirement would be specified as follows in the resulting WordprocessingML:

<w:rPr>

<w:u … w:themeColor=”accent3” />

</w:rPr>

The themeColor attribute specifies that the underline shall use the accent3 theme color. end example]

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

themeShade (Underline Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this underline.

If the themeShade is supplied, then it is applied to the RGB value of the theme color to determine the final color applied to this underline.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a underline in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting underline's color attribute:

<w:u w:color="943634" w:themeColor="accent2" w:themeShade="BF" />

end example]

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

themeTint (Underline Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this underline's contents.

If the themeTint is supplied, then it is applied to the RGB value of the theme color to determine the final color applied to this run.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to an underline in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting underline formatting's WordprocessingML color attribute:

<w:u … w:color="95B3D7" w:themeColor="accent2" w:themeTint="99" />

end example]

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

val (Underline Style)

Specifies the pattern which shall be used to create the underline applied beneath the text in this run.

Each of these possible patterns are shown in the simple type referenced below.

[Example: Consider a run of text which shall have a double underline explicitly turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:u w:val="double"/></w:rPr>

The val of the underline on this run is double, so the style of the underline on this run shall be a double line. end example]

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

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

</complexType>

vanish (Hidden Text)

This element specifies whether the contents of this run shall be hidden from display at display time in a document. [Note: The setting should affect the normal display of text, but an application may have settings to force hidden text to be displayed. end note]

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy .If this element is never applied in the style hierarchy, then this text shall not be hidden when displayed in a document.

[Example: Consider a run of text which shall have the hidden text property turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:vanish /></w:rPr>

This run declares that the vanish property is set for the contents of this run, so the contents of this run will be hidden when the document contents are displayed. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

vertAlign (Subscript/Superscript Text)

This element specifies the alignment which shall be applied to the contents of this run in relation to the default appearance of the run's text. This allows the text to be repositioned as subscript or superscript without altering the font size of the run properties.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the text shall not be subscript or superscript relative to the default baseline location for the contents of this run.

[Example: Consider a run which shall be positioning as superscript when displaying its contents. This requirement would be specified using the following WordprocessingML:

<w:rPr>

<w:vertAlign w:val="superscript" />

</w:rPr>

The resulting run is positioned as superscript, therefore it is rendered in a smaller size above the default baseline location for the contents of the run. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Subscript/Superscript Value)

Specifies the type of vertical alignment applied to the contents of the current run.

[Example: Consider a run which shall be positioning as superscript when displaying its contents. This requirement would be specified using the following WordprocessingML:

<w:rPr>

<w:vertAlign w:val="superscript" />

</w:rPr>

The value of the val attribute is superscript, therefore the run's contents are rendered in a smaller size above the default baseline location for the contents of the run. end example]

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

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

</complexType>

w (Expanded/Compressed Text)

This element specifies the amount by which each character shall be expanded or when the character is rendered in the document. This property has an of stretching or compressing each character in the run, as opposed to the spacing element (§2.3.2.33) which expands/compresses the text by adding additional character pitch but not changing the width of the actual characters displayed on the line.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy. If this element is never applied in the style hierarchy, then the run shall be displayed at 100% of its normal width.

[Example: Consider a run of text which shall be expanded to 200% of its normal width when displaying each character within the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:w w:val="200"/></w:rPr>

This run explicitly declares that the w value is 200, so the contents of this run will appear at 200% of their normal character width by stretching the width of each character. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (Text Expansion/Compression Value)

Specifies that the percentage by which the contents of this run shall be expanded or compressed with respect to its normal (100%) character width.

If this attribute is omitted, then the contents of this run shall be displayed at 100% of its normal size.

[Example: Consider a run of text which shall be compressed to 200% when displaying each character within the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:w w:val="50"/></w:rPr>

This run explicitly declares that the w value is 50, so the contents of this run will appear at 50% of their normal character width by compressing the width of each character. end example]

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

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

</complexType>

webHidden (Web Hidden Text)

This element specifies whether the contents of this run shall be hidden from display at display time in a document when the document is being displayed in a web page view. [Note: The setting should affect the normal display of text in a web page view, but an application may have settings to force hidden text to be displayed. end note] As well, this setting should not affect a normal paginated view of the document.

If this element is not present, the default value is to leave the formatting applied at previous level in the style hierarchy .If this element is never applied in the style hierarchy, then this text shall not be hidden when displayed in a document in a web page view.

[Example: Consider a run of text which shall have the hidden text property turned on for the contents of the run. This constraint is specified using the following WordprocessingML:

<w:rPr> <w:webHidden /></w:rPr>

This run declares that the webHidden property is set for the contents of this run, so the contents of this run will be hidden when the document contents are displayed in a web page view. end example]

Parent Elements

rPr (§2.7.8.1); rPr (§2.3.1.29); rPr (§2.5.2.26); rPr (§2.3.2.25); rPr (§2.3.2.26); rPr (§2.7.4.4); rPr (§2.3.1.30); rPr (§2.9.26); rPr (§2.5.2.27); rPr (§2.7.5.2)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

Run Content

The final level of the document hierarchy is run content, which is defined as the set of elements which can be contained as the contents of a particular run in a document.

[Note: Types of run content in WordprocessingML include:

Text

Field Codes

DrawingML objects

VML objects

Fields

end note]

[Example: Consider the following run within a WordprocessingML document:

<w:r> <w:rPr> <w:b/> <w:i/> </w:rPr> <w:t>quick</w:t></w:r>

The run content consists of a single string of run text inside the t element, which reads quick. end example]

br (Break)

This element specifies that a break shall be placed at the current location in the run content. A break is a special character which is used to override the normal line breaking that would be performed based on the normal layout of the document’s contents. [Example: Normal breaking for English would occur only after a breaking space or optional hyphen character. end example]

The behavior of this break character (the location where text shall be restarted after this break) shall be determined by its type and clear attribute values, described below.

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

This is a simple sentence.

Normally, just as shown above, this sentence would be displayed on a single line as it is not long enough to require line breaking (given the width of the current page). However, if a text wrapping break character (a typical line break) were inserted after the word is, as follows:

<w:r> <w:t>This is</w:t> <w:br/> <w:t xml:space="preserve"> a simple sentence.</w:t></w:r>

This would imply that this break shall be treated as a simple line break, and break the line after that word:

This is a simple sentence.

The break character forced the following text to be restarted on the next available line in the document. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

clear (Restart Location For Text Wrapping Break)

Specifies the location which shall be used as the next available line when the break’s type attribute has a value of textWrapping. This property only affects the restart location when the current run is being displayed on a line which does not span the full text extents due to the presence of a floating object (see possible values for details).

If this break is not of type textWrapping, then this attribute shall be ignored. If this attribute is omitted, then its value shall be assumed to be none if needed.

[Example: Consider a text wrapping break character which should force the restart location to the next line which spans the full width of the text extents of the page (there are no floating objects which interrupt the line).

This line break is of type textWrapping, since it shall only advance to the next line, but the clear value shall specify that this restart location shall ignore all lines which are not of the full line width by specifying a value of all, as follows:

<w:br w:type="textWrapping" w:clear="all" />

This break shall therefore not use the next available line, but rather the next available line ignoring all lines which do not span the full text width. end example]

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

type (Break Type)

Specifies the type of the current break. The break type determines the next location where text shall be placed after this manual break is applied to the text contents (see possible values for details).

If this attribute is omitted, then it shall be assumed to be of type textWrapping.

[Example: Consider a manual break which shall advance the text to the next text column in the document, rather than just the next available line. This break would therefore be specified as follows:

<w:br w:type=”column”/>

The type attribute specifies a value of column, which means that the break shall force the next character in the document to be restarted on the next line in a new text column in the document. end example]

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

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

</complexType>

control (Floating Embedded Control)

This element specifies that the parent VML object is a representation of an embedded control at the current location in the document. This element shall be used to associate the VML data with the appropriate embedded control settings and properties when the document is displayed.

If the embedded control is not present, cannot be loaded due to application settings, or is not supported, then the VML data shall be used to provide an image representation of the control at the appropriate location in the document.

[Example: Consider a run which consists of an embedded control. That run would be specified using the following WordprocessingML:

<w:r> <w:pict> … <w:control r:id=”rId99” w:shapeid=”shape01” … /> </w:pict></w:r>

The control element indicates that the parent VML object contains the positioning and last known image representation of an embedded control, whose settings and properties are stored on this element. end example]

Parent Elements

pict (§2.3.3.21); pict (§2.9.23)

Attributes

Description

id (Embedded Control Properties Relationship Reference)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID for the relationship which contains the properties for this embedded control. This property bag is contained in a separate part within the Word Open XML package.

The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/control or the document shall be conisdered non-conformant.

If this attribute is omitted, then the embedded control shall be given no property bag when instantiated.

[Example: Consider the following WordprocessingML markup for an embedded control in a document:

<w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid="_x0000_s1027" w:class="shape" w:w="145" w:h="28" w:align="left" />

The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rId5 shall contain the property data for this embedded control. end example]

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

name (Unique Name for Embedded Control)

Specifies a unique name for this embedded control. This name shall be unique across all controls in this document.

[Example: Consider the following WordprocessingML markup for an embedded control in a document:

<w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid="_x0000_s1027" w:class="shape" w:w="145" w:h="28" w:align="left" />

The name attribute specifies that the unique name for this control shall be CheckBox1. end example]

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

shapeid (Associated VML Data Reference)

Specifies the shape ID for a shape which shall be used to define the presentation and location of this embedded control within the document if the control is floating using the VML syntax.

[Note: This positioning data is sufficient to display the control in any case where:

The embedded control is not on the current machine

Embedded controls are disabled

Embedded controls of this type are not supported

end note]

This shape ID reference is resolved by looking for a VML shape element (§6.1.2.19) whose id attribute matches the value specified within this attribute. If no such shape exists, then the control shall be rendered inline in the document content at the current run content location.

If this attribute is omitted, then this embedded control shall be displayed inline in the current location in the parent run.

[Example: Consider the following WordprocessingML markup for an embedded control in a document:

<w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid="_x0000_s1027" w:class="shape" w:w="145" w:h="28" w:align="left" />

The shapeid attribute specifies that the VML shape element with a shape id attribute value of _x0000_s1027 shall contain the VML positioning data for this embedded control. end example]

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

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

</complexType>

control (Inline Embedded Control)

This element specifies that the parent embedded object is a representation of an embedded control at the current location in the document. This element shall be used to associate the appropriate embedded control settings and properties when the document is displayed.

If the embedded control is not present, cannot be loaded due to application settings, or is not supported, then a suitable placeholder image shall be used to provide a representation of the presence of an embedded control at the appropriate location in the document.

[Example: Consider a run which consists of an embedded control. That run would be specified using the following WordprocessingML:

<w:r> <w:object> … <w:control r:id=”rId99” w:shapeid=”shape01” … /> </w:object></w:r>

The control element indicates that the parent embedded object is an embedded control, whose settings and properties are stored on this element and the (optional) target of the relationship specified using the id attribute. end example]

Parent Elements

object (§2.3.3.19)

Attributes

Description

id (Embedded Control Properties Relationship Reference)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID for the relationship which contains the properties for this embedded control. This property bag is contained in a separate part within the Word Open XML package.

The relationship explicitly targeted by this attribute shall be of type http://schemas.openxmlformats.org/officeDocument/2006/relationships/control or the document shall be conisdered non-conformant.

If this attribute is omitted, then the embedded control shall be given no property bag when instantiated.

[Example: Consider the following WordprocessingML markup for an embedded control in a document:

<w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid="_x0000_s1027" w:class="shape" w:w="145" w:h="28" w:align="left" />

The id attribute in the relationship reference namespace specifies that the relationship with relationship ID rId5 shall contain the property data for this embedded control. end example]

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

name (Unique Name for Embedded Control)

Specifies a unique name for this embedded control. This name shall be unique across all controls in this document.

[Example: Consider the following WordprocessingML markup for an embedded control in a document:

<w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid="_x0000_s1027" w:class="shape" w:w="145" w:h="28" w:align="left" />

The name attribute specifies that the unique name for this control shall be CheckBox1. end example]

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

shapeid (Associated VML Data Reference)

Specifies the shape ID for a shape which shall be used to define the presentation and location of this embedded control within the document if the control is floating using the VML syntax.

[Note: This positioning data is sufficient to display the control in any case where:

The embedded control is not on the current machine

Embedded controls are disabled

Embedded controls of this type are not supported

end note]

If this attribute is omitted, then this embedded control shall be displayed inline in the current location in the parent run.

[Example: Consider the following WordprocessingML markup for an embedded control in a document:

<w:control r:id="rId5" w:id="CheckBox1" w:name="CheckBox1" w:shapeid="_x0000_s1027" w:class="shape" w:w="145" w:h="28" w:align="left" />

The shapeid attribute specifies that the VML shape element with a shape id attribute value of _x0000_s1027 shall contain the VML positioning data for this embedded control. end example]

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

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

</complexType>

cr (Carriage Return)

This element specifies that a carriage return shall be placed at the current location in the run content. A carriage return is the equivalent of Unicode character 000D, and is used to end the current line of text in WordprocessingML.

The behavior of a carriage return in run content shall be identical to a break character with null type and clear attributes, which shall end the current line and find the next available line on which to continue.

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

This is another simple sentence.

Normally, just as shown above, this sentence would be displayed on a single line as it is not long enough to require line breaking (given the width of the current page). However, if a carriage return were inserted after the word another, as follows:

<w:r> <w:t>This is another</w:t> <w:cr/> <w:t xml:space="preserve"> simple sentence.</w:t></w:r>

This would imply that this carriage return character shall force a line break, and break the line after that word:

This is another simple sentence.

The carriage return character forced the following text to be restarted on the next available line in the document. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

dayLong (Date Block - Long Day Format)

This element specifies the presence of a date block at the current location in the run content. A date block is a non-editable region of text which shall display the current date filtered through the specified date picture (see following paragraphs) . [Note: The date block is a legacy construct used for compatibility with older word processors, and should not be produced unless it was consumed while reading a document – it is recommended that the DATE field is used in its place. end note]

A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

The long day format date block shall use a date picture of DDDD, retrieving the long day format for the primary editing language.

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is a long date: </w:t> <w:dayLong /></w:r>

This run specifies that a long day format date block shall be placed after the text string literal This is a long date: in the document. Assuming that the host application’s primary editing language is French (Canada) and today’s date is 04/12/2006 (a Wednesday), this run would be displayed as follows:

This is a long date: mercredi

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

dayShort (Date Block - Short Day Format)

A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

The short day format date block shall use a date picture of DD, retrieving the short day format for the primary editing language.

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is a short date: </w:t> <w:dayShort /></w:r>

This run specifies that a short day format date block shall be placed after the text string literal This is a short date: in the document. Assuming that the host application’s primary editing language is English (Canada) and today’s date is 04/12/2006 (a Wednesday), this run would be displayed as follows:

This is a short date: 12

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

delText (Deleted Text)

This element specifies that this run contains literal text which shall be displayed in the document. The delText element shall be used for all text runs which are part of a region of text that is contained in a deleted region using the del element (§2.13.5.12).

[Example: Consider a paragraph of WordprocessingML content which reads This is deleted text, where the words deleted text are part of a deleted region of the document. This paragraph would therefore be represented as follows:

<w:p> <w:r> <w:t xml:space="preserve">This is </w:t> </w:r> <w:del> <w:r> <w:delText>deleted text</w:delText> </w:r> </w:del></w:p>

The deleted text is contained in a delText node, while the regular text is contained in a t node. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

space (Content Contains Significant Whitespace)

Namespace: http://www.w3.org/XML/1998/namespace

Specifies how white space should be handled for the contents of this element using the W3C space preservation rules.

[Example: Consider the following run contained within a WordprocessingML document:

<w:r> <w:t>significant whitespace </w:t></w:r>

Although there are three spaces on each side of the text content in the run, that whitespace has not been specifically marked as significant, therefore it is removed when this run is added to the document. end example]

The possible values for this attribute are defined by the type in the namespace.

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

</extension>

</simpleContent>

</complexType>

dirty (Invalidated Field Cache)

This element specifies that the field has been changed and the results shall be updated on open in a conforming consumer.

Parent Elements

rubyPr (§2.3.3.27)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

drawing (DrawingML Object)

This element specifies that a DrawingML object is located at this position in the run’s contents. The layout properties of this DrawingML object are specified using the WordprocessingML Drawing syntax (§5.5).

[Example: Consider a run which consists of a picture which is in line with the text in that paragraph (i.e. on the line and affects the line height). That run would be specified using the following WordprocessingML:

<w:r> <w:drawing> <wp:inline> … </wp:inline> </w:drawing></w:r>

The drawing element indicates that a DrawingML object and its WordprocessingML Drawing positioning data are located at the current position in the run (e.g. a picture or a chart). end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Child Elements

Subclause

anchor (Anchor for Floating DrawingML Object)

§5.5.2.3

inline (Inline DrawingML Object)

§5.5.2.8

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

</choice>

</complexType>

hps (Phonetic Guide Text Font Size)

This element specifies the font size which shall be applied to the phonetic guide text in the contents of this run when displayed.

If this element disagrees with the run properties on the phonetic guide text rt element (§2.3.3.23), then those properties shall be ignored and this element shall determine the size of the phonetic guide text.

[Example: Consider a run of phonetic guide text which shall have an explicit font size of 13.5 points. This constraint is specified using the following WordprocessingML:

<w:rubyPr> … <w:hps w:val="27"/>

…</w:rubyPr>

The hps property is 27 half-points for the ruby text in this run, so the phonetic guide text will be displayed in 13.5 point font size. end example]

Parent Elements

rubyPr (§2.3.3.27)

Attributes

Description

val (Half Point Measurement)

Specifies a positive measurement specified in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:sz w:val="28" />

</w:rPr>

The value of the val attribute is the font size of the run's contents.

However, consider the following fragment:

<w:rPr>

<w:kern w:val="30" />

</w:rPr>

In this case, the value in the val attribute is the minimum size for which font characters shall be automatically kerned.

In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

hpsBaseText (Phonetic Guide Base Text Font Size)

This element specifies the font size which shall be applied to the base text of this phonetic guide text when displayed. If this element disagrees with the run properties on the phonetic guide base text rubyBase element (§2.3.3.26), then this property shall be ignored and the sz element (§2.3.2.36) in that run shall determine the size of the phonetic guide base text.

[Example: Consider a run of phonetic guide base text which shall have an explicit font size of 30 points. This constraint is specified using the following WordprocessingML:

<w:rubyPr> … <w:hpsBaseText w:val="60"/>

…</w:rubyPr>

The hpsBaseText property is 60 half-points for the base text in this phonetic guide, so the phonetic guide base text will be displayed in 30 point font size. end example]

Parent Elements

rubyPr (§2.3.3.27)

Attributes

Description

val (Half Point Measurement)

Specifies a positive measurement specified in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:sz w:val="28" />

</w:rPr>

The value of the val attribute is the font size of the run's contents.

However, consider the following fragment:

<w:rPr>

<w:kern w:val="30" />

</w:rPr>

In this case, the value in the val attribute is the minimum size for which font characters shall be automatically kerned.

In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

hpsRaise (Distance Between Phonetic Guide Text and Phonetic Guide Base Text)

This element specifies the distance which shall be left between the phonetic guide base text and the phonetic guide text when this phonetic guide text is displayed.

[Example: Consider a run of phonetic guide text which shall have 10 points between the phonetic guide base text and the phonetic guide text. This constraint is specified using the following WordprocessingML:

<w:rubyPr> … <w:hpsRaise w:val="20"/>

…</w:rubyPr>

The hpsRaise property is 20 half-points for the phonetic guide, so the phonetic guide text will be displayed 10 points above the phonetic guide base text. end example]

Parent Elements

rubyPr (§2.3.3.27)

Attributes

Description

val (Half Point Measurement)

Specifies a positive measurement specified in half-points (1/144 of an inch).

The contents of this attribute value are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:rPr>

<w:sz w:val="28" />

</w:rPr>

The value of the val attribute is the font size of the run's contents.

However, consider the following fragment:

<w:rPr>

<w:kern w:val="30" />

</w:rPr>

In this case, the value in the val attribute is the minimum size for which font characters shall be automatically kerned.

In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

lastRenderedPageBreak (Position of Last Calculated Page Break)

This element specifies that this position delimited the end of a page when this document was last saved by an application which paginates its content.

[Guidance: This element shall be used by applications to specify the locations of page breaks within a document when it is saved as WordprocessingML, in order to allow other applications (e.g. assistive software) to utilize this information when reading the document. end guidance]

[Example: Consider a run which consists of the text This is the end of the page, where the word end was the last word on a page. If the application saving this file had paginated this content, that information may be saved with the file as follows:

<w:r> <w:t>This is the end</w:t> <w:lastRenderedPageBreak/> <w:t xml:space="preserve"> of the page</w:t></w:r>

The lastRenderedPageBreak element indicates that there was a page break resulting from pagination of this content, which occurred between the word end and the word of. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

lid (Language ID for Phonetic Guide)

This element specifies the language which shall be for this phonetic guide.

[Example: Consider a run of phonetic guide text which is using Japanese as it language. This constraint is specified using the following WordprocessingML:

<w:rubyPr> … <w:lid w:val="ja-JP"/>

…</w:rubyPr>

The lid property is ja-JP for the phonetic guide, so the phonetic guide is specified to be Japanese. end example]

Parent Elements

rubyPr (§2.3.3.27)

Attributes

Description

val (Language Code)

Specifies an ISO 639-1 letter code or 4 digit hexadecimal code for a specific language.

This code is interpreted in the context of the parent XML element.

[Example: Consider an object which shall specify the English(Canada) language. That object would use the ISO 639-1 letter code of en-CA to specify this language. end example]

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

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

</complexType>

monthLong (Date Block - Long Month Format)

A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

The long month format date block shall use a date picture of MMMM, retrieving the long month format for the primary editing language.

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is a long date: </w:t> <w:monthLong /></w:r>

This run specifies that a long month format date block shall be placed after the text string literal This is a long date: in the document. Assuming that the host application’s primary editing language is French (Canada) and today’s date is 04/12/2006 (a Wednesday), this run would be displayed as follows:

This is a long date: avril

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

monthShort (Date Block - Short Month Format)

This element specifies the presence of a date block at the current location in the run content. A date block is a non-editable region of text which shall display the current date filtered through the specified date picture (see following paragraphs). [Note: The date block is a legacy construct used for compatibility with older word processors, and should not be produced unless it was consumed while reading a document – it is recommended that the DATE field is used in its place. end note]

A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

The short month format date block shall use a date picture of MM, retrieving the short month format for the primary editing language.

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is a short date: </w:t> <w:monthShort /></w:r>

This run specifies that a short month format date block shall be placed after the text string literal This is a short date: in the document. Assuming that the host application’s primary editing language is English (Canada) and today’s date is 04/12/2006 (a Wednesday), this run would be displayed as follows:

This is a short date: 04

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

movie (Embedded Video)

This element specifies a location within a document where the specified parent image shall be treated as a static placeholder for an embedded movie. The specified movie file's contents should be displayed when requested at this location in the document. The location of the embedded movie to be displayed when supported shall be specified by the relationship whose Id attribute matches the id attribute on this element.

If the relationship type of the relationship specified by this element is not http://schemas.openxmlformats.org/officeDocument/2006/movie, or is not present, then the document shall be considered non-conformant. If an application cannot process external content of the content type specified by the targeted part, then it may be ignored.

[Example: Consider a WordprocessingML document which contains a VML shape holding the static image for a movie:

<v:shape id="_x0000_s1026" … > <w:movie r:id="rIdMovie" /> <v:imagedata r:id="rId5" r:pict="rId6" o:title="" o:movie="7168" /> </v:shape>

The movie element specifies that the part targeted by the relationship with an ID of rIdMovie shall be imported at the beginning of the document. Examining the contents of the corresponding relationship part item, we can see the targets for that relationship:

The corresponding relationship part item shows that the movie file is located next to the main document and is named movie.mov. end example]

Parent Elements

pict (§2.3.3.21); pict (§2.9.23)

Attributes

Description

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

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

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

</complexType>

noBreakHyphen (Non Breaking Hyphen Character)

This element specifies that a non breaking hyphen character shall be placed at the current location in the run content. A non breaking hyphen is the equivalent of Unicode character 002D (the hyphen-minus), however it shall not be used as a valid line breaking character for the current line of text when displaying this WordprocessingML content.

The behavior of a non breaking hyphen in run content shall be to display using the same glyph as the hyphen-minus character, however without being a valid line breaking position (unlike the hyphen-minus character).

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

This makes a very very very wordy and deliberately overcomplicated sentence.

Normally, just as shown above, this sentence not would be displayed on a single line as it is long enough to require line breaking (given the width of the current page). However, if a hyphen minus were inserted after the letter s in sentence, as follows:

<w:r> <w:t>This makes a very very very wordy and deliberately overcomplicated s-entence.</w:t></w:r>

This would allow a break at that position, and break the word after that character:

This makes a very very very wordy and deliberately overcomplicated s-entence.

If this was not desired, the non breaking hyphen character could be specified as follows:

<w:r> <w:t>This makes a very very very wordy and deliberately overcomplicated s</w:t> <w:nonBreakHyphen/> <w:t>entence.</w:t></w:r>

This would display a hyphen character, but would not allow the text to break at that location:

This makes a very very very wordy and deliberately overcomplicated sentence.

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

object (Inline Embedded Object)

This element specifies that an embedded object is located at this position in the run’s contents. The layout properties of this embedded object are specified using the VML syntax (§6.1).

[Example: Consider a run which consists of an embedded object which is in line with the text in that paragraph (i.e. on the line and affects the line height). That run would be specified using the following WordprocessingML:

<w:r> <w:object> … </w:object></w:r>

The object element indicates that an embedded object and its VML positioning data are located at the current position in the run (e.g. an embedded object). end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Child Elements

Subclause

Any element from the urn:schemas-microsoft-com:vml namespace

§6.1

Any element from the urn:schemas-microsoft-com:office:office namespace

§6.2

control (Inline Embedded Control)

§2.3.3.3

Attributes

Description

dxaOrig (Original Image Width)

Specifies the original (natural) width of the image representation of the current control within the document. Some vector image formats do not store a native size within their format, and this attribute shall only be used in those cases to store this information, so that the image may be appropriately restored as needed.

If this element is excluded, then the natural size of the image as stored in its format shall be used.

[Example: Consider the following WordprocessingML for an embedded object:

<w:object w:dxaOrig="3360" w:dyaOrig="2520"> … <v:shape … style="width:168pt;height:4in"> … </v:shape> <o:OLEObject … />

</w:object>

The dxaOrig attribute has a value of 3360, which specifies that the image used for the embedded object doesn't store its native width, but that width should be 3360 twentieths of a point. end example]

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

dyaOrig (Original Image Height)

Specifies the original (natural) height of the image representation of the current control within the document. Some vector image formats do not store a native size within their format, and this attribute shall only be used in those cases to store this information, so that the image may be appropriately restored as needed.

If this element is excluded, then the natural size of the image as stored in its format shall be used.

[Example: Consider the following WordprocessingML for an embedded object:

<w:object w:dxaOrig="3360" w:dyaOrig="2520"> … <v:shape … style="width:168pt;height:4in"> … </v:shape> <o:OLEObject … />

</w:object>

The dyaOrig attribute has a value of 2520, which specifies that the image used for the embedded object doesn't store its native height, but that height should be 2520 twentieths of a point. end example]

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

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

</sequence>

</extension>

</complexContent>

</complexType>

pgNum (Page Number Block)

This element specifies the presence of a page number block at the current location in the run content. A page number block is a non-editable region of text which shall display the current page using ascending decimal numbers. [Note: The page number block is a legacy construct used for compatibility with older word processors, and should not be produced unless it was consumed while reading a document – it is recommended that the PAGENUM field is used in its place. end note]

A page number block shall be displayed using ascending decimal numbers, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is the current page: </w:t> <w:pgNum /></w:r>

This run specifies that a page number block shall be placed after the text string literal This is the curent page: in the document. Assuming that this content is on the first page, this run would be displayed as follows:

This is the current page: 1

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

pict (VML Object)

This element specifies that an object is located at this position in the run’s contents. The layout properties of this object are specified using the VML syntax (§6.1).

[Example: Consider a run which consists of an object specified using VML. That run would be specified using the following WordprocessingML:

<w:r> <w:pict> … </w:pict></w:r>

The pict element indicates that an object specified in VML is located at the current position in the run (e.g. a floating embedded control). end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Child Elements

Subclause

Any element from the urn:schemas-microsoft-com:vml namespace

§6.1

Any element from the urn:schemas-microsoft-com:office:office namespace

§6.2

control (Floating Embedded Control)

§2.3.3.2

movie (Embedded Video)

§2.3.3.17

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

</sequence>

</extension>

</complexContent>

</complexType>

ptab (Absolute Position Tab Character)

This element specifies that an absolute position tab character shall be placed at the current location in the run content. An absolute position tab is a character which is used to advance the position on the current line of text when displaying this WordprocessingML content, using the following logic:

Regardless of any number of custom tab stops defined using the tabs element (§2.3.1.38) , the absolute position tab character shall advance to the position specified by its alignment and relativeTo attributes. The resulting end position of the tab character shall not be affected by the addition of any custom tab stops or changes to the value of the defaultTabStop element (§2.15.1.24).

If the alignment location specified by the positional tab cannot be found on the current line, because the starting location is past that point, then the tab character shall advance to that location on the next available line in the document.

<w:pPr>

<w:tabs>

<w:tab w:val="left" w:pos="2160" />

<w:tab w:val="left" w:pos="5040" />

</w:tabs>

</w:pPr>

If a positional tab character was added to a run in this paragraph starting at 1” inside the margin and was defined as follows:

<w:ptab w:alignment="center" w:relativeTo="margin" />

This positional tab would then ignore the next custom tab stop and the indents on the current paragraph defined using the ind element (§2.3.1.12) and would advance to the center of the line with respect to the text margins, moving to a new line if needed. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

alignment (Positional Tab Stop Alignment)

Specifies the location of the positional tab stop on the line, as well as the alignment which shall be applied to text subsequent to the current positional tab stop.

[Example: Consider a positional tab stop in a WordprocessingML document who shall move to the left edge of the text margins and whose subsequent text should be left aligned. This positional tab stop would be defined as follows:

<w:ptab w:alignment="left" w:relativeTo=”margin” … />

The alignment attribute specifies that this absolute position tab stop shall align on the left edge of the line relative to the margin. end example]

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

leader (Tab Leader Character)

Specifies the character which shall be used to fill in the space created by a positional tab. This character shall be repeated as required to completely fill the tab spacing generated by the positional tab character.

[Example: Consider a positional tab stop which should be preceded by a sequence of underscore characters, as follows:

______________Text at the positional tab stop

This tab stop would have a leader attribute value of underscore, indicating that the tab stop shall be preceded by underscore characters as needed to fill the tab spacing. end example]

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

relativeTo (Positional Tab Base)

Specifies the extents which shall be used to calculate the absolute positioning of this positional tab character.

[Example: Consider a positional tab stop in a WordprocessingML document that should have a resulting position that is centered on the text margins, ignoring both any custom tab stops and any text indents on the paragraph. This positional tab stop would be defined as follows:

<w:ptab w:relativeTo="margin" … />

The relativeTo attribute specifies that this absolute position tab stop shall be relative to the margin. end example]

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

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

</complexType>

rt (Phonetic Guide Text)

This element specifies the presence of the guide text within a phonetic guide at the current location in the document.

The contents of the guide text run are specified in the child r element (§2.3.2.23).

[Example: Consider the following two runs, each containing a phonetic guide:

tō東kyō京

The guide text run would be specified using the following WordprocessingML:

<w:rt> … <w:r> <w:t>tō</w:t> </w:r></w:rt>

The guide text is contained in a run within the rt element. end example]

Parent Elements

ruby (§2.3.3.24)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

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

</complexType>

ruby (Phonetic Guide)

This element specifies the presence of a phonetic guide at the current location in the document. A phonetic guide (often called ruby text) is a run of content with base text which appears at the normal baseline location for text in this run, with phonetic guide text displayed above it in the document. The resulting construct is called a phonetic guide as it is typically used to map words in one language to another phonetically.

The base text is stored in the rubyBase element (§2.3.3.26) and the guide text is stored in the rt element (§2.3.3.23).

[Example: Consider the following two runs, each containing a phonetic guide:

tō東kyō京

The first run would be specified using the following WordprocessingML:

<w:r> <w:ruby> <w:rubyPr> … </w:rubyPr> <w:rt> … <w:r> <w:t>tō</w:t> </w:r> </w:rt> <w:rubyBase> … <w:r> <w:t>東</w:t> </w:r> </w:rubyBase> </w:ruby></w:r>

The base text is contained in a run within the rubyBase element, and the guide text is contained in a run within the rt element. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Child Elements

Subclause

rt (Phonetic Guide Text)

§2.3.3.23

rubyBase (Phonetic Guide Base Text)

§2.3.3.26

rubyPr (Phonetic Guide Properties)

§2.3.3.27

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

</sequence>

</complexType>

rubyAlign (Phonetic Guide Text Alignment)

This element specifies the alignment setting which shall be used to determine the placement of phonetic guide text with respect to the base text when this phonetic guide is displayed.

[Example: Consider a run of phonetic guide text which shall have the ruby text positioned to the far left of the base text. This constraint is specified using the following WordprocessingML:

<w:rubyPr> … <w:rubyAlign w:val="left"/>

…</w:rubyPr>

The rubyAlign property is left for the phonetic guide, so the ruby text will be displayed on the left side of the base text. end example]

Parent Elements

rubyPr (§2.3.3.27)

Attributes

Description

val (Phonetic Guide Text Alignment Value)

Specifies the type of alignment to be applied to the phonetic guide text.

[Example: Consider a run of phonetic guide text which shall have the ruby text positioned to the far right of the base text. This constraint is specified using the following WordprocessingML:

<w:rubyPr> … <w:rubyAlign w:val="left"/>

…</w:rubyPr>

The value of the val attribute is right for the phonetic guide, so the ruby text will be displayed on the right side of the base text. end example]

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

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

</complexType>

rubyBase (Phonetic Guide Base Text)

This element specifies the presence of the base text within a phonetic guide at the current location in the document.

The contents of the base text run are specified in the child r element (§2.3.2.23).

[Example: Consider the following two runs, each containing a phonetic guide:

tō東kyō京

The base text run would be specified using the following WordprocessingML:

<w:rubyBase> … <w:r> <w:t>東</w:t> </w:r></w:rubyBase>

The base text is contained in a run within the rubyBase element. end example]

Parent Elements

ruby (§2.3.3.24)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

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

</complexType>

rubyPr (Phonetic Guide Properties)

This element specifies a set of properties which determine the behavior and appearance of a phonetic guide within the document.

[Example: Consider the following two runs, each containing a phonetic guide:

tō東kyō京

The properties for both of these phonetic guides are as follows:

<w:r> <w:ruby> <w:rubyPr> <w:rubyAlign w:val="distributeSpace" /> <w:hps w:val="16" /> <w:hpsRaise w:val="20" /> <w:hpsBaseText w:val="22" />

<w:lid w:val="ja-JP" />

</w:rubyPr> … </w:ruby></w:r>

The phonetic guide properties specify that the guide text shall be:

Distributed across the top (using the rubyAlign element)

8 point font face (using the hps element)

10 points above the base text (using the hpaRaise element)

Japanese (using the lid element)

As well, the phonetic guide properties specify that the base text shall be:

11 point font face (using the hpsBaseText element)

end example]

Parent Elements

ruby (§2.3.3.24)

Child Elements

Subclause

dirty (Invalidated Field Cache)

§2.3.3.8

hps (Phonetic Guide Text Font Size)

§2.3.3.10

hpsBaseText (Phonetic Guide Base Text Font Size)

§2.3.3.11

hpsRaise (Distance Between Phonetic Guide Text and Phonetic Guide Base Text)

§2.3.3.12

lid (Language ID for Phonetic Guide)

§2.3.3.14

rubyAlign (Phonetic Guide Text Alignment)

§2.3.3.25

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

</sequence>

</complexType>

softHyphen (Optional Hyphen Character)

This element specifies that an optional hyphen character shall be placed at the current location in the run content. An optional hyphen is a character which may be used as a valid line breaking character for the current line of text when displaying this WordprocessingML content, using the following logic:

When this character is not the character which is used to break the line, then it shall not change the normal display of text (it shall have zero width)

When this character is the character used to break the line, it shall display using the hyphen-minus character within the display of text

[Note: This character is typically used to mark locations where a word may optionally be hyphenated without causing the hyphen character to be displayed unnecessarily. end note]

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

This sentence needs to be long enough to cause some kind of line breaking.

Normally, just as shown above, this sentence not would be displayed on a single line as it is long enough to require line breaking (given the width of the current page). However, if an optional hyphen were inserted after the letter r in breaking, as follows:

<w:r> <w:t>This sentence needs to be long enough to cause some kind of line br</w:t> <w:softHyphen/> <w:t>eaking.</w:t></w:r>

This would allow a break at that position, and when that location is the point of the line break, would insert a hyphen-minus in the word after that character:

This sentence needs to be long enough to cause some kind of line breaking.

If this was not the point of the line break, then no character would be displayed at that location:

This sentence should not be long enough to cause line breaking.

The sentence now does not break at that location, so no hyphen appears in the word breaking. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

sym (Symbol Character)

This element specifies the presence of a symbol character at the current location in the run’s content. A symbol character is a special character within a run’s content which does not use any of the run fonts specified in the rFonts element (§2.3.2.24) (or by the style hierarchy).

Instead, this character shall be determined by pulling the character with the hexadecimal value specified in the char attribute from the font specified in the font attribute.

[Example: Consider a run containing the following run content:

This is a symbol character:

The last character in that run is a symbol character from the Wingdings font, and the run is specified as follows:

<w:r> <w:rPr> <w:rFonts w:ascii="Courier New" w:hAnsi="Courier New" /> </w:rPr> <w:t>This is a symbol character:</w:t> <w:sym w:font="Wingdings" w:code="F03A" /></w:r>

The resulting symbol is the specified using the sym element, and consists of character code 003A formatted as Wingdings, even though the run properties specify the Courier New font. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

char (Symbol Character Code)

Specifies the hexadecimal code for the Unicode character value of the symbol.

When this value is stored in the char attribute, it may be stored in either of the following two formats:

Directly in its Unicode character value from the font glyph

In a Unicode character value created by adding F000 to the actual character value, shifting the character value of this character into the Unicode private use area.

[Note: The use of the latter syntax allows for interoperability with legacy word processing formats, as they used this technique to store the fact that a particular character or set of characters came from a font which was not Unicode compliant, and therefore any font matching performed on this range (if the specified font was not present) would be undesirable, as the resulting glyphs and their appearance could not be predicted. end note]

[Example: Consider a run with a single symbol character defined as follows:

<w:r> <w:rPr> <w:rFonts w:ascii="Arial Black" w:hAnsi="Arial Black" /> </w:rPr> <w:sym w:font="Wingdings" w:char="F045" /></w:r>

The symbol character shall use the font defined in its font attribute and hence use the Wingdings font. The character value for the character to be used from this font is obtained by removing the F000 value from the value in the char attribute, and therefore is the character at hexadecimal position 0045 in that font. end example]

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

font (Symbol Character Font)

Specifies a font which shall be used to format this symbol character.

[Example: Consider a run with a single symbol character defined as follows:

<w:r> <w:rPr> <w:rFonts w:ascii="Arial Black" w:hAnsi="Arial Black" /> </w:rPr> <w:sym w:font="Wingdings" w:char="F045" /></w:r>

Although the run specifies that its contents shall use the Arial Black font, the symbol character shall use the font defined in its font attribute and hence use the Wingdings font. end example]

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

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

</complexType>

t (Text)

This element specifies that this run contains literal text which shall be displayed in the document. The t element shall be used for all text runs which is not:

Part of a region of text that is contained in a deleted region using the del element (§2.13.5.12)

Part of a region of text that is contained within a field code

[Example: Consider a paragraph of WordprocessingML content which reads This is text. This paragraph would therefore be represented as follows:

<w:p> <w:r> <w:t>This is text</w:t> </w:r></w:p>

The text is contained in a t node. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

space (Content Contains Significant Whitespace)

Namespace: http://www.w3.org/XML/1998/namespace

Specifies how white space should be handled for the contents of this element using the W3C space preservation rules.

[Example: Consider the following run contained within a WordprocessingML document:

<w:r> <w:t>significant whitespace </w:t></w:r>

The possible values for this attribute are defined by the type in the namespace.

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

</extension>

</simpleContent>

</complexType>

tab (Tab Character)

This element specifies that a tab character shall be placed at the current location in the run content. An tab is a character which is used to advance the position on the current line of text when displaying this WordprocessingML content, using the following logic:

When there are one or more custom tab stops defined using the tabs element (§2.3.1.38) , then the tab character shall advance to the next custom tab stop location which is further along than the starting location of the tab

When there are no custom tab stops which are further than the current position in the line, the tab character shall advance to the nearest multiple of the defaultTabStop element (§2.15.1.24) width value.

<w:pPr>

<w:tabs>

<w:tab w:val="left" w:pos="2160" />

<w:tab w:val="left" w:pos="5040" />

</w:tabs>

</w:pPr>

If a tab character was added to a run in this paragraph and appeared 1.4” along the line after all preceding content was laid out, then this tab would move the position to 1.5”. If the tab character appeared 1.6” along the line after all preceding content was laid out, then this tab would move the position to 3.5”. In both cases, the tab advanced to the next custom tab stop. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

yearLong (Date Block - Long Year Format)

This element specifies the presence of a date block at the current location in the run content. A date block is a non-editable region of text which shall display the current date filtered through the specified date picture (see following paragraphs). [Note: The date block is a legacy construct used for compatibility with older word processors, and should not be produced unless it was consumed while reading a document – it is recommended that the DATE field is used in its place. end note]

A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

The long year format date block shall use a date picture of YYYY, retrieving the long year format for the primary editing language.

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is a long date: </w:t> <w:yearLong /></w:r>

This run specifies that a long year format date block shall be placed after the text string literal This is a long date: in the document. Assuming that the host application’s primary editing language is English (Canada) and today’s date is 04/12/2006 (a Wednesday), this run would be displayed as follows:

This is a long date: 2006

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

yearShort (Date Block - Short Year Format)

This element specifies the presence of a date block at the current location in the run content. A date block is a non-editable region of text which shall display the current date filtered through the specified date picture (see following paragraphs). [Note: The date block is a legacy construct used for compatibility with older word processors, and should not be produced unless it was consumed while reading a document – it is recommended that the DATE field is used in its place. end note]

A date block shall be displayed using the primary editing language of the host application, regardless of the languages specified in the parent run’s lang property (§2.3.2.18).

The short year format date block shall use a date picture of YY, retrieving the short year format for the primary editing language.

[Example: Consider a WordprocessingML run with the following run content:

<w:r> <w:t xml:space="preserve">This is a short date: </w:t> <w:yearShort /></w:r>

This run specifies that a short year format date block shall be placed after the text string literal This is a short date: in the document. Assuming that the host application’s primary editing language is French (Canada) and today’s date is 04/12/2006 (a Wednesday), this run would be displayed as follows:

This is a short date: 06

end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

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

Tables

Another type of block-level content in WordprocessingML, a table is a set of paragraphs (and other block-level content) arranged in rows and columns. Tables in WordprocessingML are defined via the tbl element, which is analogous to the HTML <table> tag. The table element specifies the location of a table present in the document.

A tbl element (§2.4.36) has two elements that define its properties:

tblPr (§2.4.55), which defines the set of table-wide properties (such as style and width)

tblGrid (§2.4.44), which defines the grid layout of the table.

A tbl element can also contain an arbitrary non-zero number of rows, where each row is specified with a tr element (§2.4.75). Each tr element can contain an arbitrary non-zero number of cells, where each cell is specified with a tc element (§2.4.62).

[Example: Consider an empty one-cell table (i.e.; a table with one row, one column) and 1 point borders on all sides as follows:

This table is represented by the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblW w:w="5000" w:type="pct"/> <w:tblBorders> <w:top w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:left w:val="single" w:sz="4 w:space="0" w:color="auto"/> <w:bottom w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:right w:val="single" w:sz="4" w:space="0" w:color="auto"/> </w:tblBorders> </w:tblPr> <w:tblGrid> <w:gridCol w:w="10296"/> </w:tblGrid> <w:tr> <w:tc> <w:tcPr> <w:tcW w:w="0" w:type="auto"/> </w:tcPr> <w:p/> </w:tc> </w:tr></w:tbl>

This table specifies table-wide properties of 100% of page width using the tblW element and the set of table borders using the tblBorders element, the table grid which defines a set of shared vertical edges within the table using the tblGrid element, and a single row using the tr element. end example]

bidiVisual (Visually Right to Left Table)

This element specifies that the cells with this table shall be visually represented in a right to left direction. This element also affects the application of all table-level properties.

When this property is specified, then the ordering of all cells (and table-level properties) in this table shall be applied to the table assuming that the table is a normal left to right table, but the table cells shall be displayed in a right to left direction. [Example: A left border on the first table cell shall be displayed on the right side of that cell (which would be the rightmost cell) in a visually right to left table. end example]

If this element is omitted, then the table shall not be presented right to left.

[Example: Consider the following table which has the logical right to left property set:

One

Two

Three

This property would be specified in the WordprocessingML as follows:

<w:tblPr>

<w:bidiVisual/>

</w:tblPr>

Since the bidiVisual element specifies this is a visually right to left table, the actual table data would be stored in its logical order as follows:

<w:tr> <w:tc> <w:p> <w:r> <w:t>One</w:t> </w:r> </w:p> </w:tc>

<w:tc> <w:p> <w:r> <w:t>Two</w:t> </w:r> </w:p> </w:tc>

<w:tc> <w:p> <w:r> <w:t>Three</w:t> </w:r> </w:p> </w:tc>

<w:tc> <w:p/> </w:tc></w:tr>

The first logical cell with text One is stored first in the file format, and displayed on the rightmost in this table visually. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

bottom (Table Cell Bottom Margin Exception)

This element specifies the amount of space which shall be left between the bottom extent of the cell contents and the border of a specific table cell within a table. This setting shall override the table cell bottom margin definition specified by the bottom element contained within the table properties (§2.4.5).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If omitted, then this table cell shall use the bottom cell margins defined in the bottom element contained within the table properties (§2.4.5).

[Example: Consider a table with two cells in which the first table cell’s bottom margin is specified via an exception to be ten times larger (0.2 inches vs. 0.02 inches) than the other table cell margins:

This text fills the extents of the cell.

So does this

The first cell in the table would be specified using the following WordprocessingML:

<w:tc> <w:tcPr> <w:tcMar> <w:bottom w:w="288" w:type="dxa" /> </w:tcMar> </w:tcPr></w:tc>

The first cell in this table has an exception applied to the table cell bottom cell margin setting it to 288 twentieths of a point (0.2 inches). end example]

Parent Elements

tcMar (§2.4.65)

Attributes

Description

type (Table Width Type)

Specifies the units of the width property being defined by the parent element’s w attribute. This property is used to define various properties of a table, including: cell spacing, preferred width, and table margins.

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

Specifies the value of the width property being defined by the parent element. This property is used to define various properties of a table, including: cell spacing, preferred widths, and table margins.

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

The value in the w attribute shall therefore be used to determine the width being specified in the context of the units specified in the type attribute. In this case, the type is twentieths of a point (dxa), so the width is 302 twentieths of a point (.2097 inches). end example]

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

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

</complexType>

bottom (Table Cell Bottom Border)

This element specifies the border which shall be displayed at the bottom of the current table cell. The appearance of this table cell border in the document shall be determined by the following settings:

If the net tblCellSpacing element value (§2.4.41;§2.4.42;§2.4.43) applied to the cell is non-zero, then the cell border shall always be displayed

Otherwise, the display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the bottom of this table cell shall not have a cell border, and its border may use the table's border settings as appropriate.

[Example: Consider a table in which the first cell in the first row specifies a bottom cell border

R1C1

R1C2

R2C1

R2C2

This bottom cell border is specified using the following WordprocessingML:

<w:tc> <w:tcPr> … <w:tcBorders> <w:bottom w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> </w:tcBorders> </w:tcPr> <w:p/></w:tc>

The bottom element specifies a three point border of type thinThinThickSmallGap. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

bottom (Table Bottom Border)

This element specifies the border which shall be displayed at the bottom of the current table. The appearance of this table border in the document shall be determined by the following settings:

The display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the bottom of this table shall have the border specified by the associated table style. If no bottom border is specified in the style hierarchy, then this table shall not have a bottom border.

[Example: Consider a table in which the table properties specifies a bottom table border, as follows:

R1C1

R1C2

R2C1

R2C2

This bottom table border is specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblBorders> <w:bottom w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="D0D0D0" w:themeColor="accent3" w:themeTint="99"/> </w:tblBorders> </w:tblPr> …</w:tbl>

The bottom element specifies a three point bottom table border of type thinThinThickMediumGap. end example]

Parent Elements

tblBorders (§2.4.37); tblBorders (§2.4.38)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

bottom (Table Cell Bottom Margin Default)

This element specifies the amount of space which shall be left between the bottom extent of the cell contents and the border of all table cells within the parent table (or table row). This setting may be overridden by the table cell bottom margin definition specified by the bottom element contained within the table cell's properties (§2.4.2).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If this element is omitted, then it shall inherit the table cell margin from the associated table style. If a bottom margin is never specified in the style hierarchy, then this table shall have no bottom cell padding by default (excepting individual cell overrides).

[Example: Consider a two by two table in which the default table cell bottom margin is specified to be exactly 0.25 inches, as follows (marked with an arrow in the first table cell below):

R1C1

R2C1

R2C2

This table property is specified using the following WordprocessingML markup:

<w:tbl> <w:tblPr> <w:tblCellMar> <w:bottom w:w="360" w:type="dxa"/> </w:tblCellMar> </w:tblPr> …</w:tbl>

Every cell in the table has a default cell margin setting it to 360 twentieths of a point. end example]

Parent Elements

tblCellMar (§2.4.39); tblCellMar (§2.4.40)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

cantSplit (Table Row Cannot Break Across Pages)

This element specifies whether the contents within the current cell shall be rendered on a single page. When displaying the contents of a table cell (such as the table cells in this specification), it is possible that a page break would fall within the contents of a table cell, causing the contents of that cell to be displayed across two different pages. If this property is set, then all contents of a table row shall be rendered on the same page by moving the start of the current row to the start of a new page if necessary. If the contents of this table row cannot fit on a single page, then this row shall start on a new page and flow onto multiple pages as necessary.

If this element is not present, the default behavior is dictated by the setting in the associated table style. If this property is not specified in the style hierarchy, then this table row shall be allowed to split across multiple pages.

[Example: Consider the following content displayed on two different pages of a WordprocessingML document:

When this content is displayed, the contents of the 2nd table row in this document are displayed across two different pages. If the contents of this row are to be displayed on one page, then this requirement would be specified as follows:

<w:tr> <w:trPr> … <w:cantSplit /> </w:trPr> …</w:tr>

The presence of the cantSplit element specifies that the table row shall not be broken across multiple pages, therefore the second table row starts on a new page:

This setting therefore ensures that the content will always be displayed on a single page (if it fits on one page). end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

cnfStyle (Table Cell Conditional Formatting)

This element specifies the set of conditional table style formatting properties which have been applied to this table cell. [Note: This property is an optimization which is used by consumers to determine if a given property on a table cell is the result of the table style conditional formatting properties vs. direct formatting on the table cell itself. It specifies the components of the conditional formatting in the table style applied to this cell, so that the table's conditional formatting can be applied after the document is displayed without having the table style properties override the style hierarchy. end note]

If this element is omitted, then its value shall be assumed to be zero for all entries in the bit mask.

[Example: Consider a table cell in the top right corner of a table with a table style applied. This table cell would need to specify the following WordprocessingML to express that fact:

<w:tc>

<w:tcPr>

<w:cnfStyle w:val="101000000100" />

…

</w:tcPr>

…

</w:tc>

This table cell specifies that it has the conditional properties from the table style for the first column, first row, and the top left corner of the parent table by setting the appropriate bits in the val attribute. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (Conditional Formatting Bit Mask)

Specifies the set of conditional formatting properties that have been applied to this object.

These properties are expressed using a string serialization of a binary bitmask for each of the following properties (reading from the first character position right):

First Row - Is this the first row of the table?

Last Row - Is this the last row of the table?

First Column - Does this belong to the first column of the table?

Last Column - Does this belong to the last column of the table?

Band 1 Horizontal - Does this receive band 1 formatting? This property specifies whether the cell should receive the formatting specified for odd-numbered rows (e.g. 1,3,5,...)

Band 2 Horizontal - Does this receive band 2 formatting? This property specifies whether the cell should receive the formatting specified for even-numbered rows (e.g. 2,4,6...)

NE Cell - Is this part of the top-right corner of the table?

NW Cell - Is this part of the top-left corner of the table?

SE Cell - Is this part of the bottom-right corner of the table?

SW Cell - Is this part of the bottom-left corner of the table?

For each of these properties, a value of 1 in the specified character position in the string means that the value is true, a value of 0 means false. All values must be specified.

[Example: Consider a paragraph in the top right corner of a table with a table style applied. This paragraph would need to specify the following WordprocessingML:

<w:p>

<w:pPr>

<w:cnfStyle w:val="101000000100" />

...

</w:pPr>

...

</w:p>

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

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

</complexType>

cnfStyle (Table Row Conditional Formatting)

This element specifies the set of conditional table style formatting properties which have been applied to this table row. [Note: This property is an optimization which is used by consumers to determine if a given property on a table row is the result of the table style conditional formatting properties vs. direct formatting on the table cell itself. It specifies the components of the conditional formatting in the table style applied to this cell, so that the table's conditional formatting can be applied after the document is displayed without having the table style properties override the style hierarchy. end note]

If this element is omitted, then its value shall be assumed to be zero for all entries in the bit mask.

[Example: Consider a table row in the top of a table with a table style applied. This table cell would need to specify the following WordprocessingML to express that fact:

<w:tr>

<w:trPr>

<w:cnfStyle w:val="100000000000" />

…

</w:trPr>

…

</w:tr>

This table row specifies that it has the conditional properties from the table style for the first row of the parent table by setting the appropriate bits in the val attribute. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (Conditional Formatting Bit Mask)

Specifies the set of conditional formatting properties that have been applied to this object.

These properties are expressed using a string serialization of a binary bitmask for each of the following properties (reading from the first character position right):

First Row - Is this the first row of the table?

Last Row - Is this the last row of the table?

First Column - Does this belong to the first column of the table?

Last Column - Does this belong to the last column of the table?

Band 1 Horizontal - Does this receive band 1 formatting? This property specifies whether the cell should receive the formatting specified for odd-numbered rows (e.g. 1,3,5,...)

Band 2 Horizontal - Does this receive band 2 formatting? This property specifies whether the cell should receive the formatting specified for even-numbered rows (e.g. 2,4,6...)

NE Cell - Is this part of the top-right corner of the table?

NW Cell - Is this part of the top-left corner of the table?

SE Cell - Is this part of the bottom-right corner of the table?

SW Cell - Is this part of the bottom-left corner of the table?

For each of these properties, a value of 1 in the specified character position in the string means that the value is true, a value of 0 means false. All values must be specified.

[Example: Consider a paragraph in the top right corner of a table with a table style applied. This paragraph would need to specify the following WordprocessingML:

<w:p>

<w:pPr>

<w:cnfStyle w:val="101000000100" />

...

</w:pPr>

...

</w:p>

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

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

</complexType>

divId (Associated HTML div ID)

This element specifies the HTML div information which is associated with the current table row. This information, stored in the Web Settings part, is used to associate one or more table rows with a particular HTML div element. [Note: This property is used when saving an HTML document into the WordprocessingML format in order to prevent a loss of all HTML div information, so that the document can later be saved back into HTML format and have the stored information replaced, since the HTML div can store formatting properties on arbitrary regions. end note]

In order to determine the associated HTML div properties, the value of the val attribute on this element is used to look up an associated div element (§2.15.2.8) whose id attribute matches this value.

If this table row does not have a divId element present, then this table row shall not have any associated HTML div information. If this element is present, but the val attribute specifies an id value which does not have an associated div element, then this element is ignored.

[Example: Consider an HTML document defined as follows:

This HTML document specifies a div spanning the table and the first paragraph. If this document is saved into WordprocessingML, then both the rows of the table and the paragraph shall have a divId which points at the same div information in the web settings part:

<w:trPr> … <w:divId w:val="1102603671"/></w:trPr>

The val attribute then points at a div element which stores the associated div properties:

<w:divs> <w:div w:id="1102603671"> … </w:div></w:divs>

This specifies that this table's rows are part of a single HTML div. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

gridAfter (Grid Columns After Last Cell)

This element specifies the number of grid columns in the parent table's table grid (§2.4.44; §2.4.45) which shall be left after the last cell in the table row.

If this element conflicts with the remaining size of the document grid after all table cells in this row have been added to the grid, then it shall be ignored. If this element is not specified, then its value shall be assumed to be zero grid units.

[Example: Consider a table whose second row ends before the first row by one grid unit:

In this table, the second row leaves one grid unit after its cell contents, which is represented using the following WordprocessingML:

<w:tr>

<w:trPr>

<w:gridAfter w:val="1" />

…

</w:trPr>

…

</w:tr>

The gridAfter element specifies that 1 grid unit remains after the row's contents. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

gridBefore (Grid Columns Before First Cell)

This element specifies the number of grid columns in the parent table's table grid (§2.4.44; §2.4.45) which shall be skipped before the contents of this table row (its table cells) are added to the parent table. [Note: This property is used to specify tables whose leading edge (left for left-to-right tables, right for right-to-left tables) does not start at the first grid column (the same shared edge). end note]

If this element is omitted, then its value shall be assumed to be zero grid units. If this element's value is larger than the size of the table grid, then the value shall be ignored and the first cell in the row may span the full table grid (i.e. the second cell, if one exists, should start at the last shared edge in the table).

[Example: Consider a table whose second row starts after the first grid unit:

In this table, the second row skips one grid unit at the beginning which is represented by the following WordprocessingML:

<w:tr>

<w:trPr>

<w:gridBefore w:val="1" />

…

</w:trPr>

…

</w:tr>

end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

gridCol (Grid Column Definition)

This element specifies the presence and details about a single grid column within a table grid. A grid column is a logical column in a table used to specify the presence of a shared vertical edge in the table. When table cells are then added to this table, these shared edges (or grid columns, looking at the column between those shared edges) determine how table cells are placed into the table grid.

[Example: If a table row specifies that it is preceded by two grid columns, then it would start on the third vertical edge in the table including edges which are not shared by all columns. end example]

If the table grid does not match the requirements of one or more rows in the table (i.e. it does not define enough grid columns), then the grid may be redefined as needed when the table is processed.

[Example: Consider the following, more complex table that has two rows and two columns; as shown, the columns are not aligned:

This table is represented by laying out the cells on a table grid consisting of three table grid columns as follows, each grid column representing a logical vertical column in the table:

The dashed lines represent the virtual vertical continuations of each table grid column, and thus resulting table grid is represented as the following in WordprocessingML:

<w:tblGrid>

<w:gridCol w:w="5051" />

<w:gridCol w:w="3008" />

<w:gridCol w:w="1531" />

</w:tblGrid>

end example]

Parent Elements

tblGrid (§2.4.44); tblGrid (§2.4.45)

Attributes

Description

w (Grid Column Width)

Specifies the width of this grid column.

[Note: This value does not solely determine the actual width of the resulting grid column in the document. When the table is displayed in a document, these widths determine the initial width of each grid column, which may then be overridden by:

The table layout algorithm (§2.4.49;§2.4.50) applied to the current table row(s)

The preferred widths of specific cells which are part of that grid column as the table is displayed (which is an input to the algorithm above)

end note]

This value is specified in twentieths of a point.

If this attribute is omitted, then the last saved width of the grid column is assumed to be zero.

[Example: Consider the following table grid definition:

<w:tblGrid>

<w:gridCol w:w="6888"/>

<w:gridCol w:w="248"/>

<w:gridCol w:w="886"/>

<w:gridCol w:w="1554"/>

</w:tblGrid>

This table grid specifies four grid columns, each of which has an initial size of 6888 twentieths of a point, 248 twentieths of a point, 886 twentieths of a point, and 1554 twentieths of a point respectively. end example]

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

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

</complexType>

gridSpan (Grid Columns Spanned by Current Table Cell)

This element specifies the number of grid columns in the parent table's table grid which shall be spanned by the current cell. This property allows cells to have the appearance of being merged, as they span vertical boundaries of other cells in the table.

If this element is omitted, then the number of grid units spanned by this cell shall be assumed to be one. If the number of grid units specified by the val attribute exceeds the size of the table grid, then the table grid shall be augmented as needed to create the number of grid columns required.

[Example: Consider the following table that has two rows and two columns where the columns are not aligned:

This table is represented by laying out the cells on a table grid consisting of three table grid columns, each grid column representing a logical vertical column in the table:

The first table cell in the first row spans two grid column units. The second cell in the second row also consumes two grid column units (see the grid lines represented using dotted lines in the example above). This table is represented using the following WordprocessingML:

<w:tbl> … <w:tr> <w:tc> <w:tcPr> … <w:gridSpan w:val="2" /> </w:tcPr> … </w:tc> … </w:tr>

<w:tr> <w:tc> … </w:tc> <w:tc> <w:tcPr> … <w:gridSpan w:val="2" /> </w:tcPr> … </w:tc> </w:tr></w:tbl>

The gridSpan element indicates the number of columns spanned by each cell with respect to the table grid (in the case of R1C1 and TR2C2, two. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

hidden (Hidden Table Row Marker)

This element specifies that the glyph representing the end character of current table row shall not be displayed in the current document.

[Note: This setting is used to hide the end of row glyph in order to ensure that the entire table row is hidden and not displayed in the document, as if any part of the row is visible, the row is displayed. end note]

[Note: Applications may have settings which allow hidden content to be displayed, in which case this content may be visible - this property is not meant to supersede that setting. end note]

If this element is omitted, then this table row shall not be hidden in the document.

[Example: Consider a table with a table row in which the row is specified to be hidden. That requirement is specified using the following WordprocessingML:

<w:tbl> … <w:tr> <w:trPr> <w:hidden /> … </w:trPr> … </w:tr></w:tbl>

In this example this row will not be displayed nor printed, as the hidden element is specified on in table row's properties. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

hideMark (Ignore End Of Cell Marker In Row Height Calculation)

This element specifies whether the end of cell glyph shall influence the height of the given table row in the table. If it is specified, then only printing characters in this cell shall be used to determine the row height.

[Rationale: Typically, the height of a table row is determined by the height of all glyphs in all cells in that row, including the non-printing end of cell glyph characters. However, if these characters are not formatted, they are always created with the document default style properties. This means that the height of a table row cannot ever be reduced below the size of the end of cell marker glyph without manually formatting each paragraph in that run.

In a typical document, this behavior is desirable as it prevents table rows from 'disappearing' if they have no content. However, if a table row is being used as a border (for example, by shading its cells or putting an image in them), then this behavior makes it impossible to have a virtual border that is reasonably small without formatting each cell's content directly. This setting specifies that the end of cell glyph shall be ignored for this cell, allowing it to collapse to the height of its contents without formatting each cell's end of cell marker, which would have the side effect of formatting any text ever entered into that cell. end rationale]

If this element is omitted, then the end of cell marker shall be included in the determination of the height of this row.

[Example: Consider the following WordprocessingML table:

Notice that the only printing content in this table row is displayed using 5 point font, yet the row height is influenced by the end of cell markers in the empty cells.

If each cell in the second row in this table was set to exclude the table cell from this calculation, using the following WordprocessingML:

<w:tcPr> <w:hideMark/></w:tcPr>

The resulting table shall exclude the cell markers from the row height calculation:

The hideMark element specified that each cell marker was excluded, resulting in the row height being defined by the actual run contents. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

hMerge (Horizontally Merged Cell)

This element specifies that this cell is part of a horizontally merged set of cells in a table. The val attribute on this element determines how this cell is defined with respect to the previous cell in the table (i.e. does this cell continue the horizontal merge or start a new merged group of cells).

[Note: This property is maintained for compatibility with legacy word processing documents which defined tables in this manner. Whenever possible, this form or horizontal merges should not be produced, and should be translated to the appropriate gridSpan (§2.4.13) settings on the table cells instead. end note]

If this element is omitted, then this cell shall not be part of any horizontally merged grouping of cells, and any horizontal merge group in the preceding cells shall be closed.

[Example: Consider a table with one row and three columns with the last two columns horizontally merged:

The second cell in the first row starts a merge that is completed in the right adjacent cell, resulting in the following WordprocessingML:

<w:tbl> … <w:tr> <w:tc> … </w:tc> <w:tc> <w:tcPr> <w:hmerge w:val="restart"/> </w:tcPr> … </w:tc> <w:tc> <w:tcPr> <w:hmerge/> </w:tcPr> … </w:tc> </w:tr></w:tbl>

The hmerge element defines the cells which are horizontally merged, and how each group is merged together. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (Horizontal Merge Type)

Specifies how the table cell is part of a horizontally merged region. This determine whether the cell should join onto an existing grouping of merged cells if any exist, or start a new group of merged cells. Refer to the simple type definition for a full description of each type.

If this attribute is omitted, its value shall be assumed to be continue.

[Example: Consider a table cell where a horizontal cell merge begins represented as the following WordprocessingML:

<w:tcPr>

<w:hmerge w:val="restart"/>

</w:tcPr>

The attribute value of restart specifies that this element shall start a new horizontally merged region in this table. end example]

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

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

</complexType>

insideH (Table Inside Horizontal Edges Border)

This element specifies the border which shall be displayed on all horizontal table cell borders which are not on an outmost edge of the parent table (all horizontal borders which are not the topmost or bottommost border). The appearance of this table cell border in the document shall be determined by the following settings:

The display of the border on interior edges is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the inside horizontal borders of this table shall have the border specified by the associated table style. If no inside horizontal edge border is specified in the style hierarchy, then this table shall not have an inside horizontal edge border.

[Example: Consider a table in which the table specifies a border on all interior horizontal and vertical edges, as follows:

R1C1

R1C2

R2C1

R2C2

This interior horizontal cell border is specified using the following WordprocessingML:

<w:tblPr> <w:tblBorders> <w:insideH w:val="doubleWave" w:sz="6" w:space="0" w:color="92D050"/> <w:insideV w:val="doubleWave" w:sz="6" w:space="0" w:color="92D050"/> </w:tblBorders> …</w:tblPr>

The insideH element specifies a ¾ point border of type doubleWave. end example]

Parent Elements

tblBorders (§2.4.37); tblBorders (§2.4.38)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

insideH (Table Cell Inside Horizontal Edges Border)

This element specifies the border which shall be displayed on all interior horizontal edges of the current group of table cells. [Note: Although individual table cells have no concept of an internal edge, which would render this property useless in most cases, it is used to determine the cell borders to apply to a specific group of cells as part of table conditional formatting in a table style, for example, the inside horizontal edges on the set of cells in the first column. end note]

The appearance of this table cell border in the document shall be determined by the following settings:

If the net tblCellSpacing element value (§2.4.41;§2.4.42;§2.4.43) applied to the cell is non-zero, then the cell border shall always be displayed

Otherwise, the display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the specified conditional formatting on the table shall not change the current set of internal edge borders on its set of table cells (i.e. their current setting shall remain unchanged).

[Example: Consider a table in which the conditional formatting on the first column specified in the associated table style specifies a double line red cell border for all internal horizontal lines as follows:

This inner horizontal edge cell border is specified using the following WordprocessingML:

<w:tblStylePr w:type="firstColumn"> <w:tcPr> <w:tcBorders> <w:insideH w:val="double" w:sz="4" w:space="0" w:color="FF0000"/> </w:tcBorders> </w:tcPr></w:tblStylePr>

The insideH element specifies a ¼ point border of type double. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

insideV (Table Cell Inside Vertical Edges Border)

This element specifies the border which shall be displayed on all interior vertical edges of the current group of table cells. [Note: Although individual table cells have no concept of an internal edge, which would render this property useless in most cases, it is used to determine the cell borders to apply to a specific group of cells as part of table conditional formatting in a table style, for example, the inside vertical edges on the set of cells in the header row. end note]

The appearance of this table cell border in the document shall be determined by the following settings:

If the net tblCellSpacing element value (§2.4.41;§2.4.42;§2.4.43) applied to the cell is non-zero, then the cell border shall always be displayed

Otherwise, the display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

[Example: Consider a table in which the conditional formatting on the header row in the associated table style specifies a double line red cell border for all internal vertical lines as follows:

This inner vertical edge cell border is specified using the following WordprocessingML:

<w:tblStylePr w:type="firstRow"> <w:tcPr> <w:tcBorders> <w:insideV w:val="double" w:sz="4" w:space="0" w:color="FF0000"/> </w:tcBorders> </w:tcPr></w:tblStylePr>

The insideV element specifies a ¼ point border of type double. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

insideV (Table Inside Vertical Edges Border)

This element specifies the border which shall be displayed on all vertical table cell borders which are not on an outmost edge of the parent table (all horizontal borders which are not the leftmost or rightmost border). The appearance of this table cell border in the document shall be determined by the following settings:

The display of the border on interior edges is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the inside vertical borders of this table shall have the border specified by the associated table style. If no inside vertical edge border is specified in the style hierarchy, then those cells in this table shall not have an inside vertical edge border.

[Example: Consider a table in which the table specifies a border on all interior horizontal and vertical edges, as follows:

R1C1

R1C2

R2C1

R2C2

This interior horizontal cell border is specified using the following WordprocessingML:

<w:tblPr> <w:tblBorders> <w:insideH w:val="doubleWave" w:sz="6" w:space="0" w:color="92D050"/> <w:insideV w:val="doubleWave" w:sz="6" w:space="0" w:color="92D050"/> </w:tblBorders> …</w:tblPr>

The insideV element specifies a ¾ point border of type doubleWave on all interior vertical edges. end example]

Parent Elements

tblBorders (§2.4.37); tblBorders (§2.4.38)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

jc (Table Alignment Exception)

This element specifies the alignment of the set of rows which are part of the current table properties exception list with respect to the text margins in the current section. When a table is placed in a WordprocessingML document that does not have the same width as the margins, this property is used to determine how the table is positioned with respect to those margins. The interpretation of property is reversed if the parent table is right to left using the bidiVisual element (§2.4.1).

If this property is omitted on a table, then the justification shall be determined by the default set of table properties on the parent table.

[Example: Consider the following WordprocessingML table, centered on the text margins with a subset of its rows justified to the left margin by a table property exception:

That exception would be specified using the following WordprocessingML:

<w:tblPrEx> <w:jc w:val="left"/></w:tblPrEx>

The jc element specifies that the rows which are part of the table properties exception table shall be left aligned with respect to the text margins. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

val (Alignment Type)

Specifies the justification which should be applied to the parent object within a document.

The possible values (see below) for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents.

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

<w:pPr>

<w:jc w:val="right" />

</w:pPr>

This paragraph is now right justified on the page, regardless of the paragraph or section settings. end example]

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

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

</complexType>

jc (Table Row Alignment)

This element specifies the alignment of a single row in the parent table with respect to the text margins in the current section. When a table is placed in a WordprocessingML document that does not have the same width as the margins, this property is used to determine how a specific row in that table is positioned with respect to those margins. The interpretation of property is reversed if the parent table is right to left using the bidiVisual element (§2.4.1).

If this property is omitted on a table, then the justification shall be determined by the default set of table properties on the parent table.

[Example: Consider the following WordprocessingML table, centered on the text margins with its second rows justified to the left margin by a table row level justification:

That row level setting would be specified using the following WordprocessingML:

<w:trPr> <w:jc w:val="left"/></w:trPr>

The jc element specifies that the rows which are part of the table properties exception table shall be left aligned with respect to the text margins. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (Alignment Type)

Specifies the justification which should be applied to the parent object within a document.

The possible values (see below) for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents.

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

<w:pPr>

<w:jc w:val="right" />

</w:pPr>

This paragraph is now right justified on the page, regardless of the paragraph or section settings. end example]

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

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

</complexType>

jc (Table Alignment)

This element specifies the alignment of the current table with respect to the text margins in the current section. When a table is placed in a WordprocessingML document that does not have the same width as the margins, this property is used to determine how the table is positioned with respect to those margins. The interpretation of property is reversed if the parent table is right to left using the bidiVisual element (§2.4.1).

If this property is omitted on a table, then the justification shall be determined by the associated table style. If this property is not specified in the style hierarchy, then the table shall be left justified with zero indentation from the leading margin (the left margin in a left-to-right table or the right margin in a right-to-left table).

[Example: Consider the following WordprocessingML table, justified to the left margin by default:

R1C1

R1C2

R1C3

R2C1

R2C2

R2C3

This table does not fill the entire width of the text margins. If the table should be right justified to the margin, as follows:

R1C1

R1C2

R1C3

R2C1

R2C2

R2C3

That requirement would be specified using the following WordprocessingML:

<w:tblPr> <w:jc w:val="right"/></w:tblPr>

The jc element specifies that the table shall be right aligned with respect to the text margins. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (Alignment Type)

Specifies the justification which should be applied to the parent object within a document.

The possible values (see below) for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents.

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

<w:pPr>

<w:jc w:val="right" />

</w:pPr>

This paragraph is now right justified on the page, regardless of the paragraph or section settings. end example]

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

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

</complexType>

left (Table Cell Left Border)

This element specifies the border which shall be displayed on the left side of the current table cell. The appearance of this table cell border in the document shall be determined by the following settings:

If the net tblCellSpacing element value (§2.4.41;§2.4.42;§2.4.43) applied to the cell is non-zero, then the cell border shall always be displayed

Otherwise, the display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the left side of this table cell shall not have a cell border, and its border may use the table's border settings as appropriate.

[Example: Consider a table in which the second cell in the first row specifies a left cell border

R1C1

R1C2

R2C1

R2C2

This left cell border is specified using the following WordprocessingML:

<w:tc> <w:tcPr> … <w:tcBorders> <w:left w:val="double" w:sz="4" w:space="0" w:color="FF0000" /> </w:tcBorders> </w:tcPr> <w:p/></w:tc>

The left element specifies a point border of type double on the table cell. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

left (Table Cell Left Margin Exception)

This element specifies the amount of space which shall be left between the left extent of the current cell contents and the left border of a specific individual table cell within a table. This setting shall override the table cell bottom margin definition specified by the left element contained within the table properties (§2.4.26).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If omitted, then this table cell shall use the bottom cell margins defined in the left element contained within the table properties (§2.4.26).

[Example: Consider a two row, two column table in which the first table cell in the second row has a left margin which is specified via an exception to be 0.5 inches, causing the text to be position 0.5" inside the cell, as follows:

R1C1

R1C2

R2C1

R2C2

The exception on this cell would be specified using the following WordprocessingML:

<w:tc> <w:tcPr> <w:tcMar> <w:left w:w="720" w:type="dxa" /> </w:tcMar> </w:tcPr></w:tc>

The R2C1 cell in this table has an exception applied to the table cell left cell margin setting it to 720 twentieths of a point (0.5 inches). end example]

Parent Elements

tcMar (§2.4.65)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

left (Table Cell Left Margin Default)

This element specifies the amount of space which shall be left between the left extent of the cell contents and the left border of all table cells within the parent table (or table row). This setting may be overridden by the table cell bottom margin definition specified by the left element contained within the table cell's properties (§2.4.26).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If this element is omitted, then it shall inherit the table cell margin from the associated table style. If a left margin is never specified in the style hierarchy, this table shall have 115 twentieths of a point (0.08 inches) left cell padding by default (excepting individual cell overrides).

[Example: Consider a two by two table in which the default table cell left margin is specified to be exactly 0.25 inches, as follows (marked with an arrow in the first table cell below):

R1C1

R2C1

R2C2

This table property is specified using the following WordprocessingML markup:

<w:tbl> <w:tblPr> <w:tblCellMar> <w:left w:w="360" w:type="dxa"/> </w:tblCellMar> </w:tblPr> …</w:tbl>

Every cell in the table has a default left cell margin setting it to 360 twentieths of a point. end example]

Parent Elements

tblCellMar (§2.4.39); tblCellMar (§2.4.40)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

left (Table Left Border)

This element specifies the border which shall be displayed at the left edge of the current table. The appearance of this table border in the document shall be determined by the following settings:

The display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the left edge of this table shall have the border specified by the associated table style. If no left border is specified in the style hierarchy, then this table shall not have a left border.

[Example: Consider a table in which the table properties specify a left table border, as follows:

R1C1

R1C2

R2C1

R2C2

This left table border is specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblBorders> <w:left w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="D0D0D0" w:themeColor="accent3" w:themeTint="99"/> </w:tblBorders> </w:tblPr> …</w:tbl>

The left element specifies a three point left table border of type thinThinThickMediumGap. end example]

Parent Elements

tblBorders (§2.4.37); tblBorders (§2.4.38)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

noWrap (Don't Wrap Cell Content)

This element specifies how this table cell shall be laid out when the parent table is displayed in a document. This setting only affects the behavior of the cell when the tblLayout for this row (§2.4.49; §2.4.50) is set to use the auto algorithm.

This setting shall be interpreted in the context of the tcW element (§2.4.68) as follows:

If the table cell width has a type attribute value of fixed, then this element specifies that that this table cell shall never be smaller than that fixed value when other cells on the line are not at their absolute minimum width.

If the table cell width has a type attribute value of pct or auto, then this element specifies that when running the auto fit algorithm, the contents of that this table cell shall be treated as though they have no breaking characters (the contents should be treated as a single contiguous non-breaking string)

If this element is omitted, then cell content shall be allowed to wrap (the cell may be shrunk as needed if it is a fixed preferred width value, and the contents shall be treated as having breaking characters if it is a percentage or automatic width value).

[Example: Consider the following three row by three column WordprocessingML table:

In this table, each cell has a fixed preferred width of 2.38 inches (3427 twentieths of a point), and the tblLayout for this row (§2.4.49; §2.4.50) is set to use the auto algorithm. If a long non breaking string is added to the middle row, as follows, the two cells are adjusted to override their preferences and accommodate the string:

sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

However, if the first table cell has the noWrap element present as follows:

<w:tcPr> <w:noWrap/></w:tcPr>

The noWrap element specifies that because it is a fixed width cell, that cell shall not be collapsed beyond its original size until all other cells are at their minimum size, so in this example the cell maintains its width:

sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss

end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

right (Table Cell Right Margin Default)

This element specifies the amount of space which shall be present between the right extent of the cell contents and the right border of all table cells within the parent table (or table row). This setting may be overridden by the table cell bottom margin definition specified by the right element contained within the table cell's properties (§2.4.31).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If this element is omitted, then it shall inherit the table cell margin from the associated table style. If a right margin is never specified in the style hierarchy, this table shall have 115 twentieths of a point (0.08 inches) left cell padding by default (excepting individual cell overrides).

[Example: Consider a two by two table in which the default table cell right margin is specified to be exactly 0.25 inches, as follows (marked with an arrow in the first table cell below):

R1C1

R2C1

R2C2

This table property is specified using the following WordprocessingML markup:

<w:tbl> <w:tblPr> <w:tblCellMar> <w:right w:w="360" w:type="dxa"/> </w:tblCellMar> </w:tblPr> …</w:tbl>

Every cell in the table has a default right cell margin setting it to 360 twentieths of a point. end example]

Parent Elements

tblCellMar (§2.4.39); tblCellMar (§2.4.40)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

right (Table Cell Right Border)

This element specifies the border which shall be displayed on the right side of the current table cell. The appearance of this table cell border in the document shall be determined by the following settings:

If the net tblCellSpacing element value (§2.4.41;§2.4.42;§2.4.43) applied to the cell is non-zero, then the cell border shall always be displayed

Otherwise, the display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the right side of this table cell shall not have a cell border, and its border may use the table's border settings as appropriate.

[Example: Consider a table in which the second cell in the first row specifies a right cell border as follows:

R1C1

R1C2

R2C1

R2C2

This right cell border is specified using the following WordprocessingML:

<w:tc> <w:tcPr> … <w:tcBorders> <w:right w:val="double" w:sz="4" w:space="0" w:color="FF0000" /> </w:tcBorders> </w:tcPr> <w:p/></w:tc>

The right element specifies a point border of type double on the right side of the table cell. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

right (Table Cell Right Margin Exception)

This element specifies the amount of space which shall be present between the right extent of the current cell's text contents and the right border of a specific individual table cell within a table. This setting shall override the table cell bottom margin definition specified by the right element contained within the table properties (§2.4.29).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If omitted, then this table cell shall use the bottom cell margins defined in the right element contained within the table properties (§2.4.29).

[Example: Consider a two row, two column table in which the first table cell in the second row has a right margin which is specified via an exception to be 0.5 inches, the region marked with an arrow in the table below:

R1C1

R1C2

R2C1

R2C2

The exception on this cell would be specified using the following WordprocessingML:

<w:tc> <w:tcPr> <w:tcMar> <w:right w:w="720" w:type="dxa" /> </w:tcMar> </w:tcPr>

…</w:tc>

The R2C1 cell in this table has an exception applied to the table cell right cell margin setting it to 720 twentieths of a point (0.5 inches). end example]

Parent Elements

tcMar (§2.4.65)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

right (Table Right Border)

This element specifies the border which shall be displayed at the right edge of the current table. The appearance of this table border in the document shall be determined by the following settings:

The display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the right edge of this table shall have the border specified by the associated table style. If no right border is specified in the style hierarchy, then this table shall not have a right border.

[Example: Consider a table in which the table properties specify a right table border, as follows:

R1C1

R1C2

R2C1

R2C2

This right table border is specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblBorders> <w:right w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="D0D0D0" w:themeColor="accent3" w:themeTint="99"/> </w:tblBorders> </w:tblPr> …</w:tbl>

The right element specifies a three point right table border of type thinThinThickMediumGap. end example]

Parent Elements

tblBorders (§2.4.37); tblBorders (§2.4.38)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

shd (Table Cell Shading)

This element specifies the shading which shall be applied to the extents of the current table cell. Similarly to paragraph shading, this shading shall be applied to the contents of the cell up to the cell borders, regardless of the presence of text.

This shading consists of three components:

Background Color

(optional) Pattern

(optional) Pattern Color

The resulting shading is applied by setting the background color behind the paragraph, then applying the pattern color using the mask supplied by the pattern over that background.

If this element is omitted, then the cell shading shall be determined by the table-level or table-level exception cell shading settings (§2.4.34;§2.4.35) for the current table.

[Example: Consider a table in which the first cell in the first row has cell-level red shading, as follows:

R1C1

R1C2

R2C1

R2C2

This cell shading would be specified using the following WordprocessingML:

<w:tc> <w:tcPr> <w:shd w:val="clear" w:color="auto" w:fill="FF0000" /> </w:tcPr></w:tc>

The shd element specifies cell shading with a clear pattern using a background color of FF0000 (red). end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

color (Shading Pattern Color)

Specifies the color used for any foreground pattern specified for this shading using the val attribute.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the foreground shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading of type pct20 with a foreground color value of auto, as follows:

<w:shd w:val="pct20"... w:color="auto"/>

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

fill (Shading Background Color)

Specifies the color used for the background for this shading.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the background shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading using a background color of hex value C3D69B, using the following WordprocessingML:

<w:shd w:fill="C3D69B" />

The background color for this shading therefore will be a color with a hex value of C3D69B. end example]

If the shading specifies the use of a theme color via the themeFill attribute, then this value is superseded by the theme color value.

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

themeColor (Shading Pattern Theme Color)

Specifies a theme color which should be applied to any foreground pattern specified for this shading using the val attribute.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading pattern color.

<w:pPr>

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

</w:pPr>

The resulting paragraph will use the foreground pattern color accent6 in the region specified by the pct20 pattern mask. end example]

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

themeFill (Shading Background Theme Color)

Specifies a theme color which should be applied to the background for this shading.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading background color.

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

The resulting shading will use the background color specified by the accent3 theme color. end example]

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

themeFillShade (Shading Background Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeFillShade is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

The resulting themeFillShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting shading's fill attribute:

<w:shd w:fill="943634" w:themeFill="accent2" w:themeFillShade="BF" />

end example]

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

themeFillTint (Shading Background Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeFillTint is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeFillTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's fill attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:fill="95B3D7" w:themeFillColor="accent2" w:themeFillTint="99" />

end example]

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

themeShade (Shading Pattern Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeShade is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

Te resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:shd w:color="943634" w:themeColor="accent2" w:themeShade="BF" />

end example]

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

themeTint (Shading Pattern Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeTint is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's color attribute:

<w:shd w:color="95B3D7" w:themeColor="accent2" w:themeTint="99" />

end example]

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

val (Shading Pattern)

Specifies the pattern which shall be used to lay the pattern color over the background color for this paragraph shading.

[Example: Consider a shaded paragraph which uses a 10 percent foreground fill, resulting in the following WordprocessingML:

<w:shd w:val="pct10" .../>

This shading val is pct10, indicating that the border style is a 10 percent foreground fill mask. end example]

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

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

</complexType>

shd (Table Shading Exception)

This element specifies the shading which shall be applied to all cells in the current row as part of a set of table-level property exceptions. Similarly to paragraph shading, this shading shall be applied to the contents of the tab up to the table borders, regardless of the presence of text - unlike cell shading, table shading shall include any cell padding. This property shall be superseded by any cell-level shading on any cell in this row (§2.4.33).

This shading consists of three components:

Background Color

(optional) Pattern

(optional) Pattern Color

The resulting shading is applied by setting the background color behind the paragraph, then applying the pattern color using the mask supplied by the pattern over that background.

If this element is omitted, then the cell shading shall be determined by the table-level cell shading settings (§2.4.35) for the current table.

[Example: Consider a table in which the final two rows have a set of table-level property exceptions giving them theme color shading in the background2 theme color, as follows:

This table-level shading exception would be specified using the following WordprocessingML:

<w:tblPrEx>

<w:jc w:val="left" />

<w:shd w:val="clear" w:color="auto" w:fill="EEECE1" w:themeFill="background2" />

</w:tblPrEx>

The shd element specifies cell shading with a clear pattern using a background theme color of background2. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

color (Shading Pattern Color)

Specifies the color used for any foreground pattern specified for this shading using the val attribute.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the foreground shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading of type pct20 with a foreground color value of auto, as follows:

<w:shd w:val="pct20"... w:color="auto"/>

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

fill (Shading Background Color)

Specifies the color used for the background for this shading.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the background shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading using a background color of hex value C3D69B, using the following WordprocessingML:

<w:shd w:fill="C3D69B" />

The background color for this shading therefore will be a color with a hex value of C3D69B. end example]

If the shading specifies the use of a theme color via the themeFill attribute, then this value is superseded by the theme color value.

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

themeColor (Shading Pattern Theme Color)

Specifies a theme color which should be applied to any foreground pattern specified for this shading using the val attribute.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading pattern color.

<w:pPr>

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

</w:pPr>

The resulting paragraph will use the foreground pattern color accent6 in the region specified by the pct20 pattern mask. end example]

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

themeFill (Shading Background Theme Color)

Specifies a theme color which should be applied to the background for this shading.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading background color.

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

The resulting shading will use the background color specified by the accent3 theme color. end example]

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

themeFillShade (Shading Background Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeFillShade is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

The resulting themeFillShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting shading's fill attribute:

<w:shd w:fill="943634" w:themeFill="accent2" w:themeFillShade="BF" />

end example]

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

themeFillTint (Shading Background Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeFillTint is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeFillTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's fill attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:fill="95B3D7" w:themeFillColor="accent2" w:themeFillTint="99" />

end example]

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

themeShade (Shading Pattern Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeShade is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

Te resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:shd w:color="943634" w:themeColor="accent2" w:themeShade="BF" />

end example]

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

themeTint (Shading Pattern Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeTint is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's color attribute:

<w:shd w:color="95B3D7" w:themeColor="accent2" w:themeTint="99" />

end example]

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

val (Shading Pattern)

Specifies the pattern which shall be used to lay the pattern color over the background color for this paragraph shading.

[Example: Consider a shaded paragraph which uses a 10 percent foreground fill, resulting in the following WordprocessingML:

<w:shd w:val="pct10" .../>

This shading val is pct10, indicating that the border style is a 10 percent foreground fill mask. end example]

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

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

</complexType>

shd (Table Shading)

This element specifies the shading which shall be applied to the extents the current table. Similarly to paragraph shading, this shading shall be applied to the contents of the tab up to the table borders, regardless of the presence of text - unlike cell shading, table shading shall include any cell padding. This property shall be superseded by any cell-level shading via any table-level property exceptions (§2.4.34); or on any cell in this row (§2.4.33).

This shading consists of three components:

Background Color

(optional) Pattern

(optional) Pattern Color

The resulting shading is applied by setting the background color behind the paragraph, then applying the pattern color using the mask supplied by the pattern over that background.

If this element is omitted, then the cells within this table shall have the shading specified by the associated table style. If no cell shading is specified in the style hierarchy, then the cells in this table shall not have any cell shading (i.e. they shall be transparent).

[Example: Consider a table in which the first cell in the first row has cell-level red shading, as follows:

R1C1

R1C2

R2C1

R2C2

This table level cell shading would be specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:shd w:val="clear" w:color="auto" w:fill="FF0000"/> … </w:tblPr> …</w:tbl>

The shd element specifies cell shading with a clear pattern using a background color of FF0000 (red). end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

color (Shading Pattern Color)

Specifies the color used for any foreground pattern specified for this shading using the val attribute.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the foreground shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading of type pct20 with a foreground color value of auto, as follows:

<w:shd w:val="pct20"... w:color="auto"/>

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

fill (Shading Background Color)

Specifies the color used for the background for this shading.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the background shading color as appropriate.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider a shading using a background color of hex value C3D69B, using the following WordprocessingML:

<w:shd w:fill="C3D69B" />

The background color for this shading therefore will be a color with a hex value of C3D69B. end example]

If the shading specifies the use of a theme color via the themeFill attribute, then this value is superseded by the theme color value.

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

themeColor (Shading Pattern Theme Color)

Specifies a theme color which should be applied to any foreground pattern specified for this shading using the val attribute.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading pattern color.

<w:pPr>

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

</w:pPr>

The resulting paragraph will use the foreground pattern color accent6 in the region specified by the pct20 pattern mask. end example]

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

themeFill (Shading Background Theme Color)

Specifies a theme color which should be applied to the background for this shading.

The specified theme color is a reference to one of the predefined theme colors, located in the document's themes part, which allows for color information to be set centrally in the document.

If this element is omitted, then no theme color is applied, and the color attribute shall be used to determine the shading background color.

<w:shd w:val="pct20" w:themeColor="accent6" w:themeFill="accent3" />

The resulting shading will use the background color specified by the accent3 theme color. end example]

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

themeFillShade (Shading Background Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeFillShade is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

The resulting themeFillShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting shading's fill attribute:

<w:shd w:fill="943634" w:themeFill="accent2" w:themeFillShade="BF" />

end example]

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

themeFillTint (Shading Background Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeFillTint is supplied, then it is applied to the RGB value of the themeFill color (from the theme part) to determine the final color applied to this border.

The themeFillTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeFillTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's fill attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:fill="95B3D7" w:themeFillColor="accent2" w:themeFillTint="99" />

end example]

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

themeShade (Shading Pattern Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this shading color.

If the themeShade is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0 to 255) applied to the current border.

[Example: Consider a shade of 40% applied to a background shading color in a document. This shade is calculated as follows:

Te resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:shd w:color="943634" w:themeColor="accent2" w:themeShade="BF" />

end example]

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

themeTint (Shading Pattern Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this shading instance.

If the themeTint is supplied, then it is applied to the RGB value of the themeColor color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0 to 255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting shading's color attribute:

<w:shd w:color="95B3D7" w:themeColor="accent2" w:themeTint="99" />

end example]

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

val (Shading Pattern)

Specifies the pattern which shall be used to lay the pattern color over the background color for this paragraph shading.

[Example: Consider a shaded paragraph which uses a 10 percent foreground fill, resulting in the following WordprocessingML:

<w:shd w:val="pct10" .../>

This shading val is pct10, indicating that the border style is a 10 percent foreground fill mask. end example]

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

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

</complexType>

tbl (Table)

This element specifies the contents of a table present in the document. A table is a set of paragraphs (and other block-level content) arranged in rows and columns. Tables in WordprocessingML are defined via the tbl element, which is analogous to the HTML table tag.

[Example: Consider an empty one-cell table (i.e.; a table with one row, one column) and 1 point borders on all sides:

This table is represented by the following WordprocessingML:

This table specifies table-wide properties of 100% of page width using the tblW element (§2.4.61); a the set of table borders using the tblBorders element (§2.4.38); the table grid which defines a set of shared vertical edges within the table using the tblGrid element (§2.4.44); and a single table row using the tr element (§2.4.75). end example]

Parent Elements

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Row-Level Custom XML Element)

§2.5.1.4

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Row-Level Structured Document Tag)

§2.5.2.31

tblGrid (Table Grid)

§2.4.44

tblPr (Table Properties)

§2.4.55

tr (Table Row)

§2.4.75

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

</sequence>

</complexType>

tblBorders (Table Borders Exceptions)

This element specifies the set of borders for the edges of the parent table row via a set of table-level property exceptions, using the six border types defined by its child elements.

If the cell spacing for any row is non-zero as specified using the tblCellSpacing element (§2.4.41; §2.4.42; §2.4.43), then there is no border conflict and the table-level exception border shall be displayed.

If the cell spacing is zero, then there is a conflict [Example: Between the left border of all cells in the first column and the left border of the table-level exceptions. end example], which shall be resolved as follows:

If there is a cell border, then the cell border shall be displayed

If there is no cell border, then the table-level exception border shall be displayed

If this element is omitted, then this table shall have the borders specified by the associated table level borders (§2.4.38).

[Example: Consider a table in which the final two rows have a set of table-level property exceptions giving them a thicker set of table borders, as follows:

These table borders are specified via a set of table-level property exceptions using the following WordprocessingML:

<w:tr> <w:tblPrEx> <w:tblBorders> <w:top w:val="single" w:sz="24" w:space="0" w:color="000000" w:themeColor="text1"/> <w:left w:val="single" w:sz="24" w:space="0" w:color="000000" w:themeColor="text1"/> <w:bottom w:val="single" w:sz="24" w:space="0" w:color="000000" w:themeColor="text1"/> <w:right w:val="single" w:sz="24" w:space="0" w:color="000000" w:themeColor="text1"/> <w:insideH w:val="single" w:sz="24" w:space="0" w:color="000000" w:themeColor="text1"/> <w:insideV w:val="single" w:sz="24" w:space="0" w:color="000000" w:themeColor="text1"/> </w:tblBorders> </w:tblPrEx></w:tr>

The tblBorders element specifies the set of table borders applied to the final two rows in this table as part of the table-level property exceptions. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Child Elements

Subclause

bottom (Table Bottom Border)

§2.4.4

insideH (Table Inside Horizontal Edges Border)

§2.4.17

insideV (Table Inside Vertical Edges Border)

§2.4.20

left (Table Left Border)

§2.4.27

right (Table Right Border)

§2.4.32

top (Table Top Border)

§2.4.71

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

</sequence>

</complexType>

tblBorders (Table Borders)

This element specifies the set of borders for the edges of the current table, using the six border types defined by its child elements.

If the cell spacing for any row is non-zero as specified using the tblCellSpacing element (§2.4.41; §2.4.42; §2.4.43), then there is no border conflict and the table border (or table-level exception border, if one is specified) shall be displayed.

If the cell spacing is zero, then there is a conflict [Example: Between the left border of all cells in the first column and the left border of the table. end example], which shall be resolved as follows:

If there is a cell border, then the cell border shall be displayed

If there is no cell border but there is a table-level exception border on this table row, then the table-level exception border shall be displayed

If there is no cell or table-level exception border, then the table border shall be displayed

If this element is omitted, then this table shall have the borders specified by the associated table style. If no borders are specified in the style hierarchy, then this table shall not have any table borders.

[Example: Consider a table with no associated table style, which defines a set of table borders via direct formatting as follows:

These table borders are specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblW w:w="0" w:type="auto"/> <w:tblBorders> <w:top w:val="single" w:sz="4" w:space="0" w:color="000000" w:themeColor="text1"/> <w:left w:val="single" w:sz="4" w:space="0" w:color="000000" w:themeColor="text1"/> <w:bottom w:val="single" w:sz="4" w:space="0" w:color="000000" w:themeColor="text1"/> <w:right w:val="single" w:sz="4" w:space="0" w:color="000000" w:themeColor="text1"/> <w:insideH w:val="single" w:sz="4" w:space="0" w:color="000000" w:themeColor="text1"/> <w:insideV w:val="single" w:sz="4" w:space="0" w:color="000000" w:themeColor="text1"/> </w:tblBorders> … </w:tblPr> …</w:tbl>

The tblBorders element specifies the set of table borders applied to the current table. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Child Elements

Subclause

bottom (Table Bottom Border)

§2.4.4

insideH (Table Inside Horizontal Edges Border)

§2.4.17

insideV (Table Inside Vertical Edges Border)

§2.4.20

left (Table Left Border)

§2.4.27

right (Table Right Border)

§2.4.32

top (Table Top Border)

§2.4.71

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

</sequence>

</complexType>

tblCellMar (Table Cell Margin Defaults)

This element specifies the default cell margin settings for all cells in the current table. These setting may be overridden by the table cell margin definition specified by the tcMar element contained within the table cell's properties (§2.4.65) or by a set of table-level property exceptions (§2.4.40).

If this element is omitted, then it shall inherit the table cell margins from the associated table style. If table margins are never specified in the style hierarchy, then each margin shall use its default margin size (see child element definitions).

[Example: Consider a table defined to have default cells margins of 0.1 inches for all sides, as follows:

R1C1

R1C2

R2C1

R2C2

This set of default table cell margins would be specified using the following WordprocessingML:

<w:tblPr> <w:tblCellMar> <w:top w:w="144" w:type="dxa"/> <w:left w:w="144" w:type="dxa"/> <w:bottom w:w="144" w:type="dxa"/> <w:right w:w="144" w:type="dxa"/> </w:tblCellMar> …</w:tblPr>

The tblCellMar element as a child of tblPr specifies the set of default cell margins for all cells in the current table, in this case, 144 twentieths of a point. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Child Elements

Subclause

bottom (Table Cell Bottom Margin Default)

§2.4.5

left (Table Cell Left Margin Default)

§2.4.26

right (Table Cell Right Margin Default)

§2.4.29

top (Table Cell Top Margin Default)

§2.4.72

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

</sequence>

</complexType>

tblCellMar (Table Cell Margin Exceptions)

This element specifies a set of cell margins for all cells in the parent table row via a set of table-level property exceptions. These settings may be overridden by the table cell margin definition specified by the tcMar element contained within the table cell's properties (§2.4.40).

If this element is omitted, then it shall inherit the table cell margins from the table-level cell margins (§2.4.39).

[Example: Consider a table whose final two rows are defined to have default cell margins of 0.1 inches for all sides via a table-level property exception, as follows:

This set of table cell margin exceptions is specified using the following WordprocessingML:

<w:tblPrEx> <w:tblCellMar> <w:top w:w="144" w:type="dxa"/> <w:left w:w="144" w:type="dxa"/> <w:bottom w:w="144" w:type="dxa"/> <w:right w:w="144" w:type="dxa"/> </w:tblCellMar> …</w:tblPrEx>

The tblCellMar element as a child of tblPrEx specifies the set of default cell margins for all cells in final two rows in current table, in this case, 144 twentieths of a point on all sides. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Child Elements

Subclause

bottom (Table Cell Bottom Margin Default)

§2.4.5

left (Table Cell Left Margin Default)

§2.4.26

right (Table Cell Right Margin Default)

§2.4.29

top (Table Cell Top Margin Default)

§2.4.72

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

</sequence>

</complexType>

tblCellSpacing (Table Cell Spacing Exception)

This element specifies a table cell spacing exception for all cells in the parent table row as part of a set of table-level property exceptions. If specified, this element specifies the minimum amount of space which shall be left between all cells in the parent row after including the width of the table borders in the calculation. This setting shall be superseded by the row cell spacing value (§2.4.42). It is important to note that table-level cell spacing shall be added outside of the text margins, which shall be aligned with the innermost starting edge of the text extents in a table cell.

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

[Example: Consider a table whose first cell has a six point wide table border, and a table cell spacing value of 0.01 inches. The resulting table would have 0.01 inches of space between each table cell regardless of the width of the cell border, as follows (notice that no border is covered by any other border):

R1C1

R1C2

R2C1

R2C2

end example]

If this element is omitted, then the row shall inherit the table cell spacing from the table-level cell spacing setting (§2.4.39), excepting the case of a row level override.

[Example: Consider a table whose final two rows are defined to have cell spacing of 0.1 inches for all sides via a table-level property exception, as follows:

This table cell spacing exception is specified using the following WordprocessingML:

<w:tblPrEx> <w:tblCellSpacing w:w="144" w:type="dxa"> …</w:tblPrEx>

The tblCellSpacing element as a child of tblPrEx specifies the default cell spacing between all cells in final two rows in the current table, in this case 144 twentieths of a point. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tblCellSpacing (Table Row Cell Spacing)

This element specifies the default table cell spacing (the spacing between adjacent cells and the edges of the table) for all cells in the parent row. If specified, this element specifies the minimum amount of space which shall be left between all cells in the table including the width of the table borders in the calculation. It is important to note that row-level cell spacing shall be added inside of the text margins, which shall be aligned with the innermost starting edge of the text extents in a cell without row-level indentation or cell spacing. Row-level cell spacing shall not increase the width of the overall table.

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

R1C1

R1C2

R2C1

R2C2

end example]

If this element is omitted, then the cells in this row shall inherit the cell spacing from the associated table level properties.

[Example: Consider a table where the second row has a cell spacing of 0.1 inches for all sides specified via the table row properties as follows:

This table row cell spacing is specified using the following WordprocessingML:

<w:trPr> <w:tblCellSpacing w:w="144" w:type="dxa"> …</w:trPr>

The tblCellSpacing element as a child of trPr specifies the default cell spacing between all cells in the current row, in this case 144 twentieths of a point. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tblCellSpacing (Table Cell Spacing Default)

This element specifies the default table cell spacing (the spacing between adjacent cells and the edges of the table) for all cells in the parent table. If specified, this element specifies the minimum amount of space which shall be left between all cells in the table including the width of the table borders in the calculation. This setting shall be superseded by a table-level exception (§2.4.41) or the row cell spacing value (§2.4.42) in that order. It is important to note that table-level cell spacing shall be added outside of the text margins, which shall be aligned with the innermost starting edge of the text extents in a table cell.

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

R1C1

R1C2

R2C1

R2C2

end example]

If this element is omitted, then the table shall inherit the table cell spacing from the associated table style. If table cell spacing is never specified in the style hierarchy, no cell spacing shall be added to the parent table.

[Example: Consider a table with a default cell spacing of 0.1 inches for all sides as follows:

R1C1

R1C2

R2C1

R2C2

This table cell spacing deafult is specified using the following WordprocessingML:

<w:tblPr> <w:tblCellSpacing w:w="144" w:type="dxa"> …</w:tblPr>

The tblCellSpacing element as a child of tblPr specifies the default cell spacing between all cells in the current table, in this case 144 twentieths of a point. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tblGrid (Table Grid)

This element specifies the table grid for the current table. The table grid is a definition of the set of grid columns which define all of the shared vertical edges of the table, as well as default widths for each of these grid columns. These grid column widths are then used to determine the size of the table based on the table layout algorithm used (§2.4.49;§2.4.50).

If the table grid is omitted, then a new grid shall be constructed from the actual contents of the table assuming that all grid columns have a width of 0.

[Example: Consider the following table with four vertical edges (grid columns):

This table would have a table grid consisting of four grid columns as follows:

<w:tblGrid> <w:gridCol w:w="2088"/> <w:gridCol w:w="1104"/> <w:gridCol w:w="3192"/> <w:gridCol w:w="3192"/></w:tblGrid>

The tblGrid element contains the current definition for the table grid, consisting of all for grid columns as well as default widths for those columns. end example]

Parent Elements

tbl (§2.4.36)

Child Elements

Subclause

gridCol (Grid Column Definition)

§2.4.12

tblGridChange (Revision Information for Table Grid Column Definitions)

§2.13.5.35

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

</sequence>

</extension>

</complexContent>

</complexType>

tblGrid (Previous Table Grid)

This element specifies a previous table grid state, the modifications to which shall be attributed to a revision by a particular author and at a particular time. This element contains the table grid settings which were previously in place before a specific set of revisions by one author. The table grid is a definition of the set of grid columns which define all of the shared vertical edges of the table, as well as default widths for each of these grid columns. These grid column widths are then used to determine the size of the table based on the table layout algorithm used (§2.4.49;§2.4.50).

[Example: Consider the following table with four vertical edges (grid columns):

If we now modify this table by reducing the size of the last column without changing the overall table width, as follows:

This table would have a table grid consisting of four grid columns as follows:

<w:tblGrid> <w:gridCol w:w="2088"/> <w:gridCol w:w="1104"/> <w:gridCol w:w="3583"/> <w:gridCol w:w="2801"/> <w:tblGridChange w:id="1"> <w:tblGrid> <w:gridCol w:w="2088"/> <w:gridCol w:w="1104"/> <w:gridCol w:w="3192"/> <w:gridCol w:w="3192"/> </w:tblGrid> </w:tblGridChange></w:tblGrid>

The tblGrid element as a child of tblGridChange contains the previous definition for the table grid, consisting of all for grid columns as well as the original widths for those columns. end example]

Parent Elements

tblGridChange (§2.13.5.35)

Child Elements

Subclause

gridCol (Grid Column Definition)

§2.4.12

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

</sequence>

</complexType>

tblHeader (Repeat Table Row on Every New Page)

This element specifies that the current table row shall be repeated at the top of each new page on which part of this table is displayed. This gives this table row the behavior of a 'header' row on each of these pages.

If this element is omitted, then the table shall inherit the table cell spacing from the associated table style. If table cell spacing is never specified in the style hierarchy, then this table row shall not be repeated on each new page on which the table is displayed. As well, if this row is not contiguously connected with the first row of the table (that is, if this table row is not either the first row, or all rows between this row and the first row are not marked as header rows) then this property shall be ignored.

[Example: Consider a table which shall have its first row repeated on each new page, like the attribute listings in this Office Open XML Standard, for example:

Notice that the first row in the table is repeated on the top of the second page. This requirement would be specified as follows in the WordprocessingML for that row:

<w:trPr>

<w:tblHeader />

</w:trPr>

The tblHeader element specifies that this table row will now be repeated as a header row at the top of each page. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

tblInd (Table Indent from Leading Margin Exception)

This element specifies the indentation which shall be added before the leading edge of the set of parent table rows which have this set of table-level property exceptions applied. This indentation should shift the table into the text margin by the specified amount in the document (the left edge in a left-to-right table, and the right edge in a right-to-left table).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If this element is omitted, then the table shall inherit the table indentation from the associated table level property setting. If the resulting justification on the parent table row is not left after applying the value of the jc element from the three levels of this property (§2.4.21;§2.4.22;§2.4.23), then this property shall be ignored.

[Example: Consider a table in which the last two rows shall be indented one inch from the left margin via a table-level property exception definition, as follows:

This setting would be specified using the following WordprocessingML:

<w:tblPrEx> <w:tblInd w:val="1440" w:type="dxa"/></w:tblPrEx>

The tblInd element as a child of tblPrEx specifies that the rows with the table-level property exception shall be indented by 1440 twentieths of a point (one inch). end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tblInd (Table Indent from Leading Margin)

This element specifies the indentation which shall be added before the leading edge of the current table in the document (the left edge in a left-to-right table, and the right edge in a right-to-left table). This indentation should shift the table into the text margin by the specified amount.

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If this element is omitted, then the table shall inherit the table indentation from the associated table style. If table indentation is never specified in the style hierarchy, no indentation shall be added to the parent table. If the resulting justification on any table row is not left after applying the value of the jc element from the three levels of this property (§2.4.21;§2.4.22;§2.4.23), then this property shall be ignored.

[Example: Consider a table which shall be indented one inch from the left margin, as follows:

R1C1

R1C2

R2C1

R2C2

This setting would be specified using the following WordprocessingML:

<w:tblPr> <w:jc w:val="left"/> <w:tblInd w:val="1440" w:type="dxa"/></w:tblPr>

If the properties on this table were now modified to justify it on the right side by setting the value of the jc element to right, as follows:

<w:tblPr> <w:jc w:val="right"/> <w:tblInd w:val="1440" w:type="dxa"/></w:tblPr>

This table would now have no indent, as the justification is no longer on the leading edge (left):

R1C1

R1C2

R2C1

R2C2

end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tblLayout (Table Layout)

This element specifies the algorithm which shall be used to lay out the contents of this table within the document. When a table is displayed in a document, it can either be displayed using a fixed width or autofit layout algorithm (each discussed in the simple type referenced by the val attribute).

If this element is omitted, then the value of this element shall be assumed to be auto.

[Example: Consider a table which shall use the fixed width table layout algorithm. This requirement is specified using the following WordprocessingML:

<w:tblPr> <w:tblLayout w:type="fixed"/></w:tblPr>

The tblLayout element specifies that the table shall use the fixed layout algorithm. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

type (Table Layout Setting)

Specifies the algorithm which shall be used to lay out the contents of the parent table (see simple type definition for details on each algorithm used).

[Example: Consider a table which shall use the AutoFit width table layout algorithm. This requirement is specified using the following WordprocessingML:

<w:tblPr> <w:tblLayout w:type="auto"/></w:tblPr>

The tblLayout element specifies that the table shall use the auto layout algorithm. end example]

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

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

</complexType>

tblLayout (Table Layout Exception)

This element specifies the algorithm which shall be used to lay out the contents of all rows with this table within the table which have the set of table-level property exceptions specified by the parent element. When a table is displayed in a document, it can either be displayed using a fixed width or autofit layout algorithm (each discussed in the simple type referenced by the val attribute).

If this element is omitted, then the value of this element shall be assumed to be auto.

[Example: Consider a table which shall use the fixed width table layout algorithm. This requirement is specified using the following WordprocessingML:

<w:tblPrEx> <w:tblLayout w:type="fixed"/></w:tblPrEx>

The tblLayout element specifies that the table shall use the fixed layout algorithm. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

type (Table Layout Setting)

Specifies the algorithm which shall be used to lay out the contents of the parent table (see simple type definition for details on each algorithm used).

[Example: Consider a table which shall use the AutoFit width table layout algorithm. This requirement is specified using the following WordprocessingML:

<w:tblPr> <w:tblLayout w:type="auto"/></w:tblPr>

The tblLayout element specifies that the table shall use the auto layout algorithm. end example]

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

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

</complexType>

tblLook (Table Style Conditional Formatting Settings)

This element specifies the components of the conditional formatting of the referenced table style (if one exists) which shall be applied to the current table. A table style can specify up to six different optional conditional formats [Example: Different formatting for first column. end example], which then can be applied or omitted from individual tables in the document.

This element's value is hexadecimal code containing a bitmask of options, interpreted as follows:

0x0020=Apply first row conditional formatting

0x0040=Apply last row conditional formatting

0x0080=Apply first column conditional formatting

0x0100=Apply last column conditional formatting

0x0200=Do not apply row banding conditional formatting

0x0400=Do not apply column banding conditional formatting

If omitted, the bitmask of table style options on the current table shall be assumed to be 0000.

[Example: Consider a table which shall use the following conditional formatting properties from the referenced table style:

First row conditional formatting

Last row conditional formatting

This table would then apply the following portions of the bitmask:

0x0020=Apply first row conditional formatting

0x0040=Apply last row conditional formatting

0x0200=Do not apply row banding conditional formatting

0x0400=Do not apply column banding conditional formatting

The resulting WordprocessingML would be specified as follows:

<w:tblPr> <w:tblLook w:val="0660"/></w:tblPr>

The tblLook element specifies a bitmask which determines the components of the table style applied to the current table. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (Two Digit Hexadecimal Value)

Specifies a value specified as a two digit hexadecimal number), whose contents are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:tblPr>

<w:tblLook w:val="0010" />

</w:tblPr>

The value of 0010 is interpreted in the context of the parent element. end example]

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

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

</complexType>

tblLook (Table Style Conditional Formatting Settings Exception)

This element specifies the components of the conditional formatting of the referenced table style (if one exists) which shall be applied to the set of table rows with the current table-level property exceptions. A table style can specify up to six different optional conditional formats [Example: Different formatting for first column. end example], which then can be applied or omitted from individual table rows in the parent table.

This element's value is hexadecimal code containing a bitmask of options, interpreted as follows:

0x0020=Apply first row conditional formatting

0x0040=Apply last row conditional formatting

0x0080=Apply first column conditional formatting

0x0100=Apply last column conditional formatting

0x0200=Do not apply row banding conditional formatting

0x0400=Do not apply column banding conditional formatting

If omitted, the bitmask of table style options on the current table row shall be assumed to be the value specified on the table-level properties.

[Example: Consider a table which shall use the following conditional formatting properties from the referenced table style:

First row conditional formatting

Last row conditional formatting

This table would then apply the following portions of the bitmask:

0x0020=Apply first row conditional formatting

0x0040=Apply last row conditional formatting

0x0200=Do not apply row banding conditional formatting

0x0400=Do not apply column banding conditional formatting

The resulting WordprocessingML would be specified as follows:

<w:tblPrEx> <w:tblLook w:val="0660"/></w:tblPrEx>

The tblLook element specifies a bitmask which determines the components of the table style applied to the current table. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

val (Two Digit Hexadecimal Value)

Specifies a value specified as a two digit hexadecimal number), whose contents are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:tblPr>

<w:tblLook w:val="0010" />

</w:tblPr>

The value of 0010 is interpreted in the context of the parent element. end example]

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

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

</complexType>

tblOverlap (Floating Table Allows Other Tables to Overlap)

This element specifies whether the current table shall allow other floating tables to overlap its extents when the tables are displayed in a document. If specified, then no adjustment shall be made to prevent tables whose properties would normally cause them to overlap from overlapping when displayed. If turned off, then the tables shall be adjusted as needed to prevent them from overlapping when displayed by adjusting the floating table properties as needed.

If this element is omitted on a given table, then this table shall allow other tables to overlap when displayed. If the parent table is not floating via the tblpPr element (§2.4.54), then this element shall be ignored.

[Example: Consider two floating tables in a WordprocessingML document which overlap when displayed, as follows:

If either of these tables specifies that it shall not allow overlapping, using the following WordprocessingML:

<w:tblPr> <w:tblOverlap w:val="never"/></w:tblPr>

The resulting tables shall not overlap, and must be adjusted at display time to prevent any overlapping, for example:

The tblOverlap element with a value of never specifies that the specified table cannot overlap with other floating tables in the document. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (Floating Table Overlap Setting)

Specifies whether a floating table shall allow other floating tables in the document to overlap its extents when displayed.

[Example: The following WordprocessingML specifies that the table is not allowed to overlap:

<w:tblOverlap w:val="never" />

end example]

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

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

</complexType>

tblpPr (Floating Table Positioning)

This element specifies information about the current table with regard to floating tables. Floating tables are tables in a document which are not part of the main text flow in the document, and are instead absolutely positioned with a specific size and position relative to non-frame content in the current document.

The first piece of information specified by the tblpPr element is that the current table is actually a floating table. This information is specified simply by the presence of the tblpPr element in table's properties. If the tblpPr element is omitted, the table shall not floating in the document.

The second piece of information is the positioning of the table, which is specified by the attribute values stored on the tblpPr element. In all absolute positioning cases, the positioning of the table is relative to its top-left corner position. For relative positioning (e.g. center), the positioning of the table is relative to its entire frame.

Note that the table still has a logical position in the file (its location within the block-level elements in the document). This logical location shall be used to calculate the position of the table relative to a paragraph, using the next regular (non-table, non-frame) paragraph in the document.

[Example: Consider a floating table which is positioned three inches from the edge of the page extents on both its top and left edges (i.e. the top-left corner occurs at 3" x 3"). This floating table would be specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblpPr w:leftFromText="144" w:rightFromText="144" w:topFromText="144" w:bottomFromText="144" w:vertAnchor="page" w:horzAnchor="page" w:tblpX="4320" w:tblpY="4320"/> … </w:tblPr> …</w:tbl>

The presence of the tblpPr element dictates that this table is a floating table, and its attributes specify that the floating table shall be anchored 4320 twentieths of a point (3 inches) from the top and left edges of the current page. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

bottomFromText (Distance From Bottom of Table to Text)

Specifies the minimum distance which shall be maintained between the current floating table and the top of text in the paragraph which is below this floating table.

This distance is expressed in twentieths of a point.

If this attribute is omitted, its value shall be assumed to be 0.

[Example: Consider a floating table which should have a minimum of a one-half inch spacing from any text on its bottom side. This constraint would be specified using the following WordprocessingML:

<w:tblPr>

<w:tblpPr … w:bottomFromText="720" />

</w:tblPr>

The bottomFromText attribute specifies that the spacing between text and this floating table shall be a minimum of 720 twentieths of a point. end example]

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

horzAnchor (Table Horizontal Anchor)

Specifies the base object from which the horizontal positioning in the tblpX and/or tblpXSpec attribute should be calculated.

A floating table may be horizontally positioned relative to:

The vertical edge of the page before any runs of text (the left edge for left-to-right paragraphs, the right edge for right-to-left paragraphs)

The vertical edge of the text margin before any runs of text (the left edge for left-to-right paragraphs, the right edge for right-to-left paragraphs)

The vertical edge of the text margin for the column in which the anchor paragraph is located

If this attribute is omitted, then its value shall be assumed to be page.

[Example: Consider a floating table which should be positioned one inch to the right of its column in a left-to-right document. This floating table would be specified using the following WordprocessingML:

<w:tblPr>

<w:tblpPr … w:tblpX="1440" w:horzAnchor="column" />

</w:tblPr>

These table properties specify that they are relative to the current column, and that relative to that column, the floating table should be 1440 twentieths of a point. end example]

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

leftFromText (Distance From Left of Table to Text)

Specifies the minimum distance which shall be maintained between the current floating table and the edge of text in the paragraph which is to the left of this floating table.

This distance is expressed in twentieths of a point.

If this attribute is omitted, its value shall be assumed to be 0.

[Example: Consider a floating table which should have a minimum of a one-half inch spacing from any text on its left. This constraint would be specified using the following WordprocessingML:

<w:tblPr>

<w:tblpPr … w:leftFromText="720" />

</w:tblPr>

The leftFromText attribute specifies that the spacing between text and this floating table shall be a minimum of 720 twentieths of a point. end example]

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

rightFromText ((Distance From Right of Table to Text)

Specifies the minimum distance which shall be maintained between the current floating table and the edge of text in the paragraph which is to the right of this floating table.

This distance is expressed in twentieths of a point.

If this attribute is omitted, its value shall be assumed to be 0.

[Example: Consider a floating table which should have a minimum of a one-half inch spacing from any text on its right. This constraint would be specified using the following WordprocessingML:

<w:tblPr>

<w:tblpPr … w:rightFromText="720" />

</w:tblPr>

The rightFromText attribute specifies that the spacing between text and this floating table shall be a minimum of 720 twentieths of a point. end example]

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

tblpX (Absolute Horizontal Distance From Anchor)

Specifies an absolute horizontal position for the floating table. This absolute position is specified relative to the horizontal anchor specified by the horzAnchor attribute for this floating table.

This value is expressed in twentieths of a point. If it is positive, then the floating table is positioned after the anchor object in the direction of horizontal text flow in this document. If it is negative, then the floating table is positioned before the anchor object in the direction of horizontal text flow in this document.

If the tblpXSpec attribute is also specified, then this value is ignored. If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider the following WordprocessingML fragment specifying a floating table:

<w:tbl>

<w:tblPr>

<w:tblpPr … w:horizAnchor="page" w:tblpX="1643"/>

</w:tblPr>

…

</w:tbl>

This floating table specifies that it should be located exactly 1643 twentieths of a point after the vertical edge of the page (from the horizAnchor attribute). end example]

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

tblpXSpec (Relative Horizontal Alignment From Anchor)

Specifies a relative horizontal position for the floating table. This relative position is specified relative to the horizontal anchor specified by the horizAnchor attribute for this floating table.

If omitted, this attribute is not specified and the value of the tblpX attribute determines the absolute horizontal position of the floating table. If specified, the position for this attribute supersedes any value which is specified in the tblpX attribute, and that value is ignored.

[Example: Consider the following WordprocessingML fragment specifying a floating table:

<w:tbl>

<w:tblPr>

<w:tblpPr … w:horizAnchor="page" w:tblpX="1643" w:tblpXSpec="left"/>

</w:tblPr>

…

</w:tbl>

This floating table specifies that it has a horizontal placement of exactly 1643 twentieths of a point relative to the page, but that exact placement is overridden by the presence of the tblpXSpec attribute to place the table on the left side of the page. end example]

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

tblpY (Absolute Vertical Distance From Anchor)

Specifies an absolute vertical position for the floating table. This absolute position is specified relative to the vertical anchor specified by the vertAnchor attribute for this floating table.

This value is expressed in twentieths of a point. If it is positive, then the floating table is positioned after the anchor object in the direction of vertical text flow in this document. If it is negative, then the floating table is positioned before the anchor object in the direction of vertical text flow in this document.

If the tblpYSpec attribute is also specified, then this value is ignored. If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider the following WordprocessingML fragment specifying a floating table:

<w:tbl>

<w:tblPr>

<w:tblpPr … w:vertAnchor="text" w:tblpY="73" />

</w:tblPr>

…

</w:tbl>

This floating table specifies that it should be located exactly 79 twentieths of a point below the top vertical edge of the anchor's paragraph's text (from the vertAnchor attribute), assuming that the vertical text direction is top to bottom. end example]

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

tblpYSpec (Relative Vertical Alignment from Anchor)

Specifies a relative vertical position for the floating table. This relative position is specified relative to the vertical anchor specified by the vertAnchor attribute for this floating table.

If omitted, this attribute is not specified and the value of the tblpY attribute determines the absolute horizontal position of the floating table. If specified, the position for this attribute supersedes any value which is specified in the tblpY attribute, and that value is ignored, unless the vertAnchor is set to text, in which case any relative positioning is not allowed, and is itself ignored.

[Example: Consider the following WordprocessingML fragment specifying a floating table:

<w:tbl>

<w:tblPr>

<w:tblpPr … w:vertAnchor="margin" w:tblpY="73" w:tblpYSpec="center"/>

</w:tblPr>

…

</w:tbl>

This floating table specifies that it has a vertical placement of exactly 73 twentieths of a point relative to the top margin, but that exact placement is overridden by the presence of the tblpYSpec attribute to place the table in the center of the margin. end example]

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

topFromText (Distance From Top of Table to Text)

Specifies the minimum distance which shall be maintained between the current floating table and the bottom edge of text in the paragraph which is above this floating table.

This distance is expressed in twentieths of a point.

If this attribute is omitted, its value shall be assumed to be 0.

[Example: Consider a floating table which should have a minimum of a one-half inch spacing from any text above it. This constraint would be specified using the following WordprocessingML:

<w:tblPr>

<w:tblpPr … w:topFromText="720" />

</w:tblPr>

The topFromText attribute specifies that the spacing between text and this floating table shall be a minimum of 720 twentieths of a point. end example]

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

vertAnchor (Table Vertical Anchor)

Specifies the base object from which the vertical positioning in the tblpY attribute should be calculated.

A floating table may be horizontally positioned relative to:

The horizontal edge of the page before any runs of text (the top edge for top-to-bottom sections, the bottom for bottom-to-top sections)

The horizontal edge of the text margin before any runs of text (the top edge for top-to-bottom sections, the bottom for bottom-to-top sections)

The horizontal edge of the page before any runs of text (the top edge for top-to-bottom sections, the bottom for bottom-to-top sections)

If this attribute is omitted, then its value shall be assumed to be page.

[Example: Consider a floating table which should be positioned two inches below the page top in a top-to-bottom document. This floating table would be specified using the following WordprocessingML:

<w:tblPr>

<w:tblpPr … w:tblpY="2880" w:vertAnchor="page" />

</w:tblPr>

These floating table properties specify that they are relative to the anchor page, and that relative to that page, the table should be 2880 twentieths of a point in the direction of the flow of text (down, in this case). end example]

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

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

</complexType>

tblPr (Table Properties)

This element specifies the set of table-wide properties applied to the current table. These properties affect the appearance of all rows and cells within the parent table, but may be overridden by individual table-level exception, row, and cell level properties as defined by each property.

[Example: Consider the following simple WordprocessingML table:

This table defines a one point single border for all border types and is set to 100% of page width - both table-wide properties. The resulting table is represented by the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblW w:w="0" w:type="auto"/> <w:tblBorders> <w:top w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:left w:val="single" w:sz="4 w:space="0" w:color="auto"/> <w:bottom w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:right w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:insideH w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:insideV w:val="single" w:sz="4" w:space="0" w:color="auto"/> </w:tblBorders> </w:tblPr> …</w:tbl>

In this example, the tblW element (§2.4.61) defines the total width of the table, which, in this case, is set to a type of auto, which specifies that the table should be automatically sized to fit its contents. The tblBorders element (§2.4.38) specifies each of the table's borders, and specifies a one point border on the top, left, bottom, right and inside horizontal and vertical border. end example]

Parent Elements

tbl (§2.4.36)

Child Elements

Subclause

bidiVisual (Visually Right to Left Table)

§2.4.1

jc (Table Alignment)

§2.4.23

shd (Table Shading)

§2.4.35

tblBorders (Table Borders)

§2.4.38

tblCellMar (Table Cell Margin Defaults)

§2.4.39

tblCellSpacing (Table Cell Spacing Default)

§2.4.43

tblInd (Table Indent from Leading Margin)

§2.4.48

tblLayout (Table Layout)

§2.4.49

tblLook (Table Style Conditional Formatting Settings)

§2.4.51

tblOverlap (Floating Table Allows Other Tables to Overlap)

§2.4.53

tblpPr (Floating Table Positioning)

§2.4.54

tblPrChange (Revision Information for Table Properties)

§2.13.5.36

tblStyle (Referenced Table Style)

§2.4.59

tblStyleColBandSize (Number of Columns in Column Band)

§2.7.5.5

tblStyleRowBandSize (Number of Rows in Row Band)

§2.7.5.7

tblW (Preferred Table Width)

§2.4.61

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

</sequence>

</extension>

</complexContent>

</complexType>

tblPr (Previous Table Properties)

This element specifies a previous set of table properties, the modifications to which shall be attributed to a revision by a particular author and at a particular time. This element contains the table property settings which were previously in place before a specific set of revisions by one author. These properties affect the appearance of all rows and cells within the parent table, but may be overridden by individual table-level exception, row, and cell level properties, as defined by each property.

[Example: Consider the following simple WordprocessingML table:

If the table justification is set to center and the table shading to set to red with revision marking on, as follows:

The revision tracked on this table would be specified as follows in the WordprocessingML:

<w:tblPr> <w:tblStyle w:val="TableGrid"/> <w:tblW w:w="0" w:type="auto"/> <w:jc w:val="center"/> <w:shd w:val="clear" w:color="auto" w:fill="FF0000"/> <w:tblLook w:val="04A0"/> <w:tblPrChange w:id="0" … >

<w:tblPr> <w:tblStyle w:val="TableGrid"/> <w:tblW w:w="0" w:type="auto"/> <w:tblLook w:val="04A0"/> </w:tblPr> </w:tblPrChange></w:tblPr>

The tblPr element as a child of tblPrChange contains the previous definition for the table properties, consisting of the properties set before the current tracked revision. end example]

Parent Elements

tblPrChange (§2.13.5.36)

Child Elements

Subclause

bidiVisual (Visually Right to Left Table)

§2.4.1

jc (Table Alignment)

§2.4.23

shd (Table Shading)

§2.4.35

tblBorders (Table Borders)

§2.4.38

tblCellMar (Table Cell Margin Defaults)

§2.4.39

tblCellSpacing (Table Cell Spacing Default)

§2.4.43

tblInd (Table Indent from Leading Margin)

§2.4.48

tblLayout (Table Layout)

§2.4.49

tblLook (Table Style Conditional Formatting Settings)

§2.4.51

tblOverlap (Floating Table Allows Other Tables to Overlap)

§2.4.53

tblpPr (Floating Table Positioning)

§2.4.54

tblStyle (Referenced Table Style)

§2.4.59

tblStyleColBandSize (Number of Columns in Column Band)

§2.7.5.5

tblStyleRowBandSize (Number of Rows in Row Band)

§2.7.5.7

tblW (Preferred Table Width)

§2.4.61

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

</sequence>

</complexType>

tblPrEx (Table-Level Property Exceptions)

This element specifies a set of table properties which shall be applied to the contents of this row in place of the table properties specified in the tblPr element.

[Note: These properties are typically used in cases involving legacy documents, as well as cases where two existing independent tables are merged (in order to prevent the look of the second table from being superseded by the first table). end note]

[Example: Consider the following two tables in a WordprocessingML document:

These two tables each have a different set of table level borders. If the interceding paragraphs between these two tables is removed and the tables are merged together, it is obviously undesirable to have the second table lose its formatting and match the properties of the first table. Therefore, when the tables are merged as follows (note that there is now only one table):

The resulting WordprocessingML for the last three rows of the table would include the following set of table-level property exceptions:

The tblPrEx element contains all table-level properties which are being overridden for the current row in the table. end example]

Parent Elements

tr (§2.4.75)

Child Elements

Subclause

jc (Table Alignment Exception)

§2.4.21

shd (Table Shading Exception)

§2.4.34

tblBorders (Table Borders Exceptions)

§2.4.37

tblCellMar (Table Cell Margin Exceptions)

§2.4.40

tblCellSpacing (Table Cell Spacing Exception)

§2.4.41

tblInd (Table Indent from Leading Margin Exception)

§2.4.47

tblLayout (Table Layout Exception)

§2.4.50

tblLook (Table Style Conditional Formatting Settings Exception)

§2.4.52

tblPrExChange (Revision Information for Table-Level Property Exceptions)

§2.13.5.37

tblW (Preferred Table Width Exception)

§2.4.60

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

</sequence>

</extension>

</complexContent>

</complexType>

tblPrEx (Previous Table-Level Property Exceptions)

This element specifies a previous set of table-level property exceptions, the modifications to which shall be attributed to a revision by a particular author and at a particular time. This element contains the table-level property exceptions which were previously in place before a specific set of revisions by one author.

[Example: Consider the following two tables in a WordprocessingML document. If the interceding paragraphs between these two tables is removed and the tables are merged together, it is obviously undesirable to have the second table lose its formatting and match the properties of the first table. Therefore, when the tables are merged as follows (note that there is now only one table):

If the border type is changed to a red border of type thinThickThinSmallGap with revisions tracked, as follows:

The resulting WordprocessingML for the last three rows of the table would include the following set of table-level property exceptions with revision tracking:

<w:tr> <w:tblPrEx> <w:tblBorders> <w:top w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="auto"/> <w:left w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="auto"/> <w:bottom w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="auto"/> <w:right w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="auto"/> <w:insideH w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="auto"/> <w:insideV w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="auto"/> </w:tblBorders> <w:tblPrExChange w:id="9" … > <w:tblPrEx> <w:tblBorders> <w:top w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> <w:left w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> <w:bottom w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> <w:right w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> <w:insideH w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> <w:insideV w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> </w:tblBorders> </w:tblPrEx> </w:tblPrExChange> </w:tblPrEx> …</w:tr>

The tblPrEx element as a child of tblPrExChange contains the previous definition for the table-level property exceptions, consisting of the properties set before the current tracked revision. end example]

Parent Elements

tblPrExChange (§2.13.5.37)

Child Elements

Subclause

jc (Table Alignment Exception)

§2.4.21

shd (Table Shading Exception)

§2.4.34

tblBorders (Table Borders Exceptions)

§2.4.37

tblCellMar (Table Cell Margin Exceptions)

§2.4.40

tblCellSpacing (Table Cell Spacing Exception)

§2.4.41

tblInd (Table Indent from Leading Margin Exception)

§2.4.47

tblLayout (Table Layout Exception)

§2.4.50

tblLook (Table Style Conditional Formatting Settings Exception)

§2.4.52

tblW (Preferred Table Width Exception)

§2.4.60

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

</sequence>

</complexType>

tblStyle (Referenced Table Style)

This element specifies the style ID of the table style which shall be used to format the contents of this table.

This formatting is applied at the following location in the style hierarchy:

Document defaults

Table styles (this element)

Numbering styles

Paragraph styles

Character styles

Direct Formatting

This means that all properties specified in the style element (§2.7.3.17) with a styleId which corresponds to the value in this element's val attribute are applied to the table at the appropriate level in the hierarchy.

If this element is omitted, or it references a style which does not exist, then no table style shall be applied to the current table. As well, this property is ignored if the table properties are themselves part of a table style.

[Example: Consider the following WordprocessingML fragment:

<w:tblPr>

<w:tblStyle w:val=”TestTableStyle” />

</w:tblPr>

This table specifies that it will inherit all of the table properties specified by the table style with a styleId of TestTableStyle. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

tblW (Preferred Table Width Exception)

This element specifies the preferred width for the parent table row via a set of table-level property exceptions. This preferred width is used as part of the table layout algorithm specified by the tblLayout element (§2.4.49n; §2.4.50) - full description of the algorithm in the ST_TblLayout simple type (§2.18.94).

All widths in a table are considered preferred because:

The table must satisfy the shared columns as specified by the tblGrid element (§2.4.44)

Two or more widths may have conflicting values for the width of the same grid column

The table layout algorithm (§2.18.94) may require a preference to be overridden

This value is specified in the units applied via its type attribute. Any width value of type pct for this element shall be calculated relative to the text extents of the page (page width excluding margins).

If this element is omitted, then the cell width shall be of type auto.

[Example: Consider a row in a WordprocessingML table defined as follows:

<w:tr> <w:trPr> <w:tblPrEx> <w:tblW w:type="fixed" w:w="1440"/> </w:tblPrEx> </w:trPr> …</w:tr>

This table-level property exception specifies that it has a preferred table width of 1440 twentieths of a point (one inch). The resulting table row would therefore be sized such that the table maintains that preferred width, as follows:

Hello world

The text Hello world makes the middle cell larger, and the other two cells are size to maintain the preferred widths of one inch for the overall table width:

Hello world this is a longer string.

However, when the middle table cell requires a larger width to accommodate non-breaking text, that preference may be overridden as needed:

Hello worldddddddddddddddddddddddddddddd

In this case, the middle cell's long non breaking string caused the table to be expanded to prevent breaking the string, and therefore to override the preferred width on the table row. end example]

Parent Elements

tblPrEx (§2.4.57); tblPrEx (§2.4.58)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tblW (Preferred Table Width)

This element specifies the preferred width for this table. This preferred width is used as part of the table layout algorithm specified by the tblLayout element (§2.4.49; §2.4.50) - full description of the algorithm in the ST_TblLayout simple type (§2.18.94).

All widths in a table are considered preferred because:

The table must satisfy the shared columns as specified by the tblGrid element (§2.4.44)

Two or more widths may have conflicting values for the width of the same grid column

The table layout algorithm (§2.18.94) may require a preference to be overridden

If this element is omitted, then the cell width shall be of type auto.

[Example: Consider a WordprocessingML table defined as follows:

<w:tbl> <w:tblPr> <w:tblW w:type="fixed" w:w="1440"/> </w:tblPr> …</w:tbl>

This table specifies that it has a preferred table width of 1440 twentieths of a point (one inch). The resulting table would therefore be sized such that the table maintains that preferred width, as follows:

Hello world

The text Hello world makes the middle cell larger, and the other two cells are size to maintain the preferred widths of one inch for the overall table width:

Hello world this is a longer string.

However, when the middle table cell requires a larger width to accommodate non-breaking text, that preference may be overridden as needed:

Hello worldddddddddddddddddddddddddddddd

In this case, the middle cell's long non breaking string caused the table to be expanded to prevent breaking the string, and therefore to override the preferred width on the table. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

tc (Table Cell)

This element specifies a single cell in a table row, which contains the table’s content. Table cells in WordprocessingML are analogous to HTML td elements.

A tc element has one formatting child element, tcPr (§2.4.67), which defines the properties for the cell. Each unique property on the table cell is specified by a child element of this element. As well, a table cell can contain any valid block-level content, which allows for the nesting of paragraphs and tables within table cells.

If a table cell does not include at least one block-level element, then this document shall be considered corrupt.

[Example: Consider a table consisting of a single table cell, which contains the text Hello World:

Hello World

This table cell's content is represented by the following WordprocessingML:

<w:tc> <w:tcPr> <w:tcW w:w="0" w:type="auto"/> </w:tcPr> <w:p> <w:r> <w:t>Hello, World</w:t> </w:r> </w:p></w:tc>

The tc element contains a set of cell-level properties defined using the tcPr element, and a single block-level element - in this case, a paragraph. end example]

Parent Elements

customXml (§2.5.1.3); sdtContent (§2.5.2.33); tr (§2.4.75)

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

tcPr (Table Cell Properties)

§2.4.67

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

</sequence>

</complexType>

tcBorders (Table Cell Borders)

This element specifies the set of borders for the edges of the current table cell, using the eight border types defined by its child elements.

If the cell spacing for any row is non-zero as specified using the tblCellSpacing element (§2.4.41; §2.4.42; §2.4.43), then there is never a border conflict (as the non-zero cell spacing is applied above and beyond each individual cell border's width) and all table, table-level exception, and table cell borders shall be displayed.

If the cell spacing is zero, then there may be a conflict between two adjacent cell borders [Example: Between the left border of all cells in the second column and the right border of all cells in the first column of the table. end example], which shall be resolved as follows:

If either conflicting table cell border is nil or none (no border), then the opposing border shall be displayed.

If a cell border conflicts with a table border, the cell border always wins.

Each border shall then be assigned a weight using the following formula, and the border value using this calculation shall be displayed over the alternative border:

The border number shall be determined by this list:

single

thick

double

dotted

dashed

dotDash

dotDotDash

triple

thinThickSmallGap

thickThinSmallGap

thinThickThinSmallGap

thinThickMediumGap

thickThinMediumGap

thinThickThinMediumGap

thinThickLargeGap

thickThinLargeGap

thinThickThinLargeGap

wave

doubleWave

dashSmallGap

dashDotStroked

threeDEmboss

threeDEngrave

outset

inset

If the borders have an equal weight, than the higher of the two on this precedence list shall win:

single

thick

double

dotted

dashed

dotDash

dotDotDash

triple

thinThickSmallGap

thickThinSmallGap

thinThickThinSmallGap

thinThickMediumGap

thickThinMediumGap

thinThickThinMediumGap

thinThickLargeGap

thickThinLargeGap

thinThickThinLargeGap

wave

doubleWave

dashSmallGap

dashDotStroked

threeDEmboss

threeDEngrave

outset

inset

If the borders have an identical style, than each border color shall be assigned a brightness value as follows:The color with the smaller brightness value shall win.

If the borders have an identical brightness value above, than each border color shall be assigned a new brightness value as follows:The color with the smaller brightness value shall win.

If the borders have an identical brightness value above, than each border color shall be assigned a brightness value as follows:The color with the smaller brightness value shall win.

If the borders have an identical brightness value above, then they are functionally identical, and the first border in reading order should be displayed.

[Example: Consider the following two cell table (with exaggerated table cell spacing for clarity):

If we collapse the cell spacing, there will be conflicting borders at all edges. For each cell/table border conflict, rule #2 says that the cell border shall win. For the conflict in the center between two cell borders, rule #3 gives us a larger border weight for the right cell's border, resulting in the following table:

end example]

[Example: Consider a table whose first cell specifies cell-level borders consisting of a think double red line, as follows:

These cell borders are specified using the following WordprocessingML:

<w:tcPr> <w:tcBorders> <w:top w:val="double" w:sz="24" w:space="0" w:color="FF0000"/> <w:left w:val="double" w:sz="24" w:space="0" w:color="FF0000"/> <w:bottom w:val="double" w:sz="24" w:space="0" w:color="FF0000"/> <w:right w:val="double" w:sz="24" w:space="0" w:color="FF0000"/> </w:tcBorders></w:tcPr>

The tcBorders element specifies the set of borders applied to the first cell as a 3 point double border. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Child Elements

Subclause

bottom (Table Cell Bottom Border)

§2.4.3

insideH (Table Cell Inside Horizontal Edges Border)

§2.4.18

insideV (Table Cell Inside Vertical Edges Border)

§2.4.19

left (Table Cell Left Border)

§2.4.24

right (Table Cell Right Border)

§2.4.30

tl2br (Table Cell Top Left to Bottom Right Diagonal Border)

§2.4.70

top (Table Cell Top Border)

§2.4.74

tr2bl (Table Cell Top Right to Bottom Left Diagonal Border)

§2.4.76

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

</sequence>

</complexType>

tcFitText (Fit Text Within Cell)

This element specifies that the contents of the current cell shall have their inter-character spacing increased or reduced as necessary to fit the width of the text extents of the current cell. This setting shall behave identically to placing the contents of this paragraph in a run and using the fitText element (§2.3.2.12), if the width provided on that element matched the width of the current cell.

If this element is omitted, then the text in this cell shall not be fit to the current cell extents.

[Example: Consider a 2 row by two column table, in which the contents of the two cells in the first row have both have the fit text property set, as follows:

<w:tcPr> <w:tcFitText w:val="true"/></w:tcPr>

The resulting table cells shall have their contents fit to the extents of the parent table cell, as follows:

Sample text in R1C1.

And this table cell instead contains a very very long string of sample text in R2C2.

R2C1

R2C2

end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

tcMar (Single Table Cell Margins)

This element specifies a set of cell margins for a single table cell in the parent table.

This setting, if present, shall override the table cell margins from the table-level cell margins (§2.4.39).

[Example: Consider a table whose first cell is defined to have default cell margins of 0.5 inches for all sides rather then the table defaults, as follows:

R1C1

R2C1

This set of table cell margins is specified using the following WordprocessingML:

<w:tcPr> <w:tcMar> <w:top w:w="720" w:type="dxa"/> <w:left w:w="720" w:type="dxa"/> <w:bottom w:w="720" w:type="dxa"/> <w:right w:w="720" w:type="dxa"/> </w:tcMar> …</w:tcPr>

The tcMar element as a child of tcPr specifies the set of table cell margins used for the first table cell, in this case, 720 twentieths of a point on all sides. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Child Elements

Subclause

bottom (Table Cell Bottom Margin Exception)

§2.4.2

left (Table Cell Left Margin Exception)

§2.4.25

right (Table Cell Right Margin Exception)

§2.4.31

top (Table Cell Top Margin Exception)

§2.4.73

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

</sequence>

</complexType>

tcPr (Previous Table Cell Properties)

This element specifies a previous set of table cell properties, the modifications to which shall be attributed to a revision by a particular author and at a particular time. This element contains the table cell property settings which were previously in place before a specific set of revisions by one author. Each unique property is specified by a child element of this element. In any instance where there is a conflict between the table level, table-level exception, or row level properties with a corresponding table cell property, these properties shall overwrite the table or row wide properties.

[Example: Consider a basic two row by two column table as follows:

If the cell shading in the first cell is set to red with revision tracking enabled, as follows:

This revision is specified as follows in the associated WordprocessingML:

<w:tc> <w:tcPr> <w:tcW w:w="4788" w:type="dxa"/> <w:shd w:val="clear" w:color="auto" w:fill="FF0000"/> <w:tcPrChange w:id="2" …> <w:tcPr> <w:tcW w:w="4788" w:type="dxa"/> </w:tcPr> </w:tcPrChange> </w:tcPr> <w:p/></w:tc>

The tcPr element beneath the tcPrChange element specifies the set of table cell properties which were in place before the current revision to the document. end example]

Parent Elements

tcPrChange (§2.13.5.38)

Child Elements

Subclause

cellDel (Table Cell Deletion)

§2.13.5.1

cellIns (Table Cell Insertion)

§2.13.5.2

cellMerge (Vertically Merged/Split Table Cells)

§2.13.5.3

cnfStyle (Table Cell Conditional Formatting)

§2.4.7

gridSpan (Grid Columns Spanned by Current Table Cell)

§2.4.13

hideMark (Ignore End Of Cell Marker In Row Height Calculation)

§2.4.15

hMerge (Horizontally Merged Cell)

§2.4.16

noWrap (Don't Wrap Cell Content)

§2.4.28

shd (Table Cell Shading)

§2.4.33

tcBorders (Table Cell Borders)

§2.4.63

tcFitText (Fit Text Within Cell)

§2.4.64

tcMar (Single Table Cell Margins)

§2.4.65

tcW (Preferred Table Cell Width)

§2.4.68

textDirection (Table Cell Text Flow Direction)

§2.4.69

vAlign (Table Cell Vertical Alignment)

§2.4.80

vMerge (Vertically Merged Cell)

§2.4.81

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

</sequence>

</extension>

</complexContent>

</complexType>

tcPr (Table Cell Properties)

This element specifies the set of properties which shall be applied a specific table cell. Each unique property is specified by a child element of this element. In any instance where there is a conflict between the table level, table-level exception, or row level properties with a corresponding table cell property, these properties shall overwrite the table or row wide properties.

[Example: Consider a table where the cell width overwrites the table width represented in the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblCellMar> <w:left w:w="0" w:type="dxa"/> </w:tblCellMar> </w:tblPr> <w:tr> <w:tc> <w:tcPr> <w:tcMar> <w:left w:w="720" w:type="dxa"/> </w:tcMar> </w:tcPr> … </w:tc> </w:tr></w:tbl>

This table cell will have a left cell margin of 720 twentieths of a point (one half inch) as specified in the tcMar element, which overwrites the table level setting of 0 left table cell margin. end example]

Parent Elements

tc (§2.4.62)

Child Elements

Subclause

cellDel (Table Cell Deletion)

§2.13.5.1

cellIns (Table Cell Insertion)

§2.13.5.2

cellMerge (Vertically Merged/Split Table Cells)

§2.13.5.3

cnfStyle (Table Cell Conditional Formatting)

§2.4.7

gridSpan (Grid Columns Spanned by Current Table Cell)

§2.4.13

hideMark (Ignore End Of Cell Marker In Row Height Calculation)

§2.4.15

hMerge (Horizontally Merged Cell)

§2.4.16

noWrap (Don't Wrap Cell Content)

§2.4.28

shd (Table Cell Shading)

§2.4.33

tcBorders (Table Cell Borders)

§2.4.63

tcFitText (Fit Text Within Cell)

§2.4.64

tcMar (Single Table Cell Margins)

§2.4.65

tcPrChange (Revision Information for Table Cell Properties)

§2.13.5.38

tcW (Preferred Table Cell Width)

§2.4.68

textDirection (Table Cell Text Flow Direction)

§2.4.69

vAlign (Table Cell Vertical Alignment)

§2.4.80

vMerge (Vertically Merged Cell)

§2.4.81

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

</sequence>

</extension>

</complexContent>

</complexType>

tcW (Preferred Table Cell Width)

This element specifies the preferred width for this table cell. This preferred width is used as part of the table layout algorithm specified by the tblLayout element (§2.4.49; §2.4.50) - full description of the algorithm in the ST_TblLayout simple type (§2.18.94).

All widths in a table are considered preferred because:

The table must satisfy the shared columns as specified by the tblGrid element (§2.4.44)

Two or more widths may have conflicting values for the width of the same grid column

The table layout algorithm (§2.18.94) may require a preference to be overridden

This value is specified in the units applied via its type attribute. Any width value of type pct for this element shall be calculated relative to the overall width of the table.

If this element is omitted, then the cell width shall be of type auto.

[Example: Consider a WordprocessingML table defined as follows:

<w:tbl> <w:tr> <w:tc> <w:tcPr> <w:tcW w:type="pct" w:w="1667"/> </w:tcPr> … </w:tc> <w:tc> <w:tcPr> <w:tcW w:type="pct" w:w="1667"/> </w:tcPr> … </w:tc> <w:tc> <w:tcPr> <w:tcW w:type="pct" w:w="1667"/> </w:tcPr> … </w:tc> </w:tr></w:tbl>

This table specifies that it has no preferred table width, but each cell shall be exactly 33.3 percent (1667 fiftieths of a percent) of the overall table width. The resulting table would therefore be sized such that all columns are of the width of the maximum column, as follows:

Hello world

The text Hello world makes the middle cell larger, and the other two cells are increased in size to maintain the preferred widths of one-third of the overall table width. However, when the middle table cell requires a larger size to accommodate non-breaking text, that preference may be overridden as needed:

Hello worlddddddddddddddddddddddddddddddddddd

In this case, the middle cell's long non breaking string caused the table to reach the text margins on the page, and therefore to override the preferred widths on the empty cells. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

textDirection (Table Cell Text Flow Direction)

This element specifies the direction of the text flow for this table cell.

If this element is omitted on a given table cell, its value is determined by the setting previously set at any level of the style hierarchy (i.e. that previous setting remains unchanged). If this setting is never specified in the style hierarchy, then the table cell shall inherit the text flow settings from the parent section.

[Example: Consider a table with one cell in which all the table cell's text flow is top to bottom - right to left:

Text in this table cell

This table cell would specify this text flow using the following WordprocessingML:

<w:tc>

<w:tcPr>

…

<w:textDirection w:val="tbRl" />

</w:tcPr>

…

</w:tc>

The textDirection element specifies via the tbRl value in the val attribute that the text flow should go top to bottom, then right to left. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (Direction of Text Flow)

Specifies the direction of the text flow for this object.

[Example: Consider a document with a section in which text shall flow bottom to top vertically, and left to right horizontally. This setting requires the following WordprocessingML:

<w:sectPr> … <w:textDirection w:val="btLr" /></w:sectPr>

The textDirection element specifies via the btLr value in the val attribute that the text flow shall go bottom to top, and left to right. end example]

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

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

</complexType>

tl2br (Table Cell Top Left to Bottom Right Diagonal Border)

This element specifies the border which shall be displayed on the top left side to bottom right diagonal within the current table cell.

If this element is omitted, then the top left to bottom right diagonal of this table cell shall not have a cell border, and its border may use the table's border settings as appropriate.

[Example: Consider a table in which the first cell in the first row specifies a top left to bottom right diagonal cell border as follows:

R1C1

R1C2

R2C1

R2C2

This diagonal cell border is specified using the following WordprocessingML:

<w:tc> <w:tcPr> … <w:tcBorders> <w:tl2br w:val="double" w:sz="4" w:space="0" w:color="FF0000"/> </w:tcBorders> </w:tcPr> <w:p/></w:tc>

The tl2br element specifies a point border of type double on the table cell's diagonal. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

top (Table Top Border)

This element specifies the border which shall be displayed at the top of the current table. The appearance of this table border in the document shall be determined by the following settings:

The display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the top of this table shall have the border specified by the associated table style. If no top border is specified in the style hierarchy, then this table shall not have a top border.

[Example: Consider a table in which the table properties specifies a top table border, as follows:

R1C1

R1C2

R2C1

R2C2

This top table border is specified using the following WordprocessingML:

<w:tbl> <w:tblPr> <w:tblBorders> <w:top w:val="thinThickThinMediumGap" w:sz="24" w:space="0" w:color="D0D0D0" w:themeColor="accent3" w:themeTint="99"/> </w:tblBorders> </w:tblPr> …</w:tbl>

The top element specifies a three point top table border of type thinThinThickMediumGap. end example].

Parent Elements

tblBorders (§2.4.37); tblBorders (§2.4.38)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

top (Table Cell Top Margin Default)

This element specifies the amount of space which shall be left between the top extent of the cell contents and the top border of all table cells within the parent table. This setting may be overridden by the table cell top margin definition specified by the top element contained within the table cell's properties (§2.4.73).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If this element is omitted, then it shall inherit the table cell margin from the associated table style. If a top margin is never specified in the style hierarchy, then this table shall have no top cell padding by default (excepting individual cell overrides).

[Example: Consider a two by two table in which the default table cell top margin is specified to be exactly 0.25 inches, as follows (marked with an arrow in the first table cell below):

R1C1

R2C1

R2C2

This table property is specified using the following WordprocessingML markup:

<w:tbl> <w:tblPr> <w:tblCellMar> <w:top w:w="360" w:type="dxa"/> </w:tblCellMar> </w:tblPr> …</w:tbl>

Every cell in the table has a default cell margin setting it to 360 twentieths of a point. end example]

Parent Elements

tblCellMar (§2.4.39); tblCellMar (§2.4.40)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

top (Table Cell Top Margin Exception)

This element specifies the amount of space which shall be left between the top extent of the cell contents and the top border of a specific table cell within a table. This setting shall override the table cell top margin definition specified by the top element contained within the table properties (§2.4.72).

This value is specified in the units applied via its type attribute. Any width value of type pct or auto for this element shall be ignored.

If omitted, then this table cell shall use the bottom cell margins defined in the top element contained within the table properties (§2.4.72).

[Example: Consider a table with two cells in which the first table cell’s top margin is specified via an exception to be ten times larger (0.2 inches vs. 0.02 inches) than the other table cell margins:

This text fills the extents of the cell.

So does this

The first cell in the table would be specified using the following WordprocessingML:

<w:tc> <w:tcPr> <w:tcMar> <w:top w:w="288" w:type="dxa" /> </w:tcMar> </w:tcPr></w:tc>

The first cell in this table has an exception applied to the table cell top cell margin setting it to 288 twentieths of a point (0.2 inches). end example]

Parent Elements

tcMar (§2.4.65)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

top (Table Cell Top Border)

This element specifies the border which shall be displayed at the top of the current table cell. The appearance of this table cell border in the document shall be determined by the following settings:

If the net tblCellSpacing element value (§2.4.41;§2.4.42;§2.4.43) applied to the cell is non-zero, then the cell border shall always be displayed

Otherwise, the display of the border is subject to the conflict resolution algorithm defined by the tcBorders element (§2.4.63) and the tblBorders element (§2.4.37;§2.4.38)

If this element is omitted, then the top of this table cell shall not have a cell border, and its border may use the table's border settings as appropriate.

[Example: Consider a table in which the first cell in the first row specifies a top cell border , as follows:

R1C1

R1C2

R2C1

R2C2

This top cell border is specified using the following WordprocessingML:

<w:tc> <w:tcPr> … <w:tcBorders> <w:top w:val="thinThickThinSmallGap" w:sz="24" w:space="0" w:color="FF0000"/> </w:tcBorders> </w:tcPr> <w:p/></w:tc>

The top element specifies a three point border of type thinThinThickSmallGap. end example]

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

tr (Table Row)

This element specifies a single table row, which contains the table’s cells. Table rows in WordprocessingML are analogous to HTML tr elements.

A tr element has one formatting child element, trPr (§2.4.78), which defines the properties for the row. Each unique property on the table row is specified by a child element of this element. As well, a table row can contain any valid row-level content, which allows for the use of table cells.

If a table cell does not include at least one child element other than the row properties, then this document shall be considered corrupt.

[Example: Consider a table consisting of a single table cell, which contains the text Hello World:

Hello World

This table row's content is represented by the following WordprocessingML:

<w:tr> <w:tc> <w:tcPr> <w:tcW w:w="0" w:type="auto"/> </w:tcPr> <w:p> <w:r> <w:t>Hello, World</w:t> </w:r> </w:p> </w:tc></w:tr>

The tr element contains a single row-level element - in this case, a table cell. end example]

Parent Elements

customXml (§2.5.1.4); sdtContent (§2.5.2.34); tbl (§2.4.36)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Cell-Level Custom XML Element)

§2.5.1.3

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Cell-Level Structured Document Tag)

§2.5.2.28

tblPrEx (Table-Level Property Exceptions)

§2.4.57

tc (Table Cell)

§2.4.62

trPr (Table Row Properties)

§2.4.78

Attributes

Description

rsidDel (Revision Identifier for Table Row Deletion)

Specifies a unique identifier used to track the editing session when the row was deleted from the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidR (Revision Identifier for Table Row)

Specifies a unique identifier used to track the editing session when the table row was added to the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidRPr (Revision Identifier for Table Row Glyph Formatting)

Specifies a unique identifier used to track the editing session when the glyph character representing the table row mark was last modified in the main document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

rsidTr (Revision Identifier for Table Row Properties)

Specifies a unique identifier used to track the editing session when the table row's properties were last modified in this document.

All rsid* attributes throughout this document with the same value, if present, must indicate that those regions were modified during the same editing session (time between subsequent save actions).

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions to indicate the order of the modifications relative to other modifications in this document.

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

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

</sequence>

</complexType>

tr2bl (Table Cell Top Right to Bottom Left Diagonal Border)

This element specifies the border which shall be displayed on the top right to bottom left diagonal within the current table cell.

If this element is omitted, then the top right to bottom left diagonal of this table cell shall not have a cell border, and its border may use the table's border settings as appropriate.

[Example: Consider a table in which the second cell in the second row specifies a top right to bottom left diagonal cell border as follows:

R1C1

R1C2

R2C1

R2C2

This diagonal cell border is specified using the following WordprocessingML:

<w:tc> <w:tcPr> … <w:tcBorders> <w:tr2bl w:val="double" w:sz="4" w:space="0" w:color="FF0000"/> </w:tcBorders> </w:tcPr> <w:p/></w:tc>

The tr2bl element specifies a point border of type double on the table cell's diagonal. end example

Parent Elements

tcBorders (§2.4.63)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

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

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

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

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

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

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

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

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

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

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

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

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

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

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

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

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

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

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

</complexType>

trHeight (Table Row Height)

This element specifies the height of the current table row within the current table. This height shall be used to determine the resulting height of the table row, which may be absolute or relative (depending on its attribute values).

If omitted, then the table row shall automatically resize its height to the height required by its contents (the equivalent of an hRule value of auto).

[Example: Consider the following WordprocessingML table:

Some text in R1C1.

Examining the WordprocessingML for this table, the trHeight element is not specified, so the row heights are automatically determined by their contents (in the first row, the text Some text in R1C1.). If the first row shall be restricted to 0.1 inches high (144 twentieths of a point) regardless of its contents, that would be specified using the trHeight element as follows:

<w:trPr> <w:trHeight w:val="144" w:hRule="exact"/></w:trPr>

The resulting table row would be exactly 144 twentieths of a point high:

Some text in R1C1.

end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

hRule (Table Row Height Type)

Specifies the meaning of the height specified for this table row.

The meaning of the value of the val attribute is defined based on the value of the hRule attribute for this table row as follows:

If the value of hRule is auto, then the table row's height should be automatically determined based on the height of its contents. The h value is ignored.

If the value of hRule is atLeast, then the table row's height should be at least the value the h attribute.

If the value of hRule is exact, then the table row's height should be exactly the value of the h attribute.

If this attribute is omitted, then its value shall be assumed to be auto.

[Example: Consider the following paragraph containing a table row:

<w:tr>

<w:trPr>

<w:trHeight w:val="2189" w:hRule="atLeast"/>

</w:trPr>

…

</w:tr>

The hRule attribute specifies a value of atLeast, so the table row will be a minimum of 2189 twentieths of a point high regardless of its contents, since its val value is 2189 twentieths of a point. end example]

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

val (Table Row Height)

Specifies the table row's height.

This height is expressed in twentieths of a point.

If this attribute is omitted, then its value shall be assumed to be 0.

The meaning of the value of the val attribute is defined based on the value of the hRule attribute for this table row as follows:

If the value of hRule is auto, then the table row's height should be automatically determined based on the height of its contents. This value is ignored.

If the value of hRule is atLeast, then the table row's height should be at least the value of this attribute.

If the value of hRule is exact, then the table row's height should be exactly the value of this attribute.

[Example: Consider the following table row:

<w:tr>

<w:trPr>

<w:trHeight w:val="2189" w:hRule="atLeast"/>

</w:trPr>

…

</w:tr>

The val attribute specifies a value of 2189 twentieths of a point, so this table row will be a minimum of 2189 twentieths of a point high regardless of its contents (growing if needed), since its hRule value is set to atLeast. end example]

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

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

</complexType>

trPr (Table Row Properties)

This element specifies the set of row-level properties applied to the current table row. Each unique property is specified by a child element of this element. These properties affect the appearance of all cells in the current row within the parent table, but may be overridden by individual cell-level properties, as defined by each property.

[Example: Consider the following WordprocessingML table:

Some text in R1C1.

The first row shall have a table-row level property which specifies that it shall be restricted to 0.1 inches high (144 twentieths of a point) regardless of its contents, that would be specified using the trHeight element as follows:

<w:trPr> <w:trHeight w:val="144" w:hRule="exact"/>

…</w:trPr>

The trPr element specifies the set of table row properties applied to the current table row in the document, in this case a row height requirement using the trHeight element (§2.4.77). end example]

Parent Elements

tr (§2.4.75)

Child Elements

Subclause

cantSplit (Table Row Cannot Break Across Pages)

§2.4.6

cnfStyle (Table Row Conditional Formatting)

§2.4.8

del (Deleted Table Row)

§2.13.5.14

divId (Associated HTML div ID)

§2.4.9

gridAfter (Grid Columns After Last Cell)

§2.4.10

gridBefore (Grid Columns Before First Cell)

§2.4.11

hidden (Hidden Table Row Marker)

§2.4.14

ins (Inserted Table Row)

§2.13.5.16

jc (Table Row Alignment)

§2.4.22

tblCellSpacing (Table Row Cell Spacing)

§2.4.42

tblHeader (Repeat Table Row on Every New Page)

§2.4.46

trHeight (Table Row Height)

§2.4.77

trPrChange (Revision Information for Table Row Properties)

§2.13.5.39

wAfter (Preferred Width After Table Row)

§2.4.82

wBefore (Preferred Width Before Table Row)

§2.4.83

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

</sequence>

</extension>

</complexContent>

</complexType>

trPr (Previous Table Row Properties)

This element specifies a previous set of table cell properties, the modifications to which shall be attributed to a revision by a particular author and at a particular time. This element contains the table cell property settings which were previously in place before a specific set of revisions by one author. Each unique property is specified by a child element of this element. These properties affect the appearance of all cells in the current row within the parent table, but may be overridden by individual cell-level properties, as defined by each property.

[Example: Consider the following WordprocessingML table:

Some text in R1C1.

This table has a row height for row one of exactly 0.1". If we change that to a row height of at least 0.1" with revision marking enabled, the table would appear as follows:

Some text in R1C1.

The resulting WordprocessingML would be:

<w:tr> <w:trPr> <w:trHeight w:val="144"/> <w:trPrChange w:id="2" … > <w:trPr> <w:trHeight w:hRule="exact" w:val="144"/> </w:trPr> </w:trPrChange> </w:trPr> …</w:tr>

The trPr element as a child of trPrChange specifies the set of table row properties which were in place before the current revision to the document. end example]

Parent Elements

trPrChange (§2.13.5.39)

Child Elements

Subclause

cantSplit (Table Row Cannot Break Across Pages)

§2.4.6

cnfStyle (Table Row Conditional Formatting)

§2.4.8

divId (Associated HTML div ID)

§2.4.9

gridAfter (Grid Columns After Last Cell)

§2.4.10

gridBefore (Grid Columns Before First Cell)

§2.4.11

hidden (Hidden Table Row Marker)

§2.4.14

jc (Table Row Alignment)

§2.4.22

tblCellSpacing (Table Row Cell Spacing)

§2.4.42

tblHeader (Repeat Table Row on Every New Page)

§2.4.46

trHeight (Table Row Height)

§2.4.77

wAfter (Preferred Width After Table Row)

§2.4.82

wBefore (Preferred Width Before Table Row)

§2.4.83

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

</choice>

</complexType>

vAlign (Table Cell Vertical Alignment)

This element specifies the vertical alignment for text within the current table cell. The vertical alignment of this text is determined by the value of the val attribute.

[Example: Consider a table with a single cell with text vertically aligned to the bottom of the cell:

R1C1

This requirement would be specified using the following WordprocessingML:

<w:tc>

<w:tcPr>

<w:vAlign w:val="bottom" />

</w:tcPr>

<w:r>

<w:t>R1C1</w:t>

</w:r>

</w:tc>

The vAlign element specifies the vertical alignment of the cell contents, in the case, the bottom of the table cell. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (Vertical Alignment Setting)

Specifies the vertical alignment for text between the top and bottom margins of the parent container (page or table cell).

[Example: Consider a region where the text shall be vertically centered in the parent element. This would require a val value of center, in order to specify that all justification vertically shall be centered relative to the parent. For a section, this setting would be specified as follows:

<w:vAlign w:val="center" />

The val attribute of center specifies that the content is centered relative to its container (in this case, the page). end example]

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

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

</complexType>

vMerge (Vertically Merged Cell)

This element specifies that this cell is part of a vertically merged set of cells in a table. The val attribute on this element determines how this cell is defined with respect to the previous cell in the table (i.e. does this cell continue the vertical merge or start a new merged group of cells).

If this element is omitted, then this cell shall not be part of any vertically merged grouping of cells, and any vertically merged group of preceding cells shall be closed. If a vertically merged group of cells do not span the same set of grid columns, then this vertical merge is invalid.

[Example: Consider a table with three rows and two columns with the last column completely vertically merged:

The second cell in the first row starts a vertical merge that is completed in the last cell, resulting in the following WordprocessingML:

<w:tbl> … <w:tr> <w:tc> … </w:tc> <w:tc> … </w:tc> <w:tc> <w:tcPr> <w:vmerge w:val="restart"/> </w:tcPr> … </w:tc> </w:tr>

<w:tr> <w:tc> … </w:tc> <w:tc> … </w:tc> <w:tc> <w:tcPr> <w:vmerge w:val="continue"/> </w:tcPr> … </w:tc> </w:tr>

<w:tr> <w:tc> … </w:tc> <w:tc> … </w:tc> <w:tc> <w:tcPr> <w:vmerge w:val="continue"/> </w:tcPr> … </w:tc> </w:tr></w:tbl>

The vmerge element defines the cells which are vertically merged, and how each cell is merged together. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

val (Vertical Merge Type)

Specifies how the table cell is part of a vertically merged region. This determines whether the cell should join onto an existing grouping of merged cells if any exist, or start a new group of merged cells. Refer to the simple type definition for a full description of each type.

If this attribute is omitted, its value shall be assumed to be continue.

[Example: Consider a table cell where a vertical cell merge begins . This setting is represented as the following WordprocessingML:

<w:tcPr>

<w:vmerge w:val="restart"/>

</w:tcPr>

The attribute value of restart specifies that this element shall start a new vertically merged region in this table. end example]

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

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

</complexType>

wAfter (Preferred Width After Table Row)

This element specifies the preferred width for the total number of grid columns after this table row as specified in the gridAfter element (§2.4.10). This preferred width is used as part of the table layout algorithm specified by the tblLayout element (§2.4.49; §2.4.50) - full description of the algorithm in the ST_TblLayout simple type (§2.18.94).

All widths in a table are considered preferred because:

The table must satisfy the shared columns as specified by the tblGrid element (§2.4.44)

Two or more widths may have conflicting values for the width of the same grid column

The table layout algorithm (§2.18.94) may require a preference to be overridden

If this element is omitted, then the cell width shall be of type auto.

[Example: Consider a WordprocessingML table row defined as follows:

<w:tr> <w:trPr> <w:gridAfter w:val="2"/> <w:wAfter w:type="fixed" w:w="1440"/> </w:trPr> …</w:tr>

This table specifies that it has a preferred table width of 1440 twentieths of a point (one inch) for the two grid columns after the end of that row. The resulting table would therefore be sized such that that set of grid columns is one inch whenever possible, for example the second row in this table:

end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

wBefore (Preferred Width Before Table Row)

This element specifies the preferred width for the total number of grid columns before this table row as specified in the gridAfter element (§2.4.10). This preferred width is used as part of the table layout algorithm specified by the tblLayout element (§2.4.49; §2.4.50) - full description of the algorithm in the ST_TblLayout simple type (§2.18.94).

All widths in a table are considered preferred because:

The table must satisfy the shared columns as specified by the tblGrid element (§2.4.44)

Two or more widths may have conflicting values for the width of the same grid column

The table layout algorithm (§2.18.94) may require a preference to be overridden

If this element is omitted, then the cell width shall be of type auto.

[Example: Consider a WordprocessingML table row defined as follows:

<w:tr> <w:trPr> <w:gridBefore w:val="1"/> <w:wBefore w:type="fixed" w:w="1440"/> </w:trPr> …</w:tr>

This table specifies that it has a preferred table width of 1440 twentieths of a point (one inch) for the grid column before the start of the row. The resulting table would therefore be sized such that that grid column is one inch whenever possible, for example the second row in this table:

end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78); trPr (§2.4.79)

Attributes

Description

type (Table Width Type)

If this attribute is omitted, then its value shall be assumed to be dxa (twentieths of a point).

[Example: Consider a table with a table cell bottom cell spacing with a type of dxa, as follows:

<w:bottom ... w:type="dxa" />

This type shall therefore be used to interpret the width specified in the w attribute as a value in twentieths of a point. end example]

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

w (Table Width Value)

If this attribute is omitted, then its value shall be assumed to be 0.

[Example: Consider a table with a bottom margin with a width of 302, as follows:

<w:bottom w:w="302" w:type="dxa" />

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

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

</complexType>

Custom Markup

Within a WordprocessingML document, it is often necessary for specific documents to contain semantic information beyond the presentation information specified by this Office Open XML Standard. [Example: An invoice document may wish to specify that a particular sentence of text is a customer name, in order for that information to be easily extracted from the document without the need to parse the text using regular expression matching or similar. end example]

For these scenarios, multiple facilities are provided for the insertion and round-tripping of customer defined semantics within a WordprocessingML document. There are three distinct forms in which customer-defined semantics can be inserted into a WordprocessingML document, each with their own specific intended usage:

Smart tags

Custom XML markup

Structured document tags (content controls)

The elements and attributes which define each of these forms is described in the following clauses.

Custom XML and Smart Tags

The final type of customer-defined semantics which can be embedded in a WordprocessingML document are structured document tags (SDTs).

As shown above, smart tags and custom XML markup each provide a facility for embedding customer-defined semantics into the document: smart tags, via the ability to provide a basic namespace/name for a run or set of runs within a documents; and custom XML markup, via the ability to tag the document with XML elements and attributes specified by any valid XML Schema file.

However, each of these techniques, while they each provide a way to add the desired semantic information, does not provide a way to affect the presentation or interaction within the document. To bridge these two worlds, structured document tags allow both the specification of customer semantics as well as the ability to influence the presentation of that data in the document.

This means that the customer can define the semantics and context of the tag, but can then use a rich set of pre-defined properties to define its behavior and appearance within the WordprocessingML document's presentation.

[Example: Consider a region which should be tagged with the semantic of "birthday", for the user to enter their date or birth into the document. Ideally, this region would also utilize a date picker to allow the user to enter the date from a calendar:

This content would be specified using the following WordprocessingML:

<w:sdt> <w:sdtPr> <w:alias w:val="Birthday"/> <w:id w:val="8775518"/> <w:placeholder> <w:docPart w:val="DefaultPlaceholder_22479095"/> </w:placeholder> <w:showingPlcHdr/> <w:date> <w:dateFormat w:val="M/d/yyyy"/> <w:lid w:val="EN-US"/> </w:date> </w:sdtPr> <w:sdtContent> <w:p> <w:r> <w:rPr> <w:rStyle w:val="PlaceholderText"/> </w:rPr> <w:t>Click here to enter a date...</w:t> </w:r> </w:p> </w:sdtContent></w:sdt>

end example]

As shown above, each of the structured document tags in the WordprocessingML file is represented using the sdt element.

Within a structured document tag, there are two child elements which contain the definition and the content of this SDT. The first of these is the sdtPr element, which contains the set of properties specified for this structured document tag. The second is the sdtContent element, which contains all the content which is contained within this structured document tag.

attr (Custom XML Attribute)

This element specifies a custom XML attribute which shall be located on the parent custom XML element specified via the customXml element (§2.5.1.3;§2.5.1.4;§2.5.1.5; §2.5.1.6). The attributes on this element shall be used to specify the contents of the custom XML attribute.

[Example: Consider a custom XML element with the following properties:

<w:customXmlPr> <w:attr w:name="companyName" … /> <w:attr w:name="companySymbol … /></w:customXmPr>

This property bag specifies that the parent custom XML element shall have two attributes associated with it, he first with a name of companyName, and the second with a name of companySymbol. end example]

Parent Elements

customXmlPr (§2.5.1.7)

Attributes

Description

name (Name)

Specifies the name of the current custom XML attribute or smart tag property.

[Example: Consider a custom XML attribute which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXmlPr> <w:attr w:name="companyName" … /></w:customXmlPr>

The name attribute specifies that the name for this property shall be companyName. end example]

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

uri (Namespace)

Specifies the namespace URI of the current custom XML attribute or smart tag property.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a smart tag property which shall have a namespace URI of http://schemas.openxmlformats.org/2006/example. This requirement would be specified using the following WordprocessingML:

<w:smartTagPr> <w:attr w:uri="http://schemas.openxmlformats.org/2006/example" … /></w:smartTagPr>

The uri attribute specifies that the namespace for this property shall be http://schemas.openxmlformats.org/2006/example. end example]

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

val (Value)

Specifies the value of the current custom XML attribute or smart tag property.

[Example: Consider a smart tag property which shall have a value of propertyValue. This requirement would be specified using the following WordprocessingML:

<w:smartTagPr> <w:attr … w:val="propertyValue" /></w:smartTagPr>

The val attribute specifies that the value for this property shall be propertyValue. end example]

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

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

</complexType>

attr (Smart Tag Property)

This element specifies a single smart tag property which shall be located on the parent smart tag, specified via the smartTag element (§2.5.1.9). The attributes on this element shall be used to specify the contents of smart tag property.

[Example: Consider a smart tag with the following properties:

<w:smartTagPr> <w:attr w:name="attributeOne" … /> <w:attr w:name="attributeTwo" … /></w:smartTagPr>

This property bag specifies that the parent smart tag shall have two properties associated with it, the first with a name of attributeOne, and the second with a name of attributeTwo. end example].

Parent Elements

smartTagPr (§2.5.1.10)

Attributes

Description

name (Name)

Specifies the name of the current custom XML attribute or smart tag property.

[Example: Consider a custom XML attribute which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXmlPr> <w:attr w:name="companyName" … /></w:customXmlPr>

The name attribute specifies that the name for this property shall be companyName. end example]

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

uri (Namespace)

Specifies the namespace URI of the current custom XML attribute or smart tag property.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a smart tag property which shall have a namespace URI of http://schemas.openxmlformats.org/2006/example. This requirement would be specified using the following WordprocessingML:

<w:smartTagPr> <w:attr w:uri="http://schemas.openxmlformats.org/2006/example" … /></w:smartTagPr>

The uri attribute specifies that the namespace for this property shall be http://schemas.openxmlformats.org/2006/example. end example]

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

val (Value)

Specifies the value of the current custom XML attribute or smart tag property.

[Example: Consider a smart tag property which shall have a value of propertyValue. This requirement would be specified using the following WordprocessingML:

<w:smartTagPr> <w:attr … w:val="propertyValue" /></w:smartTagPr>

The val attribute specifies that the value for this property shall be propertyValue. end example]

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

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

</complexType>

customXml (Cell-Level Custom XML Element)

This element specifies the presence of a custom XML element around a single table cell. The attributes on this element shall be used to specify the name and namespace URI of the current custom XML element.

[Example: Consider a custom XML element with the name company that shall be located around a single table cell in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:tr> <w:customXml w:element="company" … > <w:tc> … </w:tc> </w:customXml> …</w:tr>

The customXml element specifies that the name of the custom XML element is company, and the custom XML element contains a single table cell (it is a cell-level element). end example]

Parent Elements

customXml (§2.5.1.3); sdtContent (§2.5.2.33); tr (§2.4.75)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Cell-Level Custom XML Element)

§2.5.1.3

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

customXmlPr (Custom XML Element Properties)

§2.5.1.7

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Cell-Level Structured Document Tag)

§2.5.2.28

tc (Table Cell)

§2.4.62

Attributes

Description

element (Custom XML Element Name)

Specifies the name of the current custom XML element or smart tag within the document.

[Example: Consider a custom XML element which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXml w:element="companyName" … > …</w:customXml>

The element attribute specifies that the name for this element shall be companyName. end example]

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

uri (Custom XML Element Namespace)

Specifies the namespace URI of the current custom XML element or smart tag.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a custom XML element which shall have a namespace URI of urn:customXmlExample. This requirement would be specified using the following WordprocessingML:

<w:customXml … w:uri="urn:customXmlExample" /> …</w:customXml>

The uri attribute specifies that the namespace for this element shall be urn:customXmlExample. end example]

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

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

</sequence>

</complexType>

customXml (Row-Level Custom XML Element)

This element specifies the presence of a custom XML element around a single table row. The attributes on this element shall be used to specify the name and namespace URI of the current custom XML element.

[Example: Consider a custom XML element with the name invoiceItem that shall be located around a single table row in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:tbl> <w:customXml w:element="invoiceItem" … > <w:tr> … </w:tr> </w:customXml> …</w:tbl>

The customXml element specifies that the name of the custom XML element is invoiceItem, and the custom XML element contains a single table row (it is a row-level element). end example]

Parent Elements

customXml (§2.5.1.4); sdtContent (§2.5.2.34); tbl (§2.4.36)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Row-Level Custom XML Element)

§2.5.1.4

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

customXmlPr (Custom XML Element Properties)

§2.5.1.7

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Row-Level Structured Document Tag)

§2.5.2.31

tr (Table Row)

§2.4.75

Attributes

Description

element (Custom XML Element Name)

Specifies the name of the current custom XML element or smart tag within the document.

[Example: Consider a custom XML element which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXml w:element="companyName" … > …</w:customXml>

The element attribute specifies that the name for this element shall be companyName. end example]

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

uri (Custom XML Element Namespace)

Specifies the namespace URI of the current custom XML element or smart tag.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a custom XML element which shall have a namespace URI of urn:customXmlExample. This requirement would be specified using the following WordprocessingML:

<w:customXml … w:uri="urn:customXmlExample" /> …</w:customXml>

The uri attribute specifies that the namespace for this element shall be urn:customXmlExample. end example]

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

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

</sequence>

</complexType>

customXml (Inline-Level Custom XML Element)

This element specifies the presence of a custom XML element around one or more inline level structures (runs, images, fields, etc.) within a paragraph. The attributes on this element shall be used to specify the name and namespace URI of the current custom XML element.

[Example: Consider a custom XML element with the name firstName that shall be located around a two text runs in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:p> <w:customXml w:element="firstName" … > <w:r> … </w:r> <w:r> … </w:r> </w:customXml> …</w:p>

The customXml element specifies that the name of the custom XML element is firstName, and the custom XML element contains a two text runs (it is an inline-level element). end example]

Parent Elements

customXml (§2.5.1.5); del (§2.13.5.12); fldSimple (§2.16.21); hyperlink (§2.16.24); ins (§2.13.5.20); moveFrom (§2.13.5.21); moveTo (§2.13.5.26); p (§2.3.1.22); sdtContent (§2.5.2.35); smartTag (§2.5.1.9)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

customXmlPr (Custom XML Element Properties)

§2.5.1.7

del (Deleted Run Content)

§2.13.5.12

fldSimple (Simple Field)

§2.16.21

hyperlink (Hyperlink)

§2.16.24

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

subDoc (Anchor for Subdocument Location)

§2.17.2.1

Attributes

Description

element (Element name)

Specifies the name of the current custom XML element or smart tag within the document.

[Example: Consider a custom XML element which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXml w:element="companyName" … > …</w:customXml>

The element attribute specifies that the name for this element shall be companyName. end example]

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

uri (Custom XML Markup Namespace)

Specifies the namespace URI of the current custom XML element or smart tag.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a custom XML element which shall have a namespace URI of urn:customXmlExample. This requirement would be specified using the following WordprocessingML:

<w:customXml … w:uri="urn:customXmlExample" /> …</w:customXml>

The uri attribute specifies that the namespace for this element shall be urn:customXmlExample. end example]

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

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

</sequence>

</complexType>

customXml (Block-Level Custom XML Element)

This element specifies the presence of a custom XML element around one or more block level structures (paragraphs, tables, etc.). The attributes on this element shall be used to specify the name and namespace URI of the current custom XML element.

[Example: Consider a custom XML element with the name address that shall be located around a single paragraph in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:body> <w:customXml w:element="address" … > <w:p> … </w:p> </w:customXml> …</w:body>

The customXml element specifies that the name of the custom XML element is address, and the custom XML element contains a single paragraph (it is a block-level element). end example]

Parent Elements

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

customXmlPr (Custom XML Element Properties)

§2.5.1.7

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

Attributes

Description

element (Custom XML Element Name)

Specifies the name of the current custom XML element or smart tag within the document.

[Example: Consider a custom XML element which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXml w:element="companyName" … > …</w:customXml>

The element attribute specifies that the name for this element shall be companyName. end example]

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

uri (Custom XML Element Namespace)

Specifies the namespace URI of the current custom XML element or smart tag.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a custom XML element which shall have a namespace URI of urn:customXmlExample. This requirement would be specified using the following WordprocessingML:

<w:customXml … w:uri="urn:customXmlExample" /> …</w:customXml>

The uri attribute specifies that the namespace for this element shall be urn:customXmlExample. end example]

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

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

</sequence>

</complexType>

customXmlPr (Custom XML Element Properties)

This element specifies the set of properties which shall be applied to the parent custom XML element.

[Example: Consider a custom XML element with the following properties specified:

<w:customXmlPr> <w:placeholder w:val="[Fill in your name]"/> <w:attr w:name="status" w:val="draft"/></w:customXmlPr>

This custom XML element specifies two properties: the presence of placeholder text via the placeholder element (§2.5.1.8) and a single custom XML attribute via the attr element (§2.5.1.1). end example]

Parent Elements

customXml (§2.5.1.3); customXml (§2.5.1.6); customXml (§2.5.1.5); customXml (§2.5.1.4)

Child Elements

Subclause

attr (Custom XML Attribute)

§2.5.1.1

placeholder (Custom XML Element Placeholder Text)

§2.5.1.8

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

</sequence>

</complexType>

placeholder (Custom XML Element Placeholder Text)

This element specifies the placeholder text which shall be displayed in place of this custom XML element when the contents of this custom XML markup are empty (i.e. there are no runs of text within the current custom XML element). If this custom XML element does contain run content, then this text shall not be displayed.

The val attribute stores the string of text which shall be displayed as the placeholder text. This string may be displayed in any font face/size desired by the hosting application.

[Example: Consider a custom XML element with the following properties specified:

<w:customXmlPr> <w:placeholder w:val="[Fill in your name]"/> <w:attr w:name="status" w:val="draft"/></w:customXmlPr>

The placeholder element specifies that this custom XML element shall display the text contents [Fill in your name] whenever there is no run content within the parent custom XML element. For example, if the custom XML element was specified as follows:

<w:customXml> <w:customXmlPr> <w:placeholder w:val="[Fill in your name]"/> </w:customXmlPr> <w:p/></w:customXml>

This custom XML element has no run content and the placeholder text would be displayed. However, if there is run content, as follows:

<w:customXml> <w:customXmlPr> <w:placeholder w:val="[Fill in your name]"/> </w:customXmlPr> <w:p> <w:r> <w:t>Name</w:t> </w:r> </w:p></w:customXml>

This custom XML element now contains run content, and the placeholder text shall not be displayed. end example]

Parent Elements

customXmlPr (§2.5.1.7)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

smartTag (Inline-Level Smart Tag)

This element specifies the presence of a smart tag around one or more inline structures (runs, images, fields, etc.) within a paragraph. The attributes on this element shall be used to specify the name and namespace URI of the current smart tag.

[Example: Consider a smart tag with the name firstName that shall be located around a two text runs in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:p> <w:smartTag w:element="firstName" … > <w:r> … </w:r> <w:r> … </w:r> </w:smartTag> …</w:p>

The smartTag element specifies that the name of the smart tag is firstName, and the smart tag contains a two text runs (it is an inline-level smart tag). end example]

Parent Elements

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

fldSimple (Simple Field)

§2.16.21

hyperlink (Hyperlink)

§2.16.24

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

smartTagPr (Smart Tag Properties)

§2.5.1.10

subDoc (Anchor for Subdocument Location)

§2.17.2.1

Attributes

Description

element (Smart Tag Name)

Specifies the name of the current custom XML element or smart tag within the document.

[Example: Consider a custom XML element which shall have a name of companyName. This requirement would be specified using the following WordprocessingML:

<w:customXml w:element="companyName" … > …</w:customXml>

The element attribute specifies that the name for this element shall be companyName. end example]

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

uri (Smart Tag Namespace)

Specifies the namespace URI of the current custom XML element or smart tag.

If this attribute is omitted, the URI shall be assumed to be null (no associated URI).

[Example: Consider a custom XML element which shall have a namespace URI of urn:customXmlExample. This requirement would be specified using the following WordprocessingML:

<w:customXml … w:uri="urn:customXmlExample" /> …</w:customXml>

The uri attribute specifies that the namespace for this element shall be urn:customXmlExample. end example]

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

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

</sequence>

</complexType>

smartTagPr (Smart Tag Properties)

This element specifies the set of properties which shall be applied to the parent smart tag.

[Example: Consider a smart tag with the following properties specified:

<w:smartTagPr> <w:attr w:name="date" w:val="01/01/2006"/> <w:attr w:name="status" w:val="draft"/></w:smartTagPr>

This smart tag specifies two properties: the presence of two smart tag properties via the attr element (§2.5.1.2). end example]

Parent Elements

smartTag (§2.5.1.9)

Child Elements

Subclause

attr (Smart Tag Property)

§2.5.1.2

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

</sequence>

</complexType>

Structured Document Tags

The final type of customer-defined semantics which can be embedded in a WordprocessingML document are structured document tags (SDTs).

This content would be specified using the following WordprocessingML:

end example]

As shown above, each of the structured document tags in the WordprocessingML file is represented using the sdt element.

alias (Friendly Name)

This element specifies the friendly name associated with the current structured document tag. The string representing the friendly name shall be stored on this element's val attribute.

If this element is omitted, then no friendly name shall be associated with the given structured document tag.

[Example: Consider the following properties on a structured document tag:

<w:sdtPr> <w:alias w:val="Birthday"/> …</w:sdtPr>

This set of properties specifies via the alias element that the friendly name for the parent structured document tag shall be Birthday. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

bibliography (Bibliography Structured Document Tag)

This element specifies that the parent structured document tag shall be of type bibliography.

This type setting does not require or imply that the contents of the structured document tag shall contain only a field of type BIBLIOGRAPHY, it shall only be used to specify that the structured document tag is of this type, which may be used by an application as desired.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:bibliography/> </w:sdtPr> …</w:sdt>

The bibliography element in this structured document tag's properties specify that the type of structured document tag is bibliography. end example]

Parent Elements

sdtPr (§2.5.2.37)

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

calendar (Date Picker Calendar Type)

This element specifies the type of calendar which shall be displayed for the current date picker structured document tag, if a user interface is present for the structured document tag. The calendar type is stored on this element's val attribute.

If this element is omitted, then the calendar type shall be gregorian.

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:date w:fullDate="01-01-2006T06:30:00Z"> <w:calendar w:val="gregorian"/> </w:date></w:sdtPr>

The calendar element specifies that the calendar type for a calendar which may be displayed in the document shall be the Gregorian calendar format (gregorian). end example]

Parent Elements

date (§2.5.2.7)

Attributes

Description

val (Calendar Type Value)

Specifies a type of calendar, the use of which is determined by the parent XML element.

If this attribute is omitted, then the calendar type shall be gregorian.

[Example: Consider the following WordprocessingML for a document containing a structured document tag:

<w:sdtPr> <w:date … > <w:calendar w:val="japan"/> </w:date></w:sdtPr>

The val attribute value of japan specifies that the Japanese Emperor Era calendar shall be used; in this case, it is used for the calendar displayed for a date structured document tag. end example]

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

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

</complexType>

citation (Citation Structured Document Tag)

This element specifies that the parent structured document tag shall be of type citation.

This type setting does not require or imply that the contents of the structured document tag shall contain only a field of type CITATION, it shall only be used to specify that the structured document tag is of this type, which may be used by an application as desired.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:citation/> </w:sdtPr> …</w:sdt>

The citation element in this structured document tag's properties specify that the type of structured document tag is citation. end example]

Parent Elements

sdtPr (§2.5.2.37)

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

comboBox (Combo Box Structured Document Tag)

This element specifies that the parent structured document tag shall be a combo box when displayed in the document.

This setting specifies that the behavior for this structured document tag shall be as follows:

The child elements of this element specify choices which shall be displayed in a standard drop-down list format

Formatting applied to any part of this structured document tag's contents shall apply to its entire contents

As well, the structured document tag must satisfy the following restraints or the document shall be considered invalid:

The contents shall only be contain a single run (one set of formatting properties)

The contents shall not contain more than a single paragraph or table cell and shall not contain a table row or table

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:comboBox> … </w:comboBox> </w:sdtPr> …</w:sdt>

The comboBox element in this structured document tag's properties specify that the type of structured document tag is a combo box. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

listItem (Combo Box List Item)

§2.5.2.20

Attributes

Description

lastValue (Combo Box Last Saved Value)

Specifies the value associated with the current display text for the combo box structured document tag.

If this structured document tag is not mapped to XML using the dataBinding element (§2.5.2.6), then this attribute shall be ignored. If this structured document tag is mapped to XML, it shall be used to determine whether the current display text in the combo box structured document tag shall be retained when the document is opened, as follows:

When the XML mapping is created, the content in the custom XML data is retrieved

If this content has an associated list item (matching its value attribute), then the corresponding display text shall be displayed in the structured document tag

If no list item exists, this content shall be matched against the lastValue attribute value. If the values match, the current display text shall be retained. If the values do not match, the current custom XML data content shall be the new display text (since no match exists in the combo box list items)

[Example: Consider a combo box structured document tag defined as follows:

<w:sdt> <w:sdtPr> <w:dataBinding … /> <w:comboBox w:lastValue="2"/> </w:sdtPr> <w:sdtContent> <w:r> <w:t>Hello world</w:t> </w:r> </w:sdtContent></w:sdt>

The current run content of the structured document tag reads Hello world. When this document is opened, if the current value of the associated custom XML data is 2, the matching lastValue attribute specifies that the contents of the combo box shall continue to be the current display text of the combo boxeven though there is no listItem whose value is 2 (and normally, the content of the structured document tag would be set to 2. Essentially, this attribute specifies a listItem whose value is 2 and whose displayText is Hello world (the current structured document tag contents). end example]

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

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

</sequence>

</complexType>

dataBinding (XML Mapping)

This element specifies the information which shall be used to establish a mapping between the parent structured document tag and an XML element stored within a Custom XML Data part in the current WordprocessingML document.

If this element is omitted, then no XML mapping shall be associated with the current structured document tag. If the parent structured document tag is of type rich text or document part gallery, then this property shall be ignored.

If this element is present and the parent structured document tag is not of a rich text type, then the current value of the structured document tag shall be determined by finding the XML element (if any) which is determined by the attributes on this element. If this information does not result in a valid XML element, then the application may use any algorithm desired to find the closest available match. If this information does result in a valid XML element, then the contents of that element shall be used to replace the current run content within the document.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> <w:dataBinding w:xpath="/root/name/first" … /> <w:text/> </w:sdtPr> <w:sdtContent> <w:r> <w:t>old text</w:t> </w:r> </w:sdtContent></w:sdt>

This structured document tag specifies that it contains only plain text via the text element, and that it shall be mapped to the element in the first Custom XML Data part which contains an element that matches the XPath expression /root/name/first. When that element is located, its contents shall replace the existing run content in the document (for example, if its contents are new text, then the contents of the run for this structured document tag shall be new text when the document is displayed. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

prefixMappings (XML Namespace Prefix Mappings)

Specifies the set of prefix mappings which shall be used to interpret the XPath expression specified on the xpath attribute when the XPath expression is evaluated against the custom XML data parts in the current document.

This attribute's value shall be specified using the following syntax: xmlns:prefix='namespace', where prefix is the namespace prefix to be mapped, and namespace is the namespace to be mapped to the current prefix. Each prefix mapping shall be delimited by one or more whitespace characters in the attribute's contents.

If this attribute is omitted, then the prefix mappings specified on each of the custom XML data parts itself shall be used to evaluate the given XPath expression.

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:dataBinding w:xpath="//ns0:book" w:prefixMapping="xmlns:ns0=

'http://example.com/example'"/> <w:text/></w:sdtPr>

This structured document tag specifies that it contains an XML mapping, and that mapping's prefixMapping attribute shall signify that the set of namespace prefix mappings to be used to evaluate the xpath attribute value shall be xmlns:ns0= 'http://example.com/example'. end example]

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

storeItemID (Custom XML Data Storage ID)

Specifies the custom XML data identifier for the custom XML data part which shall be used to evaluate the given XPath expression. The custom XML data identifier, specified using the storeItemID attribute of the dataStoreItem element (§7.5.2.1) on the Custom XML Data Properties part is a string that uniquely identifies a particular custom XML data part in a WordprocessingML document (as multiple parts may have the same namespace for their root element).

If specified, then the XPath expression specified on the xpath attribute shall only be evaluated against the custom XML data part whose properties part has a matching custom XML data identifier. If no custom XML data part exists with a matching identifier, then the XML mapping shall not be connected.

If omitted, then the XPath expression shall be evaluated against each custom XML data part in turn until the given XPath expression is resolved to an XML element.

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:dataBinding w:xpath="//ns0:book" w:storeItemID="testXmlPart"

/> <w:text/></w:sdtPr>

This structured document tag specifies that it contains an XML mapping, and that mapping shall only be evaluated against the custom XML part whose identifier is equal to testXmlPart (if one exists). end example]

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

xpath (XPath)

Specifies the XPath expression which shall be evaluated to find the custom XML node which is mapped to the parent structured document tag. This XPath expression shall be specified using the syntax defined in the XML Path Language (XPath) Version 1.0 specification (see Annex A for bibliographic reference information).

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:dataBinding w:xpath="//ns0:book" w:prefixMapping="xmlns:ns0=

'http://example.com/example'"/> <w:text/></w:sdtPr>

This structured document tag specifies that it contains an XML mapping, and that mapping's xpath attribute shall signify that the XPath expression to be evaluated shall be //ns0:book. Because the prefixMapping attribute is also specified, those prefix mappings shall be used to evaluate this XPath expression. end example]

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

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

</complexType>

date (Date Structured Document Tag)

This element specifies that the parent structured document tag shall be a date picker when displayed in the document.

This setting specifies that the behavior for this structured document tag shall be as follows:

The child elements of this element specify how the dates in this structured document tag shall be stored in any mapped custom XML data and displayed in the document

Formatting applied to any part of this structured document tag's contents shall apply to its entire contents

As well, the structured document tag must satisfy the following restraints or the document shall be considered invalid:

The contents shall only be contain a single run (one set of formatting properties)

The contents shall not contain more than a single paragraph or table cell and shall not contain a table row or table cell

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:date> … </w:date> </w:sdtPr> …</w:sdt>

The date element in this structured document tag's properties specifies that the type of structured document tag is a date picker. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

calendar (Date Picker Calendar Type)

§2.5.2.3

dateFormat (Date Display Mask)

§2.5.2.8

lid (Date Picker Language ID)

§2.5.2.19

storeMappedDataAs (Custom XML Data Date Storage Format)

§2.5.2.39

Attributes

Description

fullDate (Last Known Date in XML Schema DateTime Format)

Specifies the full date and time last entered into the parent structured document tag using the standard XML Schema DateTime syntax.

[Note: This cache is used because the date display mask stored on the dateFormat element (§2.5.2.8) may not contain all of the information about the date, which may be needed if the date display mask is later changed. end note]

If this attribute is specified, then the current fullDate attribute shall be used to populate the run content of the parent structured document tag by filtering it through the date display mask specified in the dateFormat element, if one is present.

If this attribute is omitted, then the current display text shall be maintained when the document is displayed.

[Example: Consider the following structured document tag properties:

<w:sdtPr> … <w:date w:fullDate="01-01-2006T05:30:00Z"> … </w:date></w:sdtPr>

The full XML Schema DateTime format for the current structured document tag is specified via the fullDate attribute value as 01-01-2006T05:30:00Z. end example]

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

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

</sequence>

</complexType>

dateFormat (Date Display Mask)

The element specifies the display format which shall be used to format any date entered into the parent structured document tag in full DateTime format [Example: Through a user interface (a date picker), or through custom XML data associated with this structured document tag via the dataBinding element (§2.5.2.6). end example] before displaying it in the structured document tag's run content.

If this element is omitted, then the date shall be formatted using the standard date display mask for the language ID specified on the lid element (§2.5.2.19) if present, or the language ID of the run contents otherwise.

The date display mask specified in the val attribute shall be interpreted using the semantics specified in §2.16.4.1 of this Office Open XML Standard.

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:date w:fullDate="01-01-2006T06:30:00Z"> <w:dateFormat w:val="MM-YYYY"/> </w:date></w:sdtPr>

The full XML Schema DateTime format for the current structured document tag is specified via the fullDate attribute value as 01-01-2006T06:30:00Z, and the date display mask is MM-YYYY, therefore the resulting date displayed in the document shall be 01-2006 (the month and long year from the full date value, respectively). end example]

Parent Elements

date (§2.5.2.7)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

docPart (Document Part Reference)

This element specifies the name of the document part which shall be displayed in the parent structured document tag when its run contents are empty. If this element is specified, then a document part whose name element (§2.12.12) specifies a name matching the value of this element, and which belongs to the bbPlcHdr type shall be located to be used as the placeholder text for the parent structured document tag.

If no document part is located matching the criteria specified by this element, then five non-breaking spaces shall be used as the default placeholder text.

[Example: Consider a structured document tag defined as follows:

<w:sdt> <w:sdtPr> <w:placeholder> <w:docPart w:val="DefaultPlaceholder_22610170" /> </w:placeholder> … </w:sdtPr> <w:sdtContent> … </w:sdtContent></w:sdt>

This structured document tag specifies through the docPart element that its placeholder text shall be specified in the document part of type bbPlcHdr whose name is equal to DefaultPlaceholder_22610170. end example]

Parent Elements

placeholder (§2.5.2.24)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

docPartCategory (Document Part Category Filter)

This element specifies the category of document parts which shall be used as the filter when determining the possible choices of document parts which are displayed for insertion into the parent structured document tag. A document part category is a sub-classification within a given document part gallery which may be used to further categorize the parts in a given gallery. [Example: Gallery custom1 may have categories of Legal Clauses, Conformance Clauses, etc. end example]. The category which shall be used as a filter is stored in this element's val attribute.

If this element is omitted, then the parent structured document tag shall display all document parts in the specified gallery regardless their specified category. If this element is present, but no document parts of the specified gallery and category combination are located by the application, then no document parts shall be displayed (i.e. the application shall not fall back to showing document parts in all categories in the specified gallery).

[Example: Consider the following properties for a structured document tag:

<w:sdtPr> <w:docPartList> <w:docPartGallery w:val="custom1"/> <w:docPartCategory w:val="Legal Clauses"/> </w:docPartList></w:sdtPr>

This structured document tag specifies that it shall present a selection of document parts for insertion via the docPartList element (§2.5.2.12) , and those document parts shall only be the parts which are in the custom1 gallery via the docPartType element (§2.5.2.11), and within that gallery, only the document parts which are in a category called Legal Clauses via this element. end example]

Parent Elements

docPartList (§2.5.2.12); docPartObj (§2.5.2.13)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

docPartGallery (Document Part Gallery Filter)

This element specifies the gallery of document parts which shall be used as the filter when determining the possible choices of document parts which are displayed for insertion into the parent structured document tag. A document part gallery is a classification of document parts, which may then be subdivided into categories. [Example: A gallery with a name of custom1 may have categories of Legal Clauses, Conformance Clauses, etc. end example]. The gallery which shall be used is stored in this element's val attribute.

If this element is omitted, then the parent structured document tag shall display all document parts in its default gallery. If this element is present, but no document parts of the specified gallery are located by the application, then document parts in the default gallery hall be displayed (i.e. the application shall behave as if the value was omitted).

[Example: Consider the following properties for a structured document tag:

<w:sdtPr> <w:docPartList> <w:docPartGallery w:val="custom1"/> </w:docPartList></w:sdtPr>

Parent Elements

docPartList (§2.5.2.12); docPartObj (§2.5.2.13)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

docPartList (Document Part Gallery Structured Document Tag)

This element specifies that the parent structured document tag shall be of a document part gallery type.

This type setting does not require or imply that the contents of the structured document tag shall contain only the exact contents of a document part of the specified gallery and category which is present on the current machine, it shall only be used to specify that the structured document tag is of this type, which shall be used by an application to present the possible list of choices for insertion into the parent structured document tag.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:docPartList> … </w:docPartList> </w:sdtPr> …</w:sdt>

The docPartList element in this structured document tag's properties specifies that the type of structured document tag is a document part gallery. The child elements shall specify the gallery and category filters for this list, if any. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

docPartCategory (Document Part Category Filter)

§2.5.2.10

docPartGallery (Document Part Gallery Filter)

§2.5.2.11

docPartUnique (Built-In Document Part)

§2.5.2.14

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

</sequence>

</complexType>

docPartObj (Built-In Document Part Structured Document Tag)

This element specifies that the parent structured document tag shall be of a document part type.

This element differs from the docPartList element (§2.5.2.12) in that it may be used to semantically tag a set of block-level objects in a WordprocessingML document without requiring the ability to specify a category and gallery of objects which may be swapped with it via the user interface.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:docPartObj> … </w:docPartObj> </w:sdtPr> …</w:sdt>

The docPartObj element in this structured document tag's properties specify that the type of structured document tag is a document part. The child elements shall specify the gallery and category semantics for this part, if any. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

docPartCategory (Document Part Category Filter)

§2.5.2.10

docPartGallery (Document Part Gallery Filter)

§2.5.2.11

docPartUnique (Built-In Document Part)

§2.5.2.14

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

</sequence>

</complexType>

docPartUnique (Built-In Document Part)

This element specifies that this structured document tag is being used to encapsulate a built-in document part (i.e. this element appears as a child element of the docPartObj element).

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:docPartObj> … <w:docPartUnique/> </w:docPartObj> </w:sdtPr> …</w:sdt>

The docPartUnique element in this structured document tag's properties specify that the type of structured document tag is a container for a document part. end example]

Parent Elements

docPartList (§2.5.2.12); docPartObj (§2.5.2.13)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

dropDownList (Drop-Down List Structured Document Tag)

This element specifies that the parent structured document tag shall be a drop-down list when displayed in the document.

This setting specifies that the behavior for this structured document tag shall be as follows:

The contents shall not be editable when displayed by a hosting application regardless of the locking settings

The child elements of this element specify choices which shall be displayed in a standard drop-down list format

As well, the structured document tag must satisfy the following restraints or the document shall be considered invalid:

The contents shall only be contain a single run (one set of formatting properties)

The contents shall not contain more than a single paragraph or table cell and shall not contain a table row or table

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:dropDownList> … </w:dropDownList> </w:sdtPr> …</w:sdt>

The dropDownList element in this structured document tag's properties specify that the type of structured document tag is a drop-down list. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

listItem (Drop-Down List Item)

§2.5.2.21

Attributes

Description

lastValue (Drop-down List Last Saved Value)

Specifies the value associated with the current display text for the drop-down list structured document tag.

When the XML mapping is created, the content in the custom XML data is retrieved

If this content has an associated list item (matching its value attribute), then the corresponding display text shall be displayed in the structured document tag

[Example: Consider a drop-down list structured document tag defined as follows:

<w:sdt> <w:sdtPr> <w:dataBinding … /> <w:dropDownList w:lastValue="2"/> </w:sdtPr> <w:sdtContent> <w:r> <w:t>Hello world</w:t> </w:r> </w:sdtContent></w:sdt>

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

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

</sequence>

</complexType>

equation (Equation Structured Document Tag)

This element specifies that the parent structured document tag shall be of type equation.

This type setting does not require or imply that the contents of the structured document tag shall contain only an equation or associated placeholder text, it shall only be used to specify that the structured document tag is of this type, which may be used by an application as desired.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:equation/> </w:sdtPr> …</w:sdt>

The equation element in this structured document tag's properties specify that the type of structured document tag is equation. end example]

Parent Elements

sdtPr (§2.5.2.37)

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

group (Group Structured Document Tag)

This element specifies that the parent structured document tag shall be a restricted grouping when displayed in the document.

This setting specifies that the behavior for this structured document tag shall be as follows:

The contents of this structured document tag shall not be editable when displayed by a hosting application regardless of the locking settings. This restriction may be superseded by any structured document tag contained within the group, as each structured document tag specifies the locking properties for its own content.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:group/> </w:sdtPr> …</w:sdt>

The group element in this structured document tag's properties specify that the type of structured document tag is a restricted group. end example]

Parent Elements

sdtPr (§2.5.2.37)

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

id (Unique ID)

This element specifies a unique numerical ID for the parent structured document tag. This ID shall be persisted through multiple sessions (i.e. shall not be changed once specified).

If multiple structured document tags specify the same decimal number value for the id attribute, then the first structured document tag in the document shall maintain this original ID, and all subsequent structured document tags shall have new identifiers assigned to them when the document is opened.

If this element is omitted, then the parent structured document tag shall have a new unique identifier assigned to it when the document is opened.

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:id w:val="8775518"/> …</w:sdtPr>

This set of properties specifies via the val attribute on the id element that the ID for the parent structured document shall be 8775518 (subject, of course, to the conflict management and resolution discussed above). end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

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

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

</complexType>

lid (Date Picker Language ID)

This element specifies the language ID which shall be used for displaying a calendar for the current date picker structured document tag, if a user interface is present for the structured document tag.

If this element is omitted, then the language ID shall be the language ID of the run contents of the parent structured document tag.

[Example: Consider the following structured document tag properties:

<w:sdtPr> <w:date w:fullDate="01-01-2006T06:30:00Z"> <w:lid w:val="ja-JP"/> </w:date></w:sdtPr>

The calendar language ID for a calendar which may be displayed in the document shall be the default calendar format for the Japanese (Japan) language format (ja-JP). end example]

Parent Elements

date (§2.5.2.7)

Attributes

Description

val (Language Code)

Specifies an ISO 639-1 letter code or 4 digit hexadecimal code for a specific language.

This code is interpreted in the context of the parent XML element.

[Example: Consider an object which shall specify the English(Canada) language. That object would use the ISO 639-1 letter code of en-CA to specify this language. end example]

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

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

</complexType>

listItem (Combo Box List Item)

This element specifies a single list item within the parent combo box structured document tag. Each list item shall be displayed in the list displayed for the parent structured document tag (if a user interface is present).

[Example: Consider the following combo box structured document tag:

<w:sdt> <w:sdtPr> <w:comboBox> <w:listItem w:displayText="Zero" w:value="0"/> <w:listItem w:displayText="One" w:value="1"/> </w:comboBox> </w:sdtPr> …</w:sdt>

Each listItem element within the comboBox element specifies a single list item entry, in this case resulting in two list items within the parent combo box structured document tag. end example]

Parent Elements

comboBox (§2.5.2.5)

Attributes

Description

displayText (List Entry Display Text)

Specifies the text to display in the run content (as well as any supplied user interface) in place of the value attribute contents for this drop-down list entry.

This value shall be used as follows:

If the parent structured document tag is mapped to a custom XML element, the value in that custom XML element shall be mapped the content of the value attribute, and the resulting displayText attribute value (if one is present) shall be displayed in the run content. If no displayText attribute is present, then the value shall be displayed.

If the corresponding entry is selected via a user interface, this value shall be stored in the parent element's run content in the document (this is the value that shall be shown in the document's WordprocessingML content).

If this attribute is omitted, then the content of the value attribute shall be used as the display text for the current list item entry.

[Example: Consider the following drop-down list structured document tag:

<w:sdt> <w:sdtPr> <w:dropDownList> <w:listItem w:displayText="The Letter A" w:value="a"/> <w:listItem w:displayText="The Letter B" w:value="b"/> </w:dropDownList> </w:sdtPr> …</w:sdt>

The displayText attribute for the first entry is The Letter A and the second is The Letter B, therefore, these values will be used to determine the display text if the parent structured document tag is mapped to custom XML data in a custom XML data part. end example]

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

value (List Entry Value)

Specifies the value for the current list item entry.

This value shall be used as follows:

If the parent structured document tag is mapped to a custom XML element, the value in that custom XML element shall be mapped to this value, and the resulting displayText attribute value (if one is present) shall be displayed in the run content. If no displayText attribute is present, then the value shall be displayed.

If the corresponding entry is selected via a user interface, this value shall be stored in the parent element's listItem attribute value.

[Example: Consider the following combo box structured document tag:

<w:sdt> <w:sdtPr> <w:comboBox> <w:listItem w:displayText="Zero" w:value="0"/> <w:listItem w:displayText="One" w:value="1"/> </w:comboBox> </w:sdtPr> …</w:sdt>

The value attribute for the first entry is 0 and the second is 1, therefore, these values will be used to determine the display text if the parent structured document tag is mapped to custom XML data in a custom XML data part. end example]

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

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

</complexType>

listItem (Drop-Down List Item)

This element specifies a single list item within the parent drop-down list structured document tag. Each list item shall be displayed in the list displayed for the parent structured document tag (if a user interface is present).

[Example: Consider the following combo box structured document tag:

<w:sdt> <w:sdtPr> <w:dropDownList> <w:listItem w:displayText="The Letter A" w:value="a"/> <w:listItem w:displayText="The Letter B" w:value="b"/> </w:dropDownList> </w:sdtPr> …</w:sdt>

Each listItem element within the dropDownList element specifies a single list item entry, in this case resulting in two list items within the parent drop-down list structured document tag. end example]

Parent Elements

dropDownList (§2.5.2.15)

Attributes

Description

displayText (List Entry Display Text)

Specifies the text to display in the run content (as well as any supplied user interface) in place of the value attribute contents for this drop-down list entry.

This value shall be used as follows:

If this attribute is omitted, then the content of the value attribute shall be used as the display text for the current list item entry.

[Example: Consider the following drop-down list structured document tag:

<w:sdt> <w:sdtPr> <w:dropDownList> <w:listItem w:displayText="The Letter A" w:value="a"/> <w:listItem w:displayText="The Letter B" w:value="b"/> </w:dropDownList> </w:sdtPr> …</w:sdt>

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

value (List Entry Value)

Specifies the value for the current list item entry.

This value shall be used as follows:

If the corresponding entry is selected via a user interface, this value shall be stored in the parent element's listItem attribute value.

[Example: Consider the following combo box structured document tag:

<w:sdt> <w:sdtPr> <w:comboBox> <w:listItem w:displayText="Zero" w:value="0"/> <w:listItem w:displayText="One" w:value="1"/> </w:comboBox> </w:sdtPr> …</w:sdt>

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

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

</complexType>

lock (Locking Setting)

This element specifies the set of behaviors which shall be applied to the contents of the parent structured document tag when the contents of this documents are edited by an application (whether through a user interface or directly). The type of locking applied to the structured document tag is specified via the value of the associated val attribute.

If this element is omitted, then the locking settings implied for the structured document tag shall be as follows:

If the structured document tag specifies that it is a group via the group element (§2.5.2.17), then the contents of the structured document tag shall be editable, but the entire tag may be deleted.

For all other types, no locking settings shall be applied to the structured document tag.

[Example: Consider the following plain text structured document tag:

<w:sdt> <w:sdtPr> <w:lock w:val="sdtLocked"/> … <w:text/> </w:sdtPr> …</w:sdt>

This plain text structured document tag's properties contain a lock element, specifying locking behaviors for the structured document tag. Since the locking val attribute value is sdtLocked, this locking setting shall specify that the contents of the structured document tag may be edited, but the structured document tag itself shall not be deleted from the document. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

val (Locking Type)

Specifies the type of locking which shall be applied to the parent structured document tag.

If this attribute is omitted, this its value shall be assumed to be unlocked (using the defaults stated above).

[Example: Consider the following plain text structured document tag properties:

<w:sdtPr> <w:lock w:val="contentLocked"/> … <w:text/></w:sdtPr>

The val attribute value is contentLocked, therefore this locking setting shall specify that the contents of the structured document tag shall not be edited, but the structured document tag itself may be deleted from the document. end example]

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

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

</complexType>

picture (Picture Structured Document Tag)

This element specifies that the parent structured document tag shall be a picture when displayed in the document.

This setting specifies that the behavior for this structured document tag shall be as follows:

The contents shall always be restricted to a single picture using either the DrawingML (§5.1) or VML (§6.1) syntax

As well, the structured document tag must satisfy the following restraints or the document shall be considered invalid:

The contents shall only be a single picture using either the DrawingML (§5.1) or VML (§6.1) syntax

The contents shall not contain more than a single paragraph or table cell and shall not contain a table row or table

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:picture/> </w:sdtPr> …</w:sdt>

The text element in this structured document tag's properties specify that the type of structured document tag is a picture. end example]

Parent Elements

sdtPr (§2.5.2.37)

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

placeholder (Structured Document Tag Placeholder Text)

This element specifies the placeholder text which should be displayed when this structured document tag's run contents are empty, the associated mapped XML element is empty as specified via the dataBinding element (§2.5.2.6) or the showingPlcHdr element (§2.5.2.38) is set in the structured document tag's properties. The placeholder text which shall be shown is itself specified via the child element docPart.

If this element is omitted, then five non-breaking spaces shall be used as the default placeholder text for this structured document tag.

[Example: Consider a structured document tag defined as follows:

<w:sdt> <w:sdtPr> <w:placeholder> <w:docPart w:val="DefaultPlaceholder_22610170" /> </w:placeholder> … </w:sdtPr> <w:sdtContent> … </w:sdtContent></w:sdt>

This structured document tag specifies through the placeholder element that its placeholder text shall be specified in the document part of type bbPlcHdr whose name is equal to DefaultPlaceholder_22610170. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

docPart (Document Part Reference)

§2.5.2.9

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

</sequence>

</complexType>

richText (Rich Text Structured Document Tag)

This element specifies that the parent structured document tag shall be a rich text box when displayed in the document.

If no type element (the xsd:choice block in the XML Schema fragment for the parent sdtPr element) is specified, then the parent structured document tag shall be of type richText.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:richText/> </w:sdtPr> …</w:sdt>

The richText element in this structured document tag's properties specify that the type of structured document tag is a rich text box. end example].

Parent Elements

sdtPr (§2.5.2.37)

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

rPr (Run Properties For Structured Document Tag Contents)

This element specifies the set of run properties which shall be applied to the text entered into the parent structured document tag in replacement of placeholder text. When placeholder text is present in a structured document tag, its formatting is often different than the desired underlying formatting, and this element specifies the formatting which shall be used for non-placeholder text contents when they are initially added to the control.

If this element is not present, the inserted is unformatted, as with any other run of text - it shall not inherit the properties of the placeholder text.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> <w:placeholder> <w:docPart w:val="TestPlaceholderDocPart"/> </w:placeholder> <w:showingPlcHdr/> <w:rPr> <w:rStyle w:val="UserName"/> </w:rPr> … </w:sdtPr> <w:sdtContent> <w:r> <w:rPr> <w:rStyle w:val="PlaceholderText"/> </w:rPr> <w:t>[Type Your Name Here]</w:t> </w:r> </w:sdtContent></w:sdt>

This structured document tag specifies that its current contents are placeholder text via the showingPlcHdr element (§2.5.2.38), and that text has the PlaceholderText character style applied to it.

Now, assume that that style created grey shaded text (typical for placeholder text). This formatting would clearly not be desirable for any text entered into the structured document tag. Therefore, when this text is added, the rPr element in the sdtPr is used to store the formatting on the resulting text.

In this example, the text which initially populates the control shall be formatted with the UserName character style. end example]

Parent Elements

sdtPr (§2.5.2.37)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

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

</sequence>

</complexType>

rPr (Structured Document Tag End Character Run Properties)

This element specifies the set of run properties which shall be applied to the character present to delimit the end of the structured document tag's contents. When these properties are applied, they shall be applied in addition to the run properties specified for the entire structured document tag via the rPr element (§2.5.2.26) stored in the tag's main property container.

If this element is not present, the inserted closing tag shall be formatting identically to the start tag.

[Example: Consider the following structured document tag:

<w:i/> <w:rPr> </w:sdtEndPr> <w:sdtContent> … </w:sdtContent></w:sdt>

The rPr elements under the tag's properties specify that this structured document tag specifies that its start character shall have formatting in the character style UserName, and that the end character shall have the formatting in the character style UserName as well as bold and italic direct formatting. end example]

Parent Elements

sdtEndPr (§2.5.2.36)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

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

</sequence>

</complexType>

sdt (Cell-Level Structured Document Tag)

This element specifies the presence of a structured document tag around a single table cell. The two child elements of this element shall be used to specify the properties and content of the current structured document tag via the sdtPr and sdtContent elements, respectively.

[Example: Consider a structured document tag with the friendly name company that shall be located around a single table cell in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:tr> <w:sdt> <w:sdtPr> <w:alias w:val="company"/> </w:sdtPr> <w:sdtContent> <w:tc> … </w:tc> </w:sdtContent> </w:sdt> …</w:tr>

The sdt element specifies the structured document tag, the child sdtPr element contains the friendly name property set to company, and the sdtContent element contains a single table cell (it is a cell-level structured document tag). end example]

Parent Elements

customXml (§2.5.1.3); sdtContent (§2.5.2.33); tr (§2.4.75)

Child Elements

Subclause

sdtContent (Cell-Level Structured Document Tag Content)

§2.5.2.33

sdtEndPr (Structured Document Tag End Character Properties)

§2.5.2.36

sdtPr (Structured Document Tag Properties)

§2.5.2.37

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

</sequence>

</complexType>

sdt (Inline-Level Structured Document Tag)

This element specifies the presence of a structured document tag around one or more inline-level structures (runs, DrawingML objects, fields, etc.) in the current paragraph. The two child elements of this element shall be used to specify the properties and content of the current structured document tag via the sdtPr and sdtContent elements, respectively.

[Example: Consider a structured document tag with the friendly name firstName that shall be located around two runs in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:p> <w:sdt> <w:sdtPr> <w:alias w:val="firstName"/> </w:sdtPr> <w:sdtContent> <w:r> … </w:r> <w:r> … </w:r> </w:sdtContent> </w:sdt> …</w:tr>

The sdt element specifies the structured document tag, the child sdtPr element contains the friendly name property set to firstName, and the sdtContent element contains two runs (it is an inline-level structured document tag). end example]

Parent Elements

Child Elements

Subclause

sdtContent (Inline-Level Structured Document Tag Content)

§2.5.2.35

sdtEndPr (Structured Document Tag End Character Properties)

§2.5.2.36

sdtPr (Structured Document Tag Properties)

§2.5.2.37

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

</sequence>

</complexType>

sdt (Block-Level Structured Document Tag)

This element specifies the presence of a structured document tag around one or more block-level structures (paragraphs, tables, etc.). The two child elements of this element shall be used to specify the properties and content of the current structured document tag via the sdtPr and sdtContent elements, respectively.

[Example: Consider a structured document tag with the friendly name address that shall be located around a single paragraph in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:body> <w:sdt> <w:sdtPr> <w:alias w:val="address"/> </w:sdtPr> <w:sdtContent> <w:p> … </w:p> </w:sdtContent> </w:sdt> …</w:body>

The sdt element specifies the structured document tag, the child sdtPr element contains the friendly name property set to address, and the sdtContent element contains a single paragraph (it is a block-level structured document tag). end example]

Parent Elements

Child Elements

Subclause

sdtContent (Block-Level Structured Document Tag Content)

§2.5.2.32

sdtEndPr (Structured Document Tag End Character Properties)

§2.5.2.36

sdtPr (Structured Document Tag Properties)

§2.5.2.37

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

</sequence>

</complexType>

sdt (Row-Level Structured Document Tag)

This element specifies the presence of a structured document tag around a single table row. The two child elements of this element shall be used to specify the properties and content of the current structured document tag via the sdtPr and sdtContent elements, respectively.

[Example: Consider a structured document tag with the friendly name invoiceItem that shall be located around a single table row in a WordprocessingML document. This requirement would be specified as follows in the WordprocessingML:

<w:tbl> <w:sdt> <w:sdtPr> <w:alias w:val="invoiceItem"/> </w:sdtPr> <w:sdtContent> <w:tr> … </w:tr> </w:sdtContent> </w:sdt> …</w:tbl>

The sdt element specifies the structured document tag, the child sdtPr element contains the friendly name property set to invoiceItem, and the sdtContent element contains a single table row (it is a row-level structured document tag). end example]

Parent Elements

customXml (§2.5.1.4); sdtContent (§2.5.2.34); tbl (§2.4.36)

Child Elements

Subclause

sdtContent (Row-Level Structured Document Tag Content)

§2.5.2.34

sdtEndPr (Structured Document Tag End Character Properties)

§2.5.2.36

sdtPr (Structured Document Tag Properties)

§2.5.2.37

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

</sequence>

</complexType>

sdtContent (Block-Level Structured Document Tag Content)

This element specifies the last known contents of a structured document tag around one or more block-level structures (paragraphs, tables, etc.). This element's contents shall be treated as a cache of the contents to be displayed in the structured document tag for the following reasons:

If the structured document tag specifies an XML mapping via the dataBinding element (§2.5.2.6), changes to the custom XML data part shall be reflected in the structured document tag as needed

If the contents of the structured document tag are placeholder text via the showingPlcHdr element (§2.5.2.38), then this content may be updated with the placeholder text stored in the Glossary Document part

<w:body> <w:sdt> <w:sdtPr> <w:alias w:val="address"/> </w:sdtPr> <w:sdtContent> <w:p> … </w:p> </w:sdtContent> </w:sdt> …</w:body>

The sdtContent element contains a single paragraph (it is a block-level structured document tag content container). end example]

Parent Elements

sdt (§2.5.2.30)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

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

</complexType>

sdtContent (Cell-Level Structured Document Tag Content)

This element specifies the last known contents of a structured document tag around a single table cell. This element's contents shall be treated as a cache of the contents to be displayed in the structured document tag for the following reasons:

If the structured document tag specifies an XML mapping via the dataBinding element (§2.5.2.6), changes to the custom XML data part shall be reflected in the structured document tag as needed

<w:tr> <w:sdt> <w:sdtPr> <w:alias w:val="company"/> </w:sdtPr> <w:sdtContent> <w:tc> … </w:tc> </w:sdtContent> </w:sdt> …</w:tr>

The sdtContent element contains a single table cell (it is an cell-level structured document tag content container). end example]

Parent Elements

sdt (§2.5.2.28)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Cell-Level Custom XML Element)

§2.5.1.3

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Cell-Level Structured Document Tag)

§2.5.2.28

tc (Table Cell)

§2.4.62

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

</complexType>

sdtContent (Row-Level Structured Document Tag Content)

This element specifies the last known contents of a structured document tag around a single table row.

[Note: Unlike other types of structured document tags, this type cannot show placeholder text or have mapped XML data, therefore it is never a cache. end note]

<w:tbl> <w:sdt> <w:sdtPr> <w:alias w:val="invoiceItem"/> </w:sdtPr> <w:sdtContent> <w:tr> … </w:tr> </w:sdtContent> </w:sdt> …</w:tbl>

The sdtContent element contains a single table row (it is an row-level structured document tag content container). end example]

Parent Elements

sdt (§2.5.2.31)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Row-Level Custom XML Element)

§2.5.1.4

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Row-Level Structured Document Tag)

§2.5.2.31

tr (Table Row)

§2.4.75

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

</complexType>

sdtContent (Inline-Level Structured Document Tag Content)

This element specifies the last known contents of a structured document tag around one or more inline-level structures (runs, DrawingML objects, fields, etc.). This element's contents shall be treated as a cache of the contents to be displayed in the structured document tag for the following reasons:

If the structured document tag specifies an XML mapping via the dataBinding element (§2.5.2.6), changes to the custom XML data part shall be reflected in the structured document tag as needed

<w:p> <w:sdt> <w:sdtPr> <w:alias w:val="firstName"/> </w:sdtPr> <w:sdtContent> <w:r> … </w:r> <w:r> … </w:r> </w:sdtContent> </w:sdt> …</w:p>

The sdtContent element contains two adjacent runs (it is an inline-level structured document tag content container). end example]

Parent Elements

sdt (§2.5.2.29)

Child Elements

Subclause

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

fldSimple (Simple Field)

§2.16.21

hyperlink (Hyperlink)

§2.16.24

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

subDoc (Anchor for Subdocument Location)

§2.17.2.1

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

</complexType>

sdtEndPr (Structured Document Tag End Character Properties)

This element specifies the properties which shall be applied to the physical character which delimits the end of a structured document tag.

[Example: Consider a structured document tag with the following properties specified for the end tag:

<w:sdtEndPr> <w:rPr> … </w:rPr></w:sdtEndPr>

This structured document tag specifies properties for its end character within the sdtEndPr element. end example]

Parent Elements

sdt (§2.5.2.30); sdt (§2.5.2.28); sdt (§2.5.2.29); sdt (§2.5.2.31)

Child Elements

Subclause

rPr (Structured Document Tag End Character Run Properties)

§2.5.2.27

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

</choice>

</complexType>

sdtPr (Structured Document Tag Properties)

This element specifies the set of properties which shall be applied to the parent structured document tag.

[Example: Consider a structured document tag with the following properties specified:

<w:sdtPr> <w:alias w:val="Birthday"/> <w:id w:val="8775518"/> <w:date> <w:dateFormat w:val="M/d/yyyy"/> <w:lid w:val="EN-US"/> </w:date></w:sdtPr>

This structured document tag specifies three properties: the a friendly name of Birthday via the alias element (§2.5.2.1), a unique ID of 8775518 via the id element (§2.5.2.18), and a structured document tag type of date picker via the date element (§2.5.2.7) which itself has a set of date-specific properties. end example]

Parent Elements

sdt (§2.5.2.29); sdt (§2.5.2.30); sdt (§2.5.2.28); sdt (§2.5.2.31)

Child Elements

Subclause

alias (Friendly Name)

§2.5.2.1

bibliography (Bibliography Structured Document Tag)

§2.5.2.2

citation (Citation Structured Document Tag)

§2.5.2.4

comboBox (Combo Box Structured Document Tag)

§2.5.2.5

dataBinding (XML Mapping)

§2.5.2.6

date (Date Structured Document Tag)

§2.5.2.7

docPartList (Document Part Gallery Structured Document Tag)

§2.5.2.12

docPartObj (Built-In Document Part Structured Document Tag)

§2.5.2.13

dropDownList (Drop-Down List Structured Document Tag)

§2.5.2.15

equation (Equation Structured Document Tag)

§2.5.2.16

group (Group Structured Document Tag)

§2.5.2.17

id (Unique ID)

§2.5.2.18

lock (Locking Setting)

§2.5.2.22

picture (Picture Structured Document Tag)

§2.5.2.23

placeholder (Structured Document Tag Placeholder Text)

§2.5.2.24

richText (Rich Text Structured Document Tag)

§2.5.2.25

rPr (Run Properties For Structured Document Tag Contents)

§2.5.2.26

showingPlcHdr (Current Contents Are Placeholder Text)

§2.5.2.38

tag (Programmatic Tag)

§2.5.2.40

temporary (Remove Structured Document Tag When Contents Are Edited)

§2.5.2.41

text (Plain Text Structured Document Tag)

§2.5.2.42

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

</choice>

</complexType>

showingPlcHdr (Current Contents Are Placeholder Text)

This element specifies whether the content of the sdtContent element (§2.5.2.32; §2.5.2.33; §2.5.2.34; §2.5.2.35) for the parent structured document tag shall be interpreted to contain placeholder text for this structured document tag (as opposed to regular text contents within the structured document tag). If this element is present and set to true, this state shall be resumed (showing placeholder text) upon opening this document.

If this element is omitted, then the structured document tag shall not be interpreted to be showing placeholder text when the document is displayed.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> <w:showingPlcHdr/> … <w:richText/> </w:sdtPr> <w:sdtContent> <w:r> <w:t>[Type your name here]</w:t> </w:r> </w:sdtContent></w:sdt>

This structured document tag has run contents which read [Type your name here], which would typically be interpreted as the current contents of the structured document tag. However, since the showingPlcHdr element has been specified in the structured document tag's properties, this content shall instead be interpreted as the placeholder text for the structured document tag. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

storeMappedDataAs (Custom XML Data Date Storage Format)

This element specifies the translation which shall be performed on the displayed date in a date picker structured document tag when the current contents are saved into the associated custom XML data via the dataBinding element (§2.5.2.6).

If this element is omitted, then the value of the associated custom XML element shall be placed into the custom XML data part with no translation.

[Example: Consider the following date picker structured document tag:

<w:sdt> <w:sdtPr> <w:date w:fullDate="01-01-2006T06:30:00Z"> <w:storeMappedDateAs w:val="text"/> … </w:date> </w:sdtPr> <w:sdtContent> <w:r> <w:t>January 1</w:t> </w:r> </w:sdtContent></w:sdt>

The value of the storeMappedDateAs element's attribute value is text, therefore the current run contents shall be sent to the mapped XML element without any translation (in this case, the value shall be January 1). end example]

Parent Elements

date (§2.5.2.7)

Attributes

Description

val (Date Storage Type)

Specifies the type of date translation which shall be applied to the parent date picker structured document tag.

If this attribute is omitted, this its value shall be assumed to be text.

[Example: Consider the following date picker structured document tag:

<w:sdt> <w:sdtPr> <w:date … > <w:storeMappedDateAs w:val="date"/> … </w:date> </w:sdtPr> <w:sdtContent> <w:r> <w:t>January 1</w:t> </w:r> </w:sdtContent></w:sdt>

The value of the val attribute is text, therefore the current run contents shall be sent to the mapped XML element after being translated into xsd:date format (in this case, the value shall be 01-01-2006). end example]

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

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

</complexType>

tag (Programmatic Tag)

This element specifies a programmatic tag associated with the current structured document tag. A programmatic tag is an arbitrary string which applications may associate with a structured document tag in order to identify it without providing a visible friendly name. The string representing the programmatic tag shall be stored on this element's val attribute.

If this element is omitted, then no programmatic tag shall be associated with the given structured document tag.

[Example: Consider the following properties on a structured document tag:

<w:sdtPr> <w:tag w:val="Clause_3246"/> …</w:sdtPr>

This set of properties specifies via the tag element that the programmatic tag for the parent structured document tag shall be Clause_3246. This information may then be used as needed by applications. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

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

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

</complexType>

temporary (Remove Structured Document Tag When Contents Are Edited)

This element specifies whether the parent structured document tag shall be removed from the WordprocessingML document when the its contents are modified.

[Note: This setting is primarily intended for creating structured document tags whose sole purpose is one-time placeholder text, and which should not return once replaced with content. end note]

If this element is omitted, then the parent structured document tag shall not be automatically removed when its contents are modified.

[Example: Consider the following plain text structured document tag:

<w:sdt> <w:sdtPr> <w:temporary/> <w:text/> </w:sdtPr> …</w:sdt>

This plain text structured document tag's properties contain a temporary element, specifying that the structured document tag itself shall be deleted from the document whenever its contents are first modified. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

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

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

</complexType>

text (Plain Text Structured Document Tag)

This element specifies that the parent structured document tag shall be a plain text box when displayed in the document.

This setting specifies that the behavior for this structured document tag shall be as follows:

Formatting applied to any part of this structured document tag's contents shall apply to its entire contents

As well, the structured document tag must satisfy the following restraints or the document shall be considered invalid:

The contents shall only be contain a single run (one set of formatting properties) with exceptions for soft carriage returns via the multiLine attribute on this element

The contents shall not contain more than a single paragraph or table cell and shall not contain a table row or table

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:text/> </w:sdtPr> …</w:sdt>

The text element in this structured document tag's properties specify that the type of structured document tag is a plain text box. end example]

Parent Elements

sdtPr (§2.5.2.37)

Attributes

Description

multiLine (Allow Soft Line Breaks)

Specifies whether soft line breaks may be added to the contents of this structured document tag when this document is modified. This setting shall not affect the ability of the structured document tag to display existing soft line breaks (which shall be preserved) and shall only affect the ability to add line breaks when the document is modified by an application.

If this attribute is omitted, then the parent plain text structured document control shall not allow soft line breaks to be added to its contents.

[Example: Consider the following structured document tag:

<w:sdt> <w:sdtPr> … <w:text w:multiLine="true"/> </w:sdtPr> …</w:sdt>

The multiLine attribute on the text element in this structured document tag's properties specify that an application may allow soft line breaks to be added to the run contents of the structured document tag. end example]

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

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

</complexType>

Sections

WordprocessingML does not natively store the concept of pages, since it is based on paragraphs and runs (which are laid out on to pages by consumers of this content). However, although there is no concept of storing pages in the WordprocessingML format, it is often necessary to store information about a page or group of pages in a document, in order to store information that is to be used to format the pages on which a set of paragraphs will appear. In WordprocessingML, this information is stored via the use of sections.

In WordprocessingML, sections are groupings of paragraphs that have a specific set of properties used to define the pages on which the text will appear, as well as other section-level (applying to all paragraphs' appearance) properties.

[Example: Consider a document with four paragraphs of text that is to be printed on a page in landscape mode, followed by ten paragraphs of text that are to be printed in portrait mode. This requirement implies information about the page(s) used to lay out each grouping of text—the first four paragraphs could require one page, or ten.

Therefore, rather than try to cache knowledge of the number of pages and their properties (which is likely to become invalid if the XML is manipulated by a producer that does not understand page layout), this information is stored by breaking the document into two sections, as follows:

<w:p> …</w:p>

<w:p> <w:sectPr> … (section one properties go here) <w:pgSz ... w:orient="landscape" /> … </w:sectPr> …</w:p>

…

<w:p> <w:sectPr> … (section two properties go here) <w:pgSz ... w:orient="landscape" /> … </w:sectPr> …</w:p>

end example]

bidi (Right to Left Section Layout)

This element specifies that this section shall be presented using a right-to-left page direction. This property only affects section-level properties, and does not affect the layout of text within the contents of this section.

[Example: Consider a section with the bidi property set as follows:

<w:sectPr>

...

<w:bidi/>

</w:sectPr>

This section direction is now right-to-left, which means that all section level properties are displayed right-to-left (e.g., page numbers are displayed on the right of text; columns are populated from right-to-left). However, the layout of text is determined by properties applied at the text level. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

bottom (Bottom Border)

This element specifies the presentation and display of the page border displayed at the bottom of each page in this section.

[Example: Consider a section in which all pages shall have a bottom border consisting of a repeated image of an apple, like this:

This border would result in the following WordprocessingML:

<w:sectPr> … <w:pgBorders> <w:bottom w:val="apples" .../> </w:pgBorders> …</w:sectPr>

Because the page only has a border at the bottom, only the bottom element is specified within the set of page borders. end example]

When a document has a bottom border that is relative to the page edges (using the offsetFrom attribute on pgBorders), it shall span the bottom edge of the page at the location defined by its properties, stopping when:

It intersects with the corresponding left or right page border (if one is specified).

It reaches the edge of the page.

[Example: In the example above, no left or right border was specified in the WordprocessingML, so a consumer shall draw the border from one edge of the page to the other. end example]

When a document has a bottom border that is relative to the text (using the offsetFrom attribute on pgBorders), it shall span only the necessary width to satisfy the requirement of spanning the width of the text.

Parent Elements

pgBorders (§2.6.10)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

The possible values for this attribute are defined by the ST_HexColor simple type (§2.18.43).

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

The possible values for this attribute are defined by the ST_PointMeasure simple type (§2.18.75).

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

The possible values for this attribute are defined by the ST_EighthPointMeasure simple type (§2.18.27).

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

The possible values for this attribute are defined by the ST_ThemeColor simple type (§2.18.104).

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

The possible values for this attribute are defined by the ST_Border simple type (§2.18.4).

The following XML Schema fragment defines the contents of this element:

</complexType>

col (Single Column Definition)

This element specifies the properties for a single column of text within this section.

[Example: Consider a single column with a width of two inches, which also has a one-inch space after the column, resulting in the following WordprocessingML:

<w:cols … > <w:col w:w="2880" w:space="1440"/>

…</w:cols>

The resulting column specifies its width of 2,880 twentieths of a point and space following of 1,440 twentieths of a point. end example]

The contents of the col element are only used to calculate the number and size of columns if the fixedWidth attribute is set to false or omitted.

Parent Elements

cols (§2.6.4)

Attributes

Description

space (Space Before Following Column)

Specifies the spacing (in twentieths of a point) between the current column and the next column.

[Example: Consider a text column that is to have a one-inch space after it. This text column spacing would therefore be 1x72=144 points wide, which translates to 1,440 twentieths of a point. The resulting WordprocessingML specifies that spacing width in twentieths of a point:

<w:col … w:space="1440"/>

end example]

For the last text column in the section, no spacing is allowed after the column, and, if present, any space value is ignored.

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

w (Column Width)

Specifies the width (in twentieths of a point) of this text column.

[Example: Consider a text column, which is to be two inches wide. This text column would therefore be 2x72=144 points wide, which translates to 2,880 twentieths of a point. The resulting WordprocessingML specifies that column width in twentieths of a point:

<w:col … w:w="2880"/>

end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

The following XML Schema fragment defines the contents of this element:

</complexType>

cols (Column Definitions)

This element specifies the set of columns defined for this section in the document.

[Example: Consider a document in which a section defines two columns of 4.16" and 1.83", respectively, resulting in the following WordprocessingML:

<w:cols w:equalWidth="0"> <w:col w:w="2640" w:space="720"/> <w:col w:w="6000"/></w:cols>

The cols element defines the set of columns defined for this section, which because equalWidth is 0, are defined by the number of col elements contained in the column definition. In this case, the first column is 2,640 twentieths of a point wide (as 2640/1440ths of an inch equals 1.83 inches) with one-half of an inch space after, and the second column is 6,000 twentieths of a point wide (4.16 inches). end example]

Based on the presence of the equalWidth attribute, a consumer shall render the columns using:

If equalWidth is true, then the columns are defined using the data stored as attributes of the cols element (defined below).

If equalWidth is false, then the columns are defined using the presence and data on each child col element (§2.6.3).

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Child Elements

Subclause

col (Single Column Definition)

§2.6.3

Attributes

Description

equalWidth (Equal Column Widths)

Specifies whether all text columns in the current section are of equal width.

If this attribute is present and its value is set to true, on, or 1, then all columns for this text section are of an equal width and are calculated as follows:

Take width of page (from margin to margin)

Divide by number of columns specified in num attribute

For each column, leave space after as defined in the space attribute

Remaining width of each column is the text column width.

If this attribute is present and its value is set to false, off, or 0, then all columns for this text section are of different widths and are defined by each col element as follows:

Each col element defines a single column

Each w attribute defines the text column width

Each space attribute defines the space after the text column

[Example: Consider a section with column information defined as follows:

<w:cols w:num="3" w:space="1440" w:equalWidth="1"> <w:col w:w="2880" w:space="2880" /> <w:col w:w="2880" w:space="1440" /> <w:col w:w="2880" /></w:cols>

This set of columns has a equalWidth value set to 1, therefore the col elements are ignored, and there are three equally sized columns (num value of 3), each with one inch (space value of 1440 twentieths of a point) of space after. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

num (Number of Equal Width Columns)

Specifies the number of text columns in the current section.

If all columns are not of equal width (the equalWidth attribute is not set), then this element is ignored, and the number of columns is defined by the number of col elements defined under the cols element.

[Example: Consider a section with column information defined as follows:

<w:cols w:num="3" w:space="1440" w:equalWidth="1"> …</w:cols>

This set of columns has a equalWidth value set to 1, therefore there are three equally sized columns, as the num attribute has a value of 3. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

sep (Draw Line Between Columns)

Specifies if a vertical line is drawn between each of the text columns in this section.

If set to true, on, or 1, then a vertical line shall be drawn in the center of the spacing between each column in this section.

[Example: Consider a section with column information defined as follows:

<w:cols w:sep="1"> …</w:cols>

This set of columns has a sep value set to 1, therefore there shall be a vertical line separating each column in this section. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

space (Spacing Between Equal Width Columns)

Specifies the spacing between text columns in the current section.

If all columns are not of equal width (the equalWidth attribute is not set), then this element is ignored, and the spacing after columns is defined by the space attribute on each of the col elements defined under the cols element.

[Example: Consider a section with column information defined as follows:

<w:cols w:num="3" w:space="1440" w:equalWidth="1"> …</w:cols>

This set of columns has a equalWidth value set to 1, therefore there are three equally sized columns, each with one inch (space value of 1440 twentieths of a point) of space after. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

docGrid (Document Grid)

This element specifies the settings for the document grid, which enables precise layout of full-width East Asian language characters within a document by specifying the desired number of characters per line and lines per page for all East Asian text content in this section.

[Example: Consider a document with the document grid defined to allow 20 characters per line, and 20 lines per page by snapping characters to the grid (type attribute of snapToChars) as follows:

As shown, this document allows for only 20 East Asian characters per line by adjusting the inter-character spacing to ensure that there are only 20 characters per line. end example]

If Latin text is interspersed on this line, then it is placed across the number of grid units needed to fit the content, but all other grid positions are unaffected.

[Example: Consider the example above with the addition of the text "Latin text" in English, as follows:

The Latin text spans two grid units, so it is placed in the center of those two units; no other grid positions are affected, so the text on the second line now spans two additional grid units. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

charSpace (Document Grid Character Pitch)

Specifies the number of characters to be allowed on the document grid for each line in this section.

This attribute's value shall be specified by multiplying the difference between the desired character pitch and the character pitch for that character in the font size of the Normal font by 4096.

This value shall then be used to add the character pitch for the specified point size to each character in the section [Note: This results in text in the Normal style having a specific number of characters per line. end note]

[Example: Consider a section with a Normal font size of 11 points on which a 21 point pitch document grid has been defined.. The resulting WordprocessingML would be defined as follows:

<w:docGrid w:charSize="40960" …/>

The charSpace attribute specifies a value of 40960, which means that the delta between the character pitch of each character in the grid and the Normal font is 10 points, resulting in a character pitch of 11+10 = 21 points for all characters in this section. end example]

Individual runs of text can override the line pitch information specified for the document grid by specifying that the run text shall not snap to the document grid via the snapToGrid element (§2.3.2.32).

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

linePitch (Document Grid Line Pitch)

Specifies the number of lines to be allowed on the document grid for the current page assuming all lines have equal line pitch applied to them. This line pitch shall not be added to any line which appears within a table cell unless the adjustLineHeightInTable element (§2.15.3.1) is present in the document's compatibility settings.

This attribute is specified in twentieths of a point, and defines the pitch for each line of text on this page such that the desired number of single spaced lines of text fits on the current page.

[Example: Consider a standard 8.5x11" page on which a 20 character wide, 20 line document grid has been defined. The resulting WordprocessingML would be defined as follows:

<w:docGrid w:linePitch="684" …/>

The linePitch attribute specifies that 34.2 points is to the amount of pitch allowed for each line on this page in order to maintain the specific document grid. end example]

Individual paragraphs can override the line pitch information specified for the document grid by either:

Specifying an exact line spacing value using the lineRule attribute of value exact on the spacing element (§2.3.1.33).

Specifying that the paragraph text shall not snap to the document grid via the snapToGrid element (§2.3.1.32).

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

type (Document Grid Type)

Specifies the type of the current document grid, which defines the grid behavior.

The grid can define a grid which snaps all East Asian characters to grid positions, but leaves Latin text with its default spacing; a grid which adds the specified character pitch to each character on each row; or a grid which affects only the line pitch for the current section.

[Example: Consider the document discussed above with the document grid defined to allow 20 characters per line, and 20 lines per page by snapping characters to the grid as follows:

This document has a type attribute of snapToChars, which specifies that the grid shall force East Asian characters to fit 20 to a line. end example]

The possible values for this attribute are defined by the ST_DocGrid simple type (§2.18.18).

The following XML Schema fragment defines the contents of this element:

</complexType>

formProt (Only Allow Editing of Form Fields)

This element specifies that the contents of the current section shall be protected such that they cannot be edited by a user (if the consumer is displaying the document and allowing the user to make modification) except for the text contained in any form field or embedded control that is part of the current section.

[Example: Consider a section consisting of three paragraphs of text and a single text form field, located at the beginning of the second paragraph. If this section is protected in this manner, a user would only be permitted to edit the contents of the text form field, and all other contents would be locked to prevent user edits. end example]

The enforcement of this property is determined by the documentProtection element (§2.15.1.28), as it is possible to specify protection without turning it on.

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

left (Left Border)

This element specifies the presentation and display of the page border displayed at the left of each page in this section.

[Example: Consider a section in which all pages have a left border consisting of a repeated image of an umbrella, like this:

This border would result in the following WordprocessingML:

<w:sectPr> … <w:pgBorders> <w:left w:val="seattle" …/> </w:pgBorders> …</w:sectPr>

Because the page only has a border at the left, only the left element is specified within the set of page borders. end example]

When a document has a left border that is relative to the page edges (using the offsetFrom attribute value of page on pgBorders), it shall span the left edge of the page at the location defined by its properties, stopping when:

It intersects with the corresponding top or bottom page border (if one is specified).

It reaches the edge of the page.

[Example: In the example above, no top or bottom border was specified in the WordprocessingML, so a consumer shall draw the border from one edge of the page to the other. end example]

When a document has a left border that is relative to the text (using the offsetFrom attribute value of text on pgBorders), it shall span only the necessary width to satisfy the requirement of spanning the width of the text.

Parent Elements

pgBorders (§2.6.10)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

The possible values for this attribute are defined by the ST_HexColor simple type (§2.18.43).

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

The possible values for this attribute are defined by the ST_PointMeasure simple type (§2.18.75).

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

The possible values for this attribute are defined by the ST_EighthPointMeasure simple type (§2.18.27).

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

The possible values for this attribute are defined by the ST_ThemeColor simple type (§2.18.104).

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

The possible values for this attribute are defined by the ST_Border simple type (§2.18.4).

The following XML Schema fragment defines the contents of this element:

</complexType>

lnNumType (Line Numbering Settings)

This element specifies the settings for line numbering to be displayed before each column of text in this section in the document.

[Example: Consider the line numbering used on each page of this document, which specifies: line numbering for each line, restarting at one at the top of each new page. This line-numbering scheme would be defined using the following WordprocessingML:

<w:sectPr> … <w:lnNumType w:countBy="1" /></w:sectPr>

This content specifies that line numbers shall be included on each line, restart on each page (the default), be placed automatically based on the text (the default), and shall restart at one (the default). end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

countBy (Line Number Increments to Display)

Specifies the line number increments to be displayed in the current document.

Although each line has an associated line number, only lines which are an even multiple of this value shall be displayed.

[Example: Consider a document in which only every fifth line shall have a line number. The resulting WordprocessingML for this setting would be:

<w:lnNumType … w:countBy="5"/>

This setting ensures that only lines whose number is a multiple of (e.g. 5, 10, and 15) will have a line number displayed. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

distance (Distance Between Text and Line Numbering)

Specifies the distance between the text margin and the edge of any line numbers appearing in that section.

[Example: Consider a document in which the line numbering shall appear one-half inch from the text margin. The WordprocessingML for this setting is:

<w:lnNumType … w:distance="720"/>

The distance attribute specifies that there shall be a 720 twip spacing between the text margin and the line numbering. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

restart (Line Numbering Restart Setting)

Specifies when the line numbering in this section shall be reset to the line number specified by the start attribute's value.

The line numbering increments for each line (even if it is not displayed) until it reaches the restart point specified by this element.

[Example: Consider the line numbering used on each page of this document, which specifies that line numbering shall restart at the top of each new page. This line numbering setting would be defined using the following WordprocessingML:

<w:sectPr> … <w:lnNumType w:restart="newPage" ... /></w:sectPr>

The value of newPage specifies that the line numbers shall restart at the top of each page to the value specified by the start attribute. In this case, newPage is the default, so this value could have been omitted entirely. end example]

The possible values for this attribute are defined by the ST_LineNumberRestart simple type (§2.18.54).

start (Line Numbering Starting Value)

Specifies the starting value used for the first line whenever the line numbering is restarted by use of the restart attribute.

[Example: Consider a document in which line numbering shall appear on every fifth line, but the first line shall be treated as line number . This setting would require the following WordprocessingML syntax:

<w:lnNumType w:start="3" w:countBy="5"/>

The start attribute specifies that line numbers shall be counted starting from the number 3. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

paperSrc (Paper Source Information)

This element specifies printer-specific settings for the printer tray(s) that shall be used to print different pages in this section in the document.

[Example: Consider a section which shall use the best possible tray when printing all pages in this section. This information is specified using the following WordprocessingML:

<w:paperSrc w:first="1" w:other="1" />

The attributes on the paperSrc element specify the printer codes for the trays to be used when printing this section. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

first (First Page Printer Tray Code)

Specifies a printer-specific code that uniquely identifies a specific printer tray to be used to print the first page of this section in the document.

A first value of 1 (the default) is specifically used to indicate that the printer shall automatically select the appropriate printer tray based on the printed page size.

[Example: Consider a section which shall use the best possible tray when printing the first page in this section. This information is specified using the following WordprocessingML:

<w:paperSrc w:first="1" w:other="1" />

The first attribute on the paperSrc element specifies that the printer shall automatically select the appropriate printer tray based on the printed page size when printing the first page in this section. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

other (Non-First Page Printer Tray Code)

Specifies a printer-specific code that uniquely identifies a specific printer tray to be used to print the each subsequent (non-first) page of this section in the document.

An value of 1 (the default) is specifically used to indicate that the printer shall automatically select the appropriate printer tray based on the printed page size.

[Example: Consider a section which shall use the best possible tray when printing the all pages in this section. This information is specified using the following WordprocessingML:

<w:paperSrc w:first="1" w:other="1" />

The other attribute on the paperSrc element specifies that the printer shall automatically select the appropriate printer tray based on the printed page size when printing all pages after the first in this section. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

pgBorders (Page Borders)

This element specifies the page borders for each page in this section. Each child element of the pgBorders element specifies a specific of border (left, right, bottom, or top).

[Example: Consider a page that specifies a dashed line border around each of the four sides of the page, as follows:

This page border setting would be specified using the following WordprocessingML:

<w:pgBorders w:offsetFrom="page"> <w:top w:val="dashed" w:sz="4" w:space="24" w:color="auto" /> <w:left w:val="dashed" w:sz="4" w:space="24" w:color="auto" /> <w:bottom w:val="dashed" w:sz="4" w:space="24" w:color="auto" /> <w:right w:val="dashed" w:sz="4" w:space="24" w:color="auto" /> </w:pgBorders>

The four page borders are each uniquely defined by the top, left, bottom, and right elements, respectively. Global settings that define the placement of all page borders are stored on the pgBorders element directly. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Child Elements

Subclause

bottom (Bottom Border)

§2.6.2

left (Left Border)

§2.6.7

right (Right Border)

§2.6.15

top (Top Border)

§2.6.21

Attributes

Description

display (Pages to Display Page Borders)

Specifies the pages in this section on which the page border shall be printed.

If this attribute is omitted, then the page borders shall be displayed on all pages in this section (equivalent to a value of allPages).

[Example: Consider a section in a document for which the page border shall only be printed on the first page. This setting is specified using the following WordprocessingML:

<w:pgBorders w:display="firstPage"> …</w:pgBorders>

The display attribute specifies that only the first page shall display the page border defined for this section. end example]

The possible values for this attribute are defined by the ST_PageBorderDisplay simple type (§2.18.68).

offsetFrom (Page Border Positioning)

Specifies how the relative positioning of the page borders shall be calculated.

If the value of this attribute is page, then the space attribute on each page border shall be interpreted as the distance from the edge of the page that shall be left before the page border.

If the value of this attribute is text, then the space attribute on each page border shall be interpreted as the distance from the text margins that shall be left before the page border.

[Example: Consider the following WordprocessingML fragment:

<w:pgBorders w:offsetFrom="page"> <w:top w:val="dashed" w:space="24" /> <w:left w:val="dashed" w:space="24" /> <w:bottom w:val="dashed" w:space="24"/> <w:right w:val="dashed" w:space="24"/></w:pgBorders>

This fragment specifies that the page borders shall be indented 24 points from the page extents.

This is distinct from the following fragment with identical space attribute values:

<w:pgBorders w:offsetFrom="text"> <w:top w:val="dashed" w:space="24" /> <w:left w:val="dashed" w:space="24" /> <w:bottom w:val="dashed" w:space="24"/> <w:right w:val="dashed" w:space="24"/></w:pgBorders>

In this case, the page borders will be offset by 24 points, but in this case, that offset will be calculated relative to the text margins. end example]

The possible values for this attribute are defined by the ST_PageBorderOffset simple type (§2.18.69).

zOrder (Z-Ordering of Page Border)

Specifies whether the page border is positioned above or below intersecting texts and objects in this document.

[Example: Consider a document in which the page border shall be displayed below any intersecting text as follows:

This setting is specified by setting the zOrder attribute to back, which specifies that the page border shall be display behind all intersecting text and objects. end example]

The possible values for this attribute are defined by the ST_PageBorderZOrder simple type (§2.18.70).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

pgMar (Page Margins)

This element specifies the page margins for all pages in this section.

[Example: Consider a page with a one-inch margin on all sides. Specifying these margins requires the following WordprocessingML:

<w:sectPr> <w:pgMar w:bottom="1440" w:top="1440" w:right="1440" w:left="1440"/> …</w:sectPr>

This section specifies page margins of 1,440 twentieths of a point (one inch) on all sides. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

bottom (Page Bottom Spacing)

Specifies the distance (in twentieths of a point) between the bottom of the text margins for the main document and the bottom of the page for all pages in this section.

If the value of bottom is non-negative, then the text will be placed at the greater of:

The value of bottom

The extent of the footer text

[Example: Consider a document where the footer shall start one inch of the bottom of the page extent, but the contents of the main document story specify that they shall start one-half of an inchh from the page extents. To specify these boundaries, the following page margins may specified in the WordprocessingML:

<w:pgMar ... w:bottom="720" w:footer="1440"/>

This fragment specifies that the footer shall start 1440 twentieths of a point from the bottom of the page, but the main document story shall start 720 twentieths of a point from the bottom of the page. Since the footer extent is guaranteed to be greater in this case, the bottom text extent ends at the top of the footer region. end example]

A negative value indicates that the contents of the main document shall be measured from the bottom of the page extent regardless of the footer for that document, and therefore shall overlap the footer text.

[Example: Consider a document where the footer shall start one inch of the bottom of the page extent, but the contents of the main document story shall start one-half of an inch from the page extents. To specify these boundaries, the following page margins may specified in the WordprocessingML:

<w:pgMar ... w:bottom="-720" w:footer="1440"/>

This fragment specifies that the footer shall start 1440 twentieths of a point from the bottom of the page, and the main document story shall start 720 twentieths of a point from the bottom of the page. Since the value of bottom is negative in this case, the bottom text extent starts one-half of an inch from the bottom of the page and overlaps any footer text. end example]

The possible values for this attribute are defined by the ST_SignedTwipsMeasure simple type (§2.18.88).

footer (Spacing to Bottom of Footer)

Specifies the distance (in twentieths of a point) from the bottom edge of the page to the bottom edge of the footer.

[Example: Consider a document where the footer shall start one inch above the bottom of the page extent.

To specify this boundary, the following page margins must specified in the WordprocessingML:

<w:pgMar … w:footer="1440"/>

This fragment specifies that the footer shall start 1440 twentieths of a point from the bottom of the page. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

gutter (Page Gutter Spacing)

Specifies the page gutter for each page in the current section.

The page gutter defines the amount of extra space added to the specified margin, above any existing margin values. [Note: This setting is typically used when a document is being created for binding, in order to ensure that the resulting margins are present after the binding gutter is consumed by the printed matter binding. end note]

[Example: Consider a document where the margin shall start one inch of the left edge of the page extent after one-half of an inch is hidden by the page binding.

To specify this condition, a user could simply use a left margin of 1.5 inches, which would be lost if the margins are later changed, or could specify a one-half inch gutters follows in the WordprocessingML:

<w:pgMar … w:gutter="720"/>

This fragment specifies that the gutter shall span 720 twentieths of a point, after which any margin value shall be added. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

header (Spacing to Top of Header)

Specifies the distance (in twentieths of a point) from the top edge of the page to the top edge of the header.

[Example: Consider a document where the header shall start two inches below the top of the page extent. To specify this boundary, the following page margins must specified in the WordprocessingML:

<w:pgMar … w:header="2880"/>

This fragment specifies that the header shall start 2880 twentieths of a point from the top of the page. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

left (Left Margin Spacing)

Specifies the distance (in twentieths of a point) between the left edge of the page and the left edge of the text extents for this document.

[Example: Consider a document where the left text extent shall start two inches inside the page extent. To specify this boundary, the following page margins must specified in the WordprocessingML:

<w:pgMar … w:left="2880"/>

This fragment specifies that the left margin shall span 2880 twentieths of a point from the left edge of the page. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

right (Right Margin Spacing)

Specifies the distance (in twentieths of a point) between the right edge of the page and the right edge of the text extents for this document.

[Example: Consider a document where the right text extent shall start one inch inside the page.

To specify this boundary, the following page margins must specified in the WordprocessingML:

<w:pgMar … w:right="1440"/>

This fragment specifies that the right margin shall span 1440 twentieths of a point from the right edge of the page. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

top (Top Margin Spacing)

Specifies the distance (in twentieths of a point) between the top of the text margins for the main document and the top of the page for all pages in this section.

If the value of top is non-negative, then the text will be placed at the greater of:

The value of top

The extent of the header text

[Example: Consider a document where the header shall start one inch from the top of the page extent, but the contents of the main document story specify that they shall start one-half of an inch from the page extents. To specify these boundaries, the following page margins may specified in the WordprocessingML:

<w:pgMar … w:top="720" w:header="1440"/>

This fragment specifies that the header shall start 1440 twentieths of a point from the top of the page, but the main document story shall start 720 twentieths of a point from the top of the page. Since the header extent is guaranteed to be greater in this case, the main text extent ends at the bottom of the header region. end example]

A negative value indicates that the contents of the main document shall be measured from the top of the page extent regardless of the header for that document, and therefore shall overlap the header text.

[Example: Consider a document where the header shall start one inch from the top of the page extent, but the contents of the main document story shall start one-half of an inch from the page extents. To specify these boundaries, the following page margins may specified in the WordprocessingML:

<w:pgMar ... w:top="-720" w:header="1440"/>

This fragment specifies that the header shall start 1440 twentieths of a point from the top of the page, and the main document story shall start 720 twentieths of a point from the top of the page. Since the value of top is negative in this case, the top text extent starts one-half of an inch from the top of the page and overlaps any header text. end example]

The possible values for this attribute are defined by the ST_SignedTwipsMeasure simple type (§2.18.88).

The following XML Schema fragment defines the contents of this element:

</complexType>

pgNumType (Page Numbering Settings)

This element specifies the page numbering settings for all page numbers that appear in the contents of the current section.

[Example: Consider a section in which the page numbers shall start at page 25. The following WordprocessingML syntax specifies that requirement:

<w:sectPr> … <w:pgNumType w:start="25"/></w:sectPr>

The pgNumType element specifies that numbering on this section shall start from page number 25. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

chapSep (Chapter Separator Character)

Specifies the separator character that shall appear between the chapter and page number, if a chapter style has been set for page numbers in this section.

If the chapStyle attribute is not present, or its specified heading level does not have an associated numbering format, then this value is ignored, since no chapter number is output by the field.

[Example: Consider a section in a document in which the chapter shall be separated from the page number using a colon character. This constraint would be specified using the following WordprocessingML:

<w:pgNumType w:chapSep="colon" chapStyle="1" />

The chapSep attribute declares that the chapter and page number shall be separated by a colon (e.g. 1:1 for chapter one, page one). end example]

The possible values for this attribute are defined by the ST_ChapterSep simple type (§2.18.9).

chapStyle (Chapter Heading Style)

Specifies the one-based index of the heading style applied to chapter titles in the document which shall be used as chapter headings in all page numbers for this section, by locating the nearest heading of that style and extracting the numbering information.

If the specified heading style does not exist in the current section, or does not have a numbering format, then any previous level heading format shall be used as needed as the specified chapter number. If no heading has numbering information and/or is used in the section, then the chapter and chapter separator shall be omitted from the page numbering data.

[Example: Consider a page number in a section with page numbering properties that specify a chapStyle of 1 (Heading 1 style) and a chapSep of dash.

This means that for each page number in this section, the numbering value of the nearest Heading 1 style is used for the chapter value, and is followed by a dash, then the page n umber in that section. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

fmt (Page Number Format)

Specifies the number format that shall be used for all page numbering in this section.

[Example: A fmt value of lowerLetter indicates that a consumer shall use lowercase letters for each page in this section: a,b,c… end example]

The possible values for this attribute are defined by the ST_NumberFormat simple type (§2.18.66).

start (Starting Page Number)

Specifies the page number that appears on the first page of the section.

If this value is omitted, numbering will continue from the highest page number in the previous section.

[Example: Consider the following WordprocessingML:

<w:pgNumType w:fmt="2"/>

Because the start value is omitted, the page numbers in this section begin at the value of the highest page in the previous section.

This means that if the previous section ended in page 7, this section would start with page 8. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

pgSz (Page Size)

This element specifies the properties (size and orientation) for all pages in the current section.\

[Example: Consider a section that shall be printed on A4 paper. The WordprocessingML for this paper size is as follows:

<w:pgSz w:w="11907" w:h="16839" />

This output states that all pages in this section shall be 11907 twentieths of a point wide (11907 twentieths of a point = 8.269") and 16839 twentieths of a point high (16939 twentieths of a point = 11.694"). end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

code (Printer Paper Code)

Specifies a printer-specific paper code for the paper type, which shall be used by the printer for pages in this section.

This code is stored to ensure the proper paper type is chosen if the specified paper size matches the sizes of multiple paper types supported by the current printer.

[Example: Consider the following WordprocessingML fragment:

<w:pgSz … w:code="240" />

The code attribute specifies a value of 240, which will be sent to the printer and used by the printer to determine the appropriate paper type to use when printing.

This value is not interpreted or modified other than storing it as specified by the printer. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

h (Page Height)

Specifies the height (in twentieths of a point) for all pages in the current section.

[Example: Consider the following WordprocessingML:

<w:pgSz w:w="15840" w:h="12240" />

All pages in this section are displayed on a page that is 12240 twentieths of a point (8.5") tall. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

orient (Page Orientation)

Specifies the orientation of all pages in this section.

This information is used to determine the actual paper size to use on the printer.

[Example: Pages 11" wide by 8.5" long in landscape mode use 8.5"x11" paper, because the width and height are reversed for pages in this landscape section with respect to the printed page. end example]

This implies that the actual paper size width and height are reversed for pages in this section. If this attribute is omitted, then portrait shall be implied.

[Example: Consider the following WordprocessingML:

<w:pgSz w:w="15840" w:h="12240" w:orient="landscape" />

Although the page width is 11", and page height is 8.5", according to the w and h attributes, because the orient attribute is set to landscape, pages in this section are printed on 8.5x11" paper in landscape mode. end example]

The possible values for this attribute are defined by the ST_PageOrientation simple type (§2.18.71).

w (Page Width)

This attribute indicates the width (in twentieths of a point) for all pages in the current section.

[Example: Consider the following WordprocessingML:

<w:pgSz w:w="15840" w:h="12240" />

All pages in this section are displayed on a page that is 15840 twentieths of a point (11") wide. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

The following XML Schema fragment defines the contents of this element:

</complexType>

printerSettings (Reference to Printer Settings Data)

This element specifies an explicit relationship to a Printer Settings part containing information about the printer settings used for this section.

If this element is omitted, than no additional settings are associated with this section.

[Example: Consider a producer which needed to store additional printer settings for each section. A document from such a producer would have the following section properties:

<w:sectPr> ... <w:printerSettings r:id="rId10" /></w:sectPr>

The resulting Main Document part would a relationship to the appropriate Printer Settings part with a relationship ID of rId10. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

The following XML Schema fragment defines the contents of this element:

</complexType>

right (Right Border)

This element specifies the presentation and display of the page border displayed at the right of each page in this section.

[Example: Consider a section in which all pages shall have a right border consisting of a repeated image of an umbrella, like this:

This border would result in the following WordprocessingML:

<w:sectPr> … <w:pgBorders> <w:right w:val="seattle" …/> </w:pgBorders> …</w:sectPr>

Because the page has a border at the right only, only the right element is specified within the set of page borders. end example]

When a document has a right border that is relative to the page edges (using the offsetFrom attribute value of page on pgBorders), it shall span the right edge of the page at the location defined by its properties, stopping when:

It intersects with the corresponding top or bottom page border (if one is specified)

It reaches the edge of the page.

[Example: In the example above, no top or bottom border was specified in the WordprocessingML, so a consumer shall draw the border from one edge of the page to the other. end example]

When a document has a right border that is relative to the text (using the offsetFrom attribute value of text on pgBorders), it shall only span the necessary width to satisfy the requirement of spanning the width of the text.

Parent Elements

pgBorders (§2.6.10)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

The possible values for this attribute are defined by the ST_HexColor simple type (§2.18.43).

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

The possible values for this attribute are defined by the ST_PointMeasure simple type (§2.18.75).

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

The possible values for this attribute are defined by the ST_EighthPointMeasure simple type (§2.18.27).

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

The possible values for this attribute are defined by the ST_ThemeColor simple type (§2.18.104).

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

The possible values for this attribute are defined by the ST_Border simple type (§2.18.4).

The following XML Schema fragment defines the contents of this element:

</complexType>

rtlGutter (Gutter on Right Side of Page)

This element specifies that the page gutter shall be placed on the right side of the page for this section only. The page gutter defines the amount of extra space added to the specified margin, above any existing margin values. [Note: This setting is typically used when a document is being created for binding, in order to ensure that the resulting margins are present after the binding gutter is consumed by the printed matter binding. end note]

If the gutter is set to the side of the page by the omission of the gutterAtTop element (§2.15.1.49), then each section's gutter is placed at the left by default, unless that default is overridden by the rtlGutter element.

[Example: Consider a document with three sections, with gutter properties defined as follows:

<w:p> <w:pPr> <w:sectPr> <w:pgMar w:gutter="1440" …/> … </w:sectPr> </w:pPr></w:p>

...

<w:p> <w:pPr> <w:sectPr> <w:pgMar w:gutter="1440" …/> <w:rtlGutter w:val="0" /> … </w:sectPr> </w:pPr></w:p>

...

<w:p> <w:pPr> <w:sectPr> <w:pgMar w:gutter="1440" …/> <w:rtlGutter /> … </w:sectPr> </w:pPr></w:p>

The first and second sections both place the gutter on the left side, the first by omission of the rtlGutter attribute, and the second by explicitly turning it off. The third section, however, moves the gutter to the right side via the use of the rtlGutter attribute. end example]

If the gutterAtTop element (§2.15.1.49) is specified and true, then each section's gutter is at the top and this setting is ignored.

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

sectPr (Previous Section Properties)

When specified as a child element of sectPrChange, the sectPr element specifies a set of section properties that were modified when the document was set to track all revisions.

[Example: If the page orientation was changed with revision tracking enabled, the following WordprocessingML defines the contents of that change:

<w:sectPr> … <w:sectPrChange …> <w:sectPr> <w:pgSz w:w="15840" w:h="12240"/> </w:sectPr> </w:sectPrChange></w:sectPr>

The properties that were changed as part of this revision are stored in this sectPr element. end example]

Parent Elements

sectPrChange (§2.13.5.34)

Child Elements

Subclause

bidi (Right to Left Section Layout)

§2.6.1

cols (Column Definitions)

§2.6.4

docGrid (Document Grid)

§2.6.5

endnotePr (Section-Wide Endnote Properties)

§2.11.5

footnotePr (Section-Wide Footnote Properties)

§2.11.12

formProt (Only Allow Editing of Form Fields)

§2.6.6

lnNumType (Line Numbering Settings)

§2.6.8

noEndnote (Suppress Endnotes In Document)

§2.11.16

paperSrc (Paper Source Information)

§2.6.9

pgBorders (Page Borders)

§2.6.10

pgMar (Page Margins)

§2.6.11

pgNumType (Page Numbering Settings)

§2.6.12

pgSz (Page Size)

§2.6.13

printerSettings (Reference to Printer Settings Data)

§2.6.14

rtlGutter (Gutter on Right Side of Page)

§2.6.16

textDirection (Text Flow Direction)

§2.6.20

titlePg (Different First Page Headers and Footers)

§2.10.6

type (Section Type)

§2.6.22

vAlign (Vertical Text Alignment on Page)

§2.6.23

Attributes

Description

rsidDel (Section Deletion Revision ID)

Specifies a unique identifier used to track the editing session when the section mark for this section was deleted from the document.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidR (Section Addition Revision ID)

Specifies a unique identifier used to track the editing session when the section mark for this section was added to the document.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidRPr (Physical Section Mark Character Revision ID)

Specifies a unique identifier used to track the editing session when the physical character representing this section mark was last formatted.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidSect (Section Properties Revision ID)

Specifies a unique identifier used to track the editing session when the physical character representing this section mark was last formatted.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

sectPr (Document Final Section Properties)

This element defines the section properties for the final section of the document. [Note: For any other section the properties are stored as a child element of the paragraph element corresponding to the last paragraph in the given section. end note]

[Example: Consider a document with multiple sections. For all sections except the final section, the sectPr element is stored as a child element of the last paragraph in the section. For the final section, this information is stored as the last child element of the body element, as follows:

<w:body> <w:p> … </w:p> … <w:sectPr> (final section's properties) </w:sectPr></w:body>

end example]

Parent Elements

body (§2.2.2); docPartBody (§2.12.6)

Child Elements

Subclause

bidi (Right to Left Section Layout)

§2.6.1

cols (Column Definitions)

§2.6.4

docGrid (Document Grid)

§2.6.5

endnotePr (Section-Wide Endnote Properties)

§2.11.5

footerReference (Footer Reference)

§2.10.2

footnotePr (Section-Wide Footnote Properties)

§2.11.12

formProt (Only Allow Editing of Form Fields)

§2.6.6

headerReference (Header Reference)

§2.10.5

lnNumType (Line Numbering Settings)

§2.6.8

noEndnote (Suppress Endnotes In Document)

§2.11.16

paperSrc (Paper Source Information)

§2.6.9

pgBorders (Page Borders)

§2.6.10

pgMar (Page Margins)

§2.6.11

pgNumType (Page Numbering Settings)

§2.6.12

pgSz (Page Size)

§2.6.13

printerSettings (Reference to Printer Settings Data)

§2.6.14

rtlGutter (Gutter on Right Side of Page)

§2.6.16

sectPrChange (Revision Information for Section Properties)

§2.13.5.34

textDirection (Text Flow Direction)

§2.6.20

titlePg (Different First Page Headers and Footers)

§2.10.6

type (Section Type)

§2.6.22

vAlign (Vertical Text Alignment on Page)

§2.6.23

Attributes

Description

rsidDel (Section Deletion Revision ID)

Specifies a unique identifier used to track the editing session when the section mark for this section was deleted from the document.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidR (Section Addition Revision ID)

Specifies a unique identifier used to track the editing session when the section mark for this section was added to the document.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidRPr (Physical Section Mark Character Revision ID)

Specifies a unique identifier used to track the editing session when the physical character representing this section mark was last formatted.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidSect (Section Properties Revision ID)

Specifies a unique identifier used to track the editing session when the physical character representing this section mark was last formatted.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

sectPr (Section Properties)

This element defines the section properties for the a section of the document. [Note: For the last section in the document, the section properties are stored as a child element of the body element. end note]

[Example: Consider a document with multiple sections. For all sections except the final section, the sectPr element is stored as a child element of the last paragraph in the section, as follows:

<w:body> <w:p>

<w:pPr>

<w:sectPr> (final section's properties) </w:sectPr>

</w:pPr>

… </w:p> … <w:sectPr> (final section's properties) </w:sectPr></w:body>

end example]

Parent Elements

pPr (§2.7.4.2); pPr (§2.9.24); pPr (§2.7.5.1); pPr (§2.3.1.26); pPr (§2.7.7.2)

Child Elements

Subclause

bidi (Right to Left Section Layout)

§2.6.1

cols (Column Definitions)

§2.6.4

docGrid (Document Grid)

§2.6.5

endnotePr (Section-Wide Endnote Properties)

§2.11.5

footerReference (Footer Reference)

§2.10.2

footnotePr (Section-Wide Footnote Properties)

§2.11.12

formProt (Only Allow Editing of Form Fields)

§2.6.6

headerReference (Header Reference)

§2.10.5

lnNumType (Line Numbering Settings)

§2.6.8

noEndnote (Suppress Endnotes In Document)

§2.11.16

paperSrc (Paper Source Information)

§2.6.9

pgBorders (Page Borders)

§2.6.10

pgMar (Page Margins)

§2.6.11

pgNumType (Page Numbering Settings)

§2.6.12

pgSz (Page Size)

§2.6.13

printerSettings (Reference to Printer Settings Data)

§2.6.14

rtlGutter (Gutter on Right Side of Page)

§2.6.16

sectPrChange (Revision Information for Section Properties)

§2.13.5.34

textDirection (Text Flow Direction)

§2.6.20

titlePg (Different First Page Headers and Footers)

§2.10.6

type (Section Type)

§2.6.22

vAlign (Vertical Text Alignment on Page)

§2.6.23

Attributes

Description

rsidDel (Section Deletion Revision ID)

Specifies a unique identifier used to track the editing session when the section mark for this section was deleted from the document.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidR (Section Addition Revision ID)

Specifies a unique identifier used to track the editing session when the section mark for this section was added to the document.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidRPr (Physical Section Mark Character Revision ID)

Specifies a unique identifier used to track the editing session when the physical character representing this section mark was last formatted.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

rsidSect (Section Properties Revision ID)

Specifies a unique identifier used to track the editing session when the physical character representing this section mark was last formatted.

All rsid* attributes throughout this document of an equal value, if present, shall indicate that those regions were modified during the same editing session.

A producer may choose to increment the revision save ID value to indicate subsequent editing sessions (editing between save actions) to indicate the order of the saves performed.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

textDirection (Text Flow Direction)

This element specifies the direction of the text flow for this section.

[Example: Consider a document with a section in which text shall flow bottom to top vertically, and left to right horizontally. This setting requires the following WordprocessingML:

<w:sectPr> … <w:textDirection w:val="btLr" /></w:sectPr>

The textDirection element specifies via the btLr value in the val attribute that the text flow shall go bottom to top, and left to right. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (Direction of Text Flow)

Specifies the direction of the text flow for this object.

[Example: Consider a document with a section in which text shall flow bottom to top vertically, and left to right horizontally. This setting requires the following WordprocessingML:

<w:sectPr> … <w:textDirection w:val="btLr" /></w:sectPr>

The textDirection element specifies via the btLr value in the val attribute that the text flow shall go bottom to top, and left to right. end example]

The possible values for this attribute are defined by the ST_TextDirection simple type (§2.18.100).

The following XML Schema fragment defines the contents of this element:

</complexType>

top (Top Border)

This element specifies the presentation and display of the page border displayed at the top of each page in this section.

[Example: Consider a section in which all pages shall have a top border consisting of a repeated image of balloons, like this:

This border would result in the following WordprocessingML:

<w:sectPr> … <w:pgBorders> <w:top w:val="balloons" .../> </w:pgBorders> …</w:sectPr>

Because the page only has a border at the top, only the top element is specified within the set of page borders. end example]

When a document has a top border that is relative to the page edges (using an offsetFrom attribute value of page on pgBorders), it shall span the top edge of the page at the location defined by its properties, stopping when:

It intersects with the corresponding left or right page border (if one is specified)

It reaches the edge of the page.

[Example: In the example above, no left or right border was specified in the WordprocessingML, so a consumer shall draw the border from one edge of the page to the other. end example]

When a document has a top border that is relative to the text (using the offsetFrom attribute value of text on pgBorders), it shall only span the necessary width to satisfy the requirement of spanning the width of the text.

Parent Elements

pgBorders (§2.6.10)

Attributes

Description

color (Border Color)

Specifies the color for this border.

This color may either be presented as a hex value (in RRGGBB format), or auto to allow a consumer to automatically determine the border color as appropriate.

[Example: Consider a border color with value auto, as follows:

<w:bottom … w:color="auto"/>

The possible values for this attribute are defined by the ST_HexColor simple type (§2.18.43).

frame (Create Frame Effect)

Specifies whether the specified border should be modified to create a frame effect by reversing the border's appearance from the edge nearest the text to the edge furthest from the text.

If this attribute is omitted, then the border is not given any frame effect.

[Example: Consider a bottom border which shall appear with a frame effect, which is specified in the following WordprocessingML:

<w:bottom w:frame="true" ... />

This frame's val is true, indicating that the border frame effect shall be applied. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

shadow (Border Shadow)

Specifies whether this border should be modified to create the appearance of a shadow.

If this attribute is omitted, then the border is not given the shadow effect.

[Example: Consider a top border which shall appear with a shadow effect, resulting in the following WordprocessingML:

<w:bottom w:shadow="true" ... />

This frame's val is true, indicating that the shadow effect shall be applied to the border. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

space (Border Spacing Measurement)

Specifies the spacing offset that shall be used to place this border on the parent object.

[Example: Consider a document with a set of page borders all specified to appear 24 points from the edge of the page. The resulting WordprocessingML would be as follows:

<w:pgBorders w:offsetFrom="page">

<w:bottom … w:space="24/>

</w:pgBorders

The possible values for this attribute are defined by the ST_PointMeasure simple type (§2.18.75).

sz (Border Width)

Specifies the width of the current border.

[Example: Consider a document with a three point wide dashed line border on all sides, resulting in the following WordprocessingML markup:

<w:top w:val="dashed" w:sz="24" …/>

<w:left w:val="dashed" w:sz="24" …/>

<w:bottom w:val="dashed" w:sz="24" …/>

<w:right w:val="dashed" w:sz="24" …/>

The possible values for this attribute are defined by the ST_EighthPointMeasure simple type (§2.18.27).

themeColor (Border Theme Color)

Specifies a theme color to be applied to the current border.

The specified theme color is a reference to one of the predefined theme colors, located in the document's Theme part,which allows color information to be set centrally in the document.

[Example: Consider a set of borders configured to use the accent2 theme color, resulting in the following WordprocessingML markup:

The possible values for this attribute are defined by the ST_ThemeColor simple type (§2.18.104).

themeShade (Border Theme Color Shade)

Specifies the shade value applied to the supplied theme color (if any) for this border instance.

If the themeShade is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeShade value is stored as a hex encoding of the shade value (from 0–255) applied to the current border.

[Example: Consider a shade of 40% applied to a border in a document. This shade is calculated as follows:

The resulting themeShade value in the file format would be 66. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is C0504D.

The equivalent HSL color value would be.

Applying the shade formula with a shade percentage of 75% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 943634.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="943634" w:themeColor="accent2" w:themeShade="BF"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

themeTint (Border Theme Color Tint)

Specifies the tint value applied to the supplied theme color (if any) for this border instance.

If the themeTint is supplied, then it is applied to the RGB value of the theme color (from the theme part) to determine the final color applied to this border.

The themeTint value is stored as a hex encoding of the tint value (from 0–255) applied to the current border.

[Example: Consider a tint of 60% applied to a border in a document. This tint is calculated as follows:

The resulting themeTint value in the file format would be 99. end example]

Given an RGB color defined as three hex values in RRGGBB format, the shade is applied as follows:

Convert the color to the HSL color format (values from 0 to 1)

Modify the luminance factor as follows:

Convert the resultant HSL color to RGB

[Example: Consider a document with a background using the accent2 theme color, whose RGB value (in RRGGBB hex format) is 4F81BD.

The equivalent HSL color value would be.

Applying the tint formula with a tint percentage of 60% to the luminance, we get:

Taking the resulting HSL color value of and converting back to RGB, we get 95B3D7.

This transformed value can be seen in the resulting background's color attribute:

<w:top w:val="single" w:sz="4" w:space="24" w:color="95B3D7" w:themeColor="accent2" w:themeTint="99"/>

end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

val (Border Style)

Specifies the style of border used on this object.

[Example: Consider a left border resulting in the following WordprocessingML:

<w:left w:val="single" …/>

This border's val is single, indicating that the border style is a single line. end example]

The possible values for this attribute are defined by the ST_Border simple type (§2.18.4).

The following XML Schema fragment defines the contents of this element:

</complexType>

type (Section Type)

This element specifies the type of the current section. The section type specifies how the contents of the current section shall be placed relative to the previous section.

WordprocessingML supports five distinct types of section breaks:

Next page section breaks (the default if type is not specified), which begin the new section on the following page.

Odd page section breaks, which begin the new section on the next odd-numbered page.

Even page section breaks, which begin the new section on the next even-numbered page.

Continuous section breaks, which begin the new section on the following paragraph. This means that continuous section breaks might not specify certain page-level section properties, since they must be inherited from the following section. These breaks, however, can specify other section properties, such as line numbering and footnote/endnote settings.

Column section breaks, which begin the new section on the next column on the page.

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (Section Type Setting)

Specifies the type of the current section.

[Example: Consider a section that shall start on the next page in the document. The WordprocessingML specifying this would look like:

<w:sectPr> … <w:type w:val="nextPage"/></w:sectPr>

The nextPage value specifies that this section starts on the next page. end example]

The possible values for this attribute are defined by the ST_SectionMark simple type (§2.18.84).

The following XML Schema fragment defines the contents of this element:

</complexType>

vAlign (Vertical Text Alignment on Page)

This element specifies the vertical alignment for text on pages in the current section, relative to the top and bottom margins in the main document story on each page.

[Example: Consider a section used as a title page on which text shall be vertically centered. In order to center the text vertically on the page, the following WordprocessingML is used:

<w:sectPr> … <w:vAlign w:val="center" /></w:sectPr>

The vAlign value of center specifies that text shall be laid out in the center of the top and bottom text margins for all pages in this section. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (Vertical Alignment Setting)

Specifies the vertical alignment for text between the top and bottom margins of the parent container (page or table cell).

<w:vAlign w:val="center" />

The val attribute of center specifies that the content is centered relative to its container (in this case, the page). end example]

The possible values for this attribute are defined by the ST_VerticalJc simple type (§2.18.111).

The following XML Schema fragment defines the contents of this element:

</complexType>

Styles

Within a WordprocessingML file, styles are predefined sets of table, numbering, paragraph, and/or character properties which can be applied to text within the document. This allows the formatting properties to be stored and managed independently from the content, allowing the look of document content to be changed in a single location (e.g. the look of all first-level headings is changed by changing the style with styleId Heading1 rather than looking for and changing each paragraph in the document).

[Example: The Normal paragraph style in a word processing document can have any number of formatting properties, e.g. font face = Times New Roman; font size = 12pt; paragraph justification = left). All paragraphs which reference this paragraph style would automatically inherit these properties. end example]

Each style defined within a WordprocessingML document requires a style definition. The style definition contains all of the information needed by a consumer to store and display that style within a WordprocessingML document, and is defined using the style element. The style definition for any style in WordprocessingML can be divided into three segments The complete definition of style properties can be found on the reference for the style element (§2.7.3.17):

General style properties

Style types

Type specific formatting properties

Each of these three segments are discussed in the following subclauses.

Style Inheritance

In order to compile the complete set of paragraph and character properties specified by any given style (as appropriate), a consumer must follow the rule of style inheritance to determine each property in that set.

Style inheritance states that styles of any given type may inherit from other styles of that type, and therefore a consumer must ‘build up’ the style information by following the inheritance tree. This inheritance is defined via the basedOn element, which specifies the styleId of the parent style.

[Example: The “Tristan Test” paragraph style can inherit properties from the “Heading 1” paragraph style, which itself can inherit properties from the “Normal” paragraph style. end example]

To build up the resulting style, a consumer must trace the hierarchy (following each basedOn value) back to a style which has no basedOn element (is not based on another style). The resulting style is then constructed by following each level in the tree, applying the specified paragraph and/or character properties as appropriate. When properties conflict, they are overridden by each subsequent level (this includes turning OFF a property set at an earlier level). Properties which are not specified simply do not change those specified at earlier levels.

[Example: Consider a character style Green which specifies only that the text color is green, but inherits from another character style Base which defines a font face of Arial, as well as bold:

<w:style w:type="character" w:styleId="Green">

<w:name w:val="Green" />

<w:basedOn w:val="Base" />

<w:rPr>

<w:color w:val="22B14C" />

</w:rPr>

</w:style>

...

../Local Settings/Temp/styles.xml<w:style w:type="character" w:styleId="Base">

<w:name w:val="Base" />

<w:rPr>

<w:rFonts w:ascii="Arial" w:hAnsi="Arial" />

<w:b />

</w:rPr>

</w:style>

The definition of the Green character style has a basedOn element which specifies the Base style. This means that any use of the Green style is defined as bold, green, Arial text. end example]

Conversely, a producer should not output any property on a style which has already been set by a previous level of the style hierarchy, as well as those which match the document defaults. This means that if the document defaults or any previous level in a style’s hierarchy specify a property which is unchanged at this level, that property should not be part of the style definition in the resulting WordprocessingML.

[Example: If the document default font is Bauhaus 93 and the Heading 1 style also specifies the Bauhaus 93 font, then a producer should not output any rFonts element for the Heading 1 style definition, because that formatting is inherited from the document defaults. end example]

Style Hierarchy

With the various flavors of styles available (see each of the subclauses below), multiple style types can be applied to the same content within a file, which means that properties must be applied in a specific deterministic order. As with inheritance, the resulting formatting properties set by one type can be unchanged, removed, or altered by following types.

The following table illustrates the order of application of these defaults, and which properties are impacted by each:

This process can be described as follows:

First, the document defaults are applied to all runs and paragraphs in the document.

Next, the table style properties are applied to each table in the document, following the conditional formatting inclusions and exclusions specified per table.

Next, numbered item and paragraph properties are applied to each paragraph formatted with a numbering style.

Next, paragraph and run properties are applied to each paragraph as defined by the paragraph style.

Next, run properties are applied to each run with a specific character style applied.

Finally, we apply direct formatting (paragraph or run properties not from styles). If this direct formatting includes numbering, that numbering + the associated paragraph properties are applied.

General Style Properties

General style properties refer to the set of properties which can be used regardless of the type of style. [Example: Within a style definition the style name, additional aliases for the style, a style ID (used by the document content to refer to the style), if style is hidden, if style is locked, etc. are general style properties. end example]

[Example: Consider a style called Heading 1 in a document as follows:

<w:style w:type="paragraph" w:styleId="Heading1"> <w:name w:val="heading 1"/> <w:basedOn w:val="Normal"/> <w:next w:val="Normal"/> <w:link w:val="Heading1Char"/> <w:priority w:val="1"/> <w:qformat/> <w:rsid w:val="00F303CE"/> ...</w:style>

Above the formatting information specific to this style type are a set of general style properties which define information shared by all style types. end example]

aliases (Alternate Style Names)

This element specifies the set of alternative names for the parent style definition. These names may be used in an application's user interface as desired. The alternate names shall be stored in this element's val attribute, and each name shall be separated by one or more consecutive comma characters (Unicode character value 002C). All commas present shall be interpreted as separator character and never as part of an alternate style name.

If present, the alternate style names shall be used in the user interface in place of the built-in name specified in the name element (§2.7.3.9) when the appropriate value is set in the stylePaneFormatFilter element (§2.15.1.87).

If this element is omitted, then the style shall not have any alternate style names.

[Example: Consider a style with a primary name and two alternate names, defined using the name and aliases elements, as follows:

<w:style w:styleId="TestStyle" … > <w:name w:val="GD20Complex"/> <w:aliases w:val="Regional Growth,Complex Growth"/> …</w:style>

This style specifies that it has the primary name GD20Complex using the name element (§2.7.3.9), as well as two alternate names Regional Growth and Complex Growth using the aliases element. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

autoRedefine (Automatically Merge User Formatting Into Style Definition)

This element specifies whether an application shall automatically modify this style when the contents of an entire paragraph in the document with this style applied are modified, ensuring that although only a single instance of text with this style was modified, that change is stored on the style and therefore propagated to all locations where the style is in use.

If this element is omitted, then formatting shall not automatically be merged back into the style definition.

[Example: Consider a style defined as follows in a WordprocessingML document:

<w:style w:styleId="Normal" … > <w:name w:val="Normal"/> <w:autoRedefine/> <w:rPr> <w:b/> </w:rPr> …</w:style>

This style specifies via the use of the autoRedefine element that any formatting applied to text which uses this style shall be merged back into the style definition (assuming, of course, that this is a paragraph style).

For example, consider a document which uses the Normal style as defined above:

The first and third paragraphs use the Normal style, and hence have the bold property applied. If an application were to add the underline formatting to the entire first paragraph, as follows:

That property, rather than being saved as direct formatting, shall be used to update the associated Normal style to add this property, specified using the u element (§2.3.2.38).

<w:style w:styleId="Normal" … > <w:name w:val="Normal"/> <w:autoRedefine/> <w:rPr> <w:b/> <w:u/> </w:rPr> …</w:style>

Since this property is automatically merged into the style, it would also appear on the third paragraph (note that the step above would normally be automatically modified into the state shown below, and not discrete as shown above).

end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

basedOn (Parent Style ID)

This element specifies the style ID of the parent style from which this style inherits in the style inheritance. The style inheritance refers to a set of styles which inherit from one another to produce the resulting set of properties for a single style. The val attribute of this element specifies the styleId attribute for the parent style in the style inheritance.

If this element is omitted, then this style shall not be based on any other style in the current document (i.e. this element is the root of the style inheritance for a style). If no style in the current document specifies the styleId present in the val attribute, then this element shall be ignored (i.e. this element is the root of the style inheritance for a style).

If a style with this styleId is present, then it shall be subject to the following restrictions:

If the current style is a table style, then the parent style must also be a table style, or this element shall be ignored.

If the current style is a paragraph style, then the parent style must also be a paragraph style, or this element shall be ignored.

If the current style is a character style, then the parent style must also be a character style, or this element shall be ignored.

If the current style is a numbering style, then this element shall be ignored.

[Example: Consider three WordprocessingML character styles defined as follows:

A character style with a styleId value of Strong whose properties consist of the bold property

A character style with a styleId value of Underline whose properties consist of the underline property

A character style with a styleId value of Emphasis whose properties consist of the italics property

Each of these character styles defines a single character formatting property. If the basedOn values for each element were defined as follows:

<w:style w:styleId="Strong"> <w:basedOn w:val="Underline"/> … <w:rPr> <w:b/> </w:rPr></w:style>

<w:style w:styleId="Underline"> <w:basedOn w:val="Emphasis"/> … <w:rPr> <w:u/> </w:rPr></w:style>

<w:style w:styleId="Emphasis"> … <w:rPr> <w:i/> </w:rPr></w:style>

The Strong style is based on the Underline style which is in turn based on the Emphasis style. This means that the actual definition of the Strong style would be as follows:

Bold

Underline (inherited from Underline)

Italics (inherited from Emphasis)

The style chain for the Strong style would be defined as follows:

Emphasis

Underline

Strong

Similarly, the style chain for the Underline style would be defined as follows:

Emphasis

Underline

In each case, the style chain is the list of all styles which are combined in order to produce the entire set of properties for any given style. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

hidden (Hide Style From User Interface)

This element specifies whether this style shall be hidden from any and all user interfaces when this document is loaded by an application. If this element is set, then this style may be used to format content (i.e. any content which references this style shall have its properties as normal), but the style shall be hidden from all user interface associated with that application. [Note: This setting is typically used to hide styles which are being used internally by an application which should not be used as formatting in a typical case. end note]

If this element is omitted, then the style shall not be required to be hidden from the user interface.

[Example: Consider a style with a primary name of InternalStyle that should not be displayed in any user interface. This requirement would be specified using the following WordprocessingML:

<w:style … w:styleId="Style2"> <w:name w:val="InternalStyle"/> <w:hidden/> …</w:style>

The hidden element specifies that this style definition shall be round-tripped with the file (since it is part of the document) but should not be displayed in any user interface associated with an application which processes this document. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

latentStyles (Latent Style Information)

This element specifies the properties which shall be applied to a set of latent styles for this document. Latent styles refer to any set of style definitions known to an application which have not been included in the current document. [Example: Latent styles may include additional styles known by a particular hosting application. end example]

When a style definition is embedded in a document, it specifies two distinct groups of properties:

Behavior properties

Formatting properties

Obviously, embedding all the styles known to a particular application in each document which it produces would drastically increase the file size. Latent styles provide a way to store pieces of information for the first group (behavior properties) which must be specified for all styles known to an application without requiring the storage of the second group (formatting properties).

[Example: Consider a WordprocessingML document which contains text specified in one of two styles: Heading1 or Normal. Based on this, the document only needs to store the formatting properties for those two styles, saving the additional overhead which would be required to save all of the styles supported by the hosting application.

However, if the documentProtection element (§2.15.1.28) specifies that the hosting application shall prevent the use of any style whose locked element (§2.7.3.7) is set to false, then the locking state of all styles known to that application become useful and necessary to maintain the current state of the document. Using latent styles, this information may be stored without storing any formatting properties for those styles.

For example, if all styles which are not stored in the document shall be locked except for the style with a primary name (§2.7.3.9) of Heading 2. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defLockedState="true"> <w:lsdException w:name="Heading 2" w:locked="false"/></w:latentStyles>

The latentStyles element specifies that all latent styles known to any hosting application shall have a default locking state of true except for any style known to the hosting application with a primary name of Heading 2, whose latent style definition specifies that its locked state shall be false. end example]

Parent Elements

styles (§2.7.3.18)

Child Elements

Subclause

lsdException (Latent Style Exception)

§2.7.3.8

Attributes

Description

count (Latent Style Count)

Specifies the number of known styles which shall be initialized to the current latent style defaults when this document is first processed. [Note: This property may be used by an application as needed to ensure that only the number of styles known when this document was created are initialized with the defaults on the parent element, and that all new known styles use their default values. end note]

[Example: Consider a WordprocessingML document in which only the first 20 latent styles shall be initialized. This requirement would be specified as follows:

<w:latentStyles w:count="20" … > …</w:latentStyles>

The count attribute specifies that 20 known styles shall be initialized to the default settings when the document is first opened, and any additional styles should use the defaults defined by the application. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

defLockedState (Default Style Locking Setting)

Specifies the default setting for the locked element (§2.7.3.7) which shall be applied to any style made available by the hosting application which is not explicitly defined in the current document. This setting shall be overridden for every style for which a latent style exception (§2.7.3.8) exists.

If this element is omitted, the default locked state for all latent styles in the current document shall be false.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall be locked. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defLockedState="true"> …</w:latentStyles>

The defLockedState attribute specifies that all latent styles in the current document shall have a locked element setting of true by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

defQFormat (Default Primary Style Setting)

Specifies the default setting for the qFormat element (§2.7.3.14) which shall be applied to any style made available by the hosting application which is not explicitly defined in the current document. This setting shall be overridden for every style for which a latent style exception (§2.7.3.8) exists.

If this element is omitted, the default qFormat state for all latent styles in the current document shall be false.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall not be marked as primary styles. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defQFormat="false"> …</w:latentStyles>

The defQFormat attribute specifies that all latent styles in the current document shall have a qFormat element setting of false by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

defSemiHidden (Default Semi-Hidden Setting)

Specifies the default setting for the semiHidden element (§2.7.3.16) which shall be applied to any style made available by the hosting application which is not explicitly defined in the current document. This setting shall be overridden for every style for which a latent style exception (§2.7.3.8) exists.

If this element is omitted, the default semiHidden state for all latent styles in the current document shall be false.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall not be marked as semi-hidden. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defSemiHIdden="false"> …</w:latentStyles>

The defSemiHidden attribute specifies that all latent styles in the current document shall have a semiHidden element setting of false by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

defUIPriority (Default User Interface Priority Setting)

Specifies the default setting for the uiPriority element (§2.7.3.19) which shall be applied to any style made available by the hosting application which is not explicitly defined in the current document. This setting shall be overridden for every style for which a latent style exception (§2.7.3.8) exists.

If this element is omitted, the default uiPriority state for all latent styles in the current document shall be 99.

<w:latentStyles … w:defUIPriority="10"> …</w:latentStyles>

The defUIPriority attribute specifies that all latent styles in the current document shall have a uiPriority element setting of 10 by default. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

defUnhideWhenUsed (Default Hidden Until Used Setting)

Specifies the default setting for the unhideWhenUsed element (§2.7.3.20) which shall be applied to any style made available by the hosting application which is not explicitly defined in the current document. This setting shall be overridden for every style for which a latent style exception (§2.7.3.8) exists.

If this element is omitted, the default unhideWhenUsed state for all latent styles in the current document shall be false.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall be hidden until they are used in the document's contents. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defUnhideWhenUsed="true"> …</w:latentStyles>

The defUnhideWhenUsed attribute specifies that all latent styles in the current document shall have a unhideWhenUsed element setting of true by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

link (Linked Style Reference)

This element specifies the pairing of styles which comprise a linked style. A linked style is a grouping of a paragraph style and character style which is used in a user interface to allow the same set of formatting properties to be applied:

To the contents of one or more entire paragraphs (i.e. as a paragraph style)

To the contents of one or more runs within a paragraph (i.e. as a character style)

Each style continues to exist independently in the file format as there is both a paragraph and character style present within the styles element (§2.7.3.18), however these two styles shall be merged into one and applied appropriately based on whether they are applied to run(s) or paragraph(s), by referencing the styleId attribute of the paired linked style via this element's val attribute.

If this element is omitted, then this style is not part of a linked style pairing. If no style in the current document specifies the styleId present in the val attribute, then this element shall be ignored.

If a style with this styleId is present, then it shall be subject to the following restrictions:

If the parent style is a table style, then this element shall be ignored.

If the parent style is a paragraph style, then the parent style must be a character style, or this element shall be ignored.

If the parent style is a character style, then the parent style must be a paragraph style, or this element shall be ignored.

If the parent style is a numbering style, then this element shall be ignored.

[Example: Consider a linked style defined as follows in a WordprocessingML document:

<w:style w:type="paragraph" w:styleId="TestParagraphStyle"> <w:link w:val="TestCharacterStyle"/> …</w:style>

<w:style w:type="character" w:styleId="TestCharacterStyle"> <w:link w:val="TestParagraphStyle"/> …</w:style>

This pairing of a paragraph style and a character style are linked via the link element, which is used the reference the styleId of the paragraph style from the character style definition and vice versa. Because this pairing is valid based on the rules above, the resulting combination shall be used as a linked style, which appears as one style in an application, but uses the character and/or paragraph style as appropriate. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

locked (Style Cannot Be Applied)

This element specifies whether an application shall prevent the use of this style when this document is loaded and/or modified. If this element is set, then this style may be used to format existing content (i.e. any content which references this style shall have its properties as normal), but new instances of the style shall be prevented from being applied via all mechanisms associated with that application.

If this element is omitted, then the use of the style shall not be prevented by an application processing this document.

[Example: Consider a style with a primary name of Test Style which should be locked, and prevented from being added to any content in a given document. This requirement would be specified using the following WordprocessingML:

<w:style … w:styleId="TestStyle"> <w:name w:val="Test Style"/> <w:locked/> …</w:style>

The presence of the locked element specifies that this style definition shall new instances of the style shall be prevented from being applied via all mechanisms associated with that application. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

lsdException (Latent Style Exception)

This element specifies the properties which shall be applied a single latent style for this document. Latent styles refer to any set of known style definitions which have not been included in the current document.

<w:latentStyles … w:defLockedState="true"> <w:lsdException w:name="Heading 2" w:locked="false"/></w:latentStyles>

The lsdException element specifies that the latent style with a primary name of Heading 2 shall have a locked state setting of false. end example]

Parent Elements

latentStyles (§2.7.3.5)

Attributes

Description

locked (Latent Style Locking Setting)

Specifies the default setting for the locked element (§2.7.3.7) which shall be applied to the latent style with the matching style name value.

If this element is omitted, the default locked state for this latent style shall be determined by the defLockedState attribute on the parent latentStyles element.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall be locked except for the TestStyle style. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defLockedState="true"> <w:lsdException w:name="TestStyle" w:locked="false"/></w:latentStyles>

The locked attribute on the latent style exception specifies that the TestStyle style shall have a locked element setting of false by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

name (Primary Style Name)

Specifies the primary name for the style which shall inherit this set of latent style property exceptions.

If the current application does not know of an internal primary style with the current name, then this set of latent style exceptions may be ignored.

<w:latentStyles … w:defLockedState="true"> <w:lsdException w:name="TestStyle" w:locked="false"/></w:latentStyles>

The name attribute on the latent style exception specifies that the TestStyle style shall have this set of latent style properties (if the application knows of a style with this name). end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

qFormat (Latent Style Primary Style Setting)

Specifies the default setting for the qFormat element (§2.7.3.14) which shall be applied to the latent style with the matching style name value.

If this element is omitted, the default qFormat state for this latent style shall be determined by the defQFormat attribute on the parent latentStyles element.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall not be primary styles except for the TestStyle style. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defQFormat="false"> <w:lsdException w:name="TestStyle" w:qFormat="true"/></w:latentStyles>

The qFormat attribute on the latent style exception specifies that the TestStyle style shall have a qFormat element setting of true by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

semiHidden (Semi hidden text override)

Specifies the default setting for the semiHidden element (§2.7.3.16) which shall be applied to the latent style with the matching style name value.

If this element is omitted, the default semiHidden state for this latent style shall be determined by the defSemiHidden attribute on the parent latentStyles element.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall not be semi-hidden except for the TestStyle style. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defSemiHidden="false"> <w:lsdException w:name="TestStyle" w:semiHidden="true"/></w:latentStyles>

The semiHidden attribute on the latent style exception specifies that the TestStyle style shall have a semiHidden element setting of true by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

uiPriority (Override default sorting order)

Specifies the default setting for the uiPriority element (§2.7.3.19) which shall be applied to the latent style with the matching style name value.

If this element is omitted, the default uiPriority state for this latent style shall be determined by the defUIPriority attribute on the parent latentStyles element.

[Example: Consider a WordprocessingML document in which all styles which are not stored in the document shall have a priority value of 10 except for the TestStyle style. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defUIPriority="10"> <w:lsdException w:name="TestStyle" w:uiPriority="25"/></w:latentStyles>

The uiPriority attribute on the latent style exception specifies that the TestStyle style shall have a uiPriority element setting of 25 by default. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

unhideWhenUsed (Unhide when used)

Specifies the default setting for the unhideWhenUsed element (§2.7.3.20) which shall be applied to the latent style with the matching style name value.

If this element is omitted, the default unhideWhenUsed state for this latent style shall be determined by the defUnhideWhenUsed attribute on the parent latentStyles element.

[Example: Consider a WordprocessingML document in which all styles are to be hidden until used except for the TestStyle style. This requirement would be specified using latent styles as follows:

<w:latentStyles … w:defUnhideWhenUsed="true"> <w:lsdException w:name="TestStyle" w:unhideWhenUsed="false"/></w:latentStyles>

The unhideWhenUsed attribute on the latent style exception specifies that the TestStyle style shall have an unhideWhenUsed element setting of false by default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

name (Primary Style Name)

This element specifies the primary name for the current style in the document. This name may be used in an application's user interface as desired. The actual primary name for this style is stored in its val attribute.

If present, the alternate style names (§2.7.3.1) shall be used in the user interface in place of the built-in name specified when the appropriate value is set in the stylePaneFormatFilter element (§2.15.1.86).

If this element is omitted, then the style shall not have a primary style name.

[Example: Consider a style with a primary name and two alternate names, defined using the name and aliases elements, as follows:

<w:style w:styleId="TestStyle" … > <w:name w:val="GD20Complex"/> <w:aliases w:val="Regional Growth,Complex Growth"/> …</w:style>

This style specifies that it has the primary name GD20Complex using the name element. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

next (Style For Next Paragraph)

This element specifies the style which shall automatically be applied to a new paragraph created following a paragraph with the parent paragraph style applied. [Note: This setting is typically used when the use of the current style is limited to one paragraph at most, and it would typically be undesirable to apply this style to following paragraphs - for example, a title style may specify that its following paragraphs shall return to regular text formatting. end note]

If this element is specified on a style of any type other than a paragraph style, this element shall be ignored. If no style whose styleId matches the val attribute of this element exists or that style is not a paragraph style, this element shall be ignored.

If this element is omitted, then the following paragraph shall use the same paragraph style as the current paragraph.

[Example: Consider a style defined as follows in a WordprocessingML document:

<w:style w:styleId="TestParagraphStyle" … > <w:name w:val="Test Paragraph Style"/> <w:next w:val="AnotherParagraphStyle"/> <w:rPr> <w:b/> </w:rPr> …</w:style>

This style specifies via the use of the next element that the style for the next paragraph in the document shall be the paragraph style whose styleId attribute value is AnotherParagraphStyle (if such a paragraph style exists). end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

personal (E-Mail Message Text Style)

This element specifies that the parent style, when in use in the context of an e-mail message, was used by default to format all message text from one or more users. [Note: This setting does not provide any additional semantic about the style, but may be used in the context of e-mail to automatically reformat the contents of the e-mail message while ignoring any content to which styles were deliberately applied (since this style was implicitly applied to message text without user interaction). end note]

If this element is specified on a style of any type other than a character style, this element shall be ignored. If no style whose styleId matches the val attribute of this element exists or that style is not a character style, this element shall be ignored.

If this element is omitted, then the current style shall not be considered a message text style in the context of e-mail messages.

[Example: Consider a style defined as follows in a WordprocessingML document:

<w:style w:styleId="EmailText" w:type="character" > <w:name w:val="EmailText"/> <w:personal w:val="true" /> <w:rPr> … </w:rPr></w:style>

This style specifies via the use of the personal element that this style is a style used to format message text in the context of e-mail. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

personalCompose (E-Mail Message Composition Style)

This element specifies that the parent style, when in use in the context of an e-mail message, may be used by default to format new message text within the e-mail message. [Note: This setting does not provide any additional semantic about the style, but may be used in the context of e-mail to automatically format the contents of new test in the e-mail message. end note]

If this element is omitted, then the current style shall not be considered a message composition text style in the context of e-mail messages.

[Example: Consider a style defined as follows in a WordprocessingML document:

<w:style w:styleId="EmailText" w:type="character" > <w:name w:val="EmailText"/> <w:personalCompose w:val="true" /> <w:rPr> … </w:rPr></w:style>

This style specifies via the use of the personalCompose element that this style is a style used to format new message text in the context of e-mail. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

personalReply (E-Mail Message Reply Style)

This element specifies that the parent style, when in use in the context of an e-mail message, may be used by default to format existing message text within the e-mail message when a new reply is generated. [Note: This setting does not provide any additional semantic about the style, but may be used in the context of e-mail to automatically format the contents of existing test in the e-mail message. end note]

If this element is omitted, then the current style shall not be considered a message reply text style in the context of e-mail messages.

[Example: Consider a style defined as follows in a WordprocessingML document:

<w:style w:styleId="EmailText" w:type="character" > <w:name w:val="EmailText"/> <w:personalReply w:val="true" /> <w:rPr> … </w:rPr></w:style>

This style specifies via the use of the personalReply element that this style is a style used to format existing message text in the context of e-mail. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

qFormat (Primary Style)

This element specifies whether this style shall be treated as a primary style when this document is loaded by an application. If this element is set, then this style has been designated as being particularly important for the current document, and this information may be used by an application in any means desired. [Note: This setting does not imply any behavior for the style, only that the style is of particular significance for this document. end note]

If this element is omitted, then the style shall not be considered a primary style for this document.

[Example: Consider a style with a primary name of PrimaryStyleExample that should be treated as a primary style for the document. This requirement would be specified using the following WordprocessingML:

<w:style … w:styleId="PStyle"> <w:name w:val="PrimaryStyleExample"/> <w:qFormat/> …</w:style>

The qFormat element specifies that this style definition shall be treated as a primary style for this document. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

rsid (Revision Identifier for Style Definition)

This element specifies a unique four digit number which shall be used to determine the editing session in which this style definition was last modified. This value shall follow this following constraint: All document elements which specify the same rsid* values must correspond to changes made during the same editing session. An editing session is defined as the period of editing which takes place between any two subsequent save actions. [Note: This setting does not imply any behavior for the style, only that the style was last modified during one particular editing session. This information may be interpreted by an application in any manner desired. end note]

If this element is omitted, then no revision identifier shall be associated with the parent style definition.

[Example: Consider a style with a primary name of PrimaryStyleExample that is defined as follows:

<w:style … w:styleId="PStyle"> <w:name w:val="PrimaryStyleExample"/> <w:rsid w:val="3E412D01"/> …</w:style>

The rsid element specifies that this style definition was last edited in the editing session corresponding to the value 3E412D01. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (Long Hexadecimal Number Value)

Specifies a number value specified as a four digit hexadecimal number), whose contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following value for an attribute of type ST_LongHexNumber: 00BE2C6C.

This value is valid, as it contains four hexadecimal digits, each an encoding of an octet of the actual decimal number value. It may therefore be interpreted as desired in the context of the parent XML element, end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</complexType>

semiHidden (Hide Style From Main User Interface)

This element specifies whether this style shall be hidden from the main user interface when this document is loaded by an application. If this element is set, then this style may be used to format content (i.e. any content which references this style shall have its properties as normal), but the style shall be hidden from the main user interface associated with that application.

[Note: The interpretation of a "main" user interface shall not be dictated by this Office Open XML Standard, and may be defined by an application as appropriate.

This setting is intended to define a style property which allows styles to be seen and modified in an advanced user interface, without exposing the style in a less advanced setting, for example, the style which is used to format the contents of a comment should typically not be shown in a simple user interface (as it is uncommon to want to modify it), but would be inappropriate to hide completely using the hidden element (§2.7.3.4), as very advanced users may want to change its appearance. end note]

If this element is omitted, then the style shall not be required to be hidden from the main user interface.

[Example: Consider a style with a primary name of Comment Style that should not be displayed in the main user interface. This requirement would be specified using the following WordprocessingML:

<w:style … w:styleId="CStyle"> <w:name w:val="Comment Style"/> <w:semiHidden/> …</w:style>

The semiHidden element specifies that this style definition should not be displayed in any main user interface associated with an application which processes this document. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

style (Style Definition)

This element specifies the definition of a single style within a WordprocessingML document. A style is a predefined set of table, numbering, paragraph, and/or character properties which can be applied to regions within a document.

The style definition for any style definition can be divided into three segments:

General style properties

Style type

Type-specific properties

General style properties refers to the set of properties which can be used regardless of the type of style; for example, the style name, additional aliases for the style, a style ID (used by the document content to refer to the style), if style is hidden, if style is locked, etc.

[Example: Consider a style called Heading 1 in a document as follows:

<w:style w:type="paragraph" w:styleId="Heading1"> <w:name w:val="Heading 1"/> <w:basedOn w:val="Normal"/> <w:next w:val="Normal"/> <w:link w:val="Heading1Char"/> <w:priority w:val="1"/> <w:qformat/> <w:rsid w:val="00F303CE"/> …</w:style>

Above the formatting information specific to this style type are a set of general style properties which define information shared by all style types. end example]

Style types refers to the property on a style which defines the type of style created with this style definition. WordprocessingML supports six types of style definitions by the values for the style definition's type attribute:

Paragraph styles

Character styles

Linked styles (paragraph + character) [Note: Accomplished via the link element (§2.7.3.6). end note]

Table styles

Numbering styles

Default paragraph + character properties

[Example: Consider a style called Heading 1 in a document as follows:

The type attribute has a value of paragraph, which indicates that the following style definition is a paragraph style. end example]

Type-specific properties refers to the payload of the style: its formatting information as well as any properties which apply only to that type of style.

[Example: Consider a table style with primary name Normal Table defined as follows:

<w:style w:type="table" w:default="1" w:styleId="TableNormal"> <w:name w:val="Normal Table"/> … <w:tblPr> <w:tblInd w:w="0" w:type="dxa"/> <w:tblCellMar> <w:top w:w="0" w:type="dxa"/> <w:left w:w="108" w:type="dxa"/> <w:bottom w:w="0" w:type="dxa"/> <w:right w:w="108" w:type="dxa"/> </w:tblCellMar> </w:tblPr></w:style>

The tblPr element contains the formatting payload for this table style, which is only applicable to a table style. end example]

Parent Elements

styles (§2.7.3.18)

Child Elements

Subclause

aliases (Alternate Style Names)

§2.7.3.1

autoRedefine (Automatically Merge User Formatting Into Style Definition)

§2.7.3.2

basedOn (Parent Style ID)

§2.7.3.3

hidden (Hide Style From User Interface)

§2.7.3.4

link (Linked Style Reference)

§2.7.3.6

locked (Style Cannot Be Applied)

§2.7.3.7

name (Primary Style Name)

§2.7.3.9

next (Style For Next Paragraph)

§2.7.3.10

personal (E-Mail Message Text Style)

§2.7.3.11

personalCompose (E-Mail Message Composition Style)

§2.7.3.12

personalReply (E-Mail Message Reply Style)

§2.7.3.13

pPr (Style Paragraph Properties)

§2.7.7.2

qFormat (Primary Style)

§2.7.3.14

rPr (Run Properties)

§2.7.8.1

rsid (Revision Identifier for Style Definition)

§2.7.3.15

semiHidden (Hide Style From Main User Interface)

§2.7.3.16

tblPr (Style Table Properties)

§2.7.5.4

tblStylePr (Style Conditional Table Formatting Properties)

§2.7.5.6

tcPr (Style Table Cell Properties)

§2.7.5.8

trPr (Style Table Row Properties)

§2.7.5.11

uiPriority (Optional User Interface Sorting Order)

§2.7.3.19

unhideWhenUsed (Remove Semi-Hidden Property When Style Is Used)

§2.7.3.20

Attributes

Description

customStyle (User-Defined Style)

Specifies that this style is a user-defined style (i.e. it is not a style which was automatically generated by an application). This setting (specifically a value of true or its equivalents) shall not allow the formatting associated with the style to be changed automatically by an application, but may be used to specify that if the associated style ID is known, certain user interface behaviors may be applied to its definition. [Example: The style's primary name may be localized to match the current user interface language. end example]

If this attribute is omitted, then the style shall be assumed to be a built-in style.

[Example: Consider a paragraph style defined as follows:

<w:style w:type="paragraph" w:styleId="MyStyle" w:customStyle="true"> <w:name w:val="My Paragraph Style"/> <w:rPr> <w:b/> </w:rPr></w:style>

This paragraph style specifies that it is a user-defined style using the customStyle attribute's value of true. An application may therefore take action on the style if it has behaviors associated with the style ID MyStyle. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

default (Default Style)

Specifies that this style is the default for this type of style.

This property is used in conjunction with the type attribute to determine the style which is applied to objects that do not explicitly declare a style. [Example: The paragraph style with the default attribute set is the paragraph style applied to all paragraphs which do not explicitly reference a paragraph style using the pStyle element (§2.3.1.27). end example]

If this attribute is not specified for any style, then no properties shall be applied to objects of the specified type. If this attribute is specified by multiple styles, then the last instance of a style with this property shall be used.

[Example: Consider a paragraph style defined as follows:

<w:style w:type="paragraph" w:default="1" w:styleId="MyStyle" > <w:name w:val="My Paragraph Style"/> <w:rPr> <w:b/> </w:rPr></w:style>

This paragraph style specifies that it is the default paragraph style, and therefore all paragraphs which do not explicitly reference a paragraph style shall have this style applied.

For example, consider the following paragraphs from the same WordprocessingML document:

<w:p> <w:pPr> <w:pStyle w:val="Normal"/> </w:pPr> …</w:p>

<w:p> …</w:p>

The contents of the first paragraph shall have the Normal paragraph style applied to them, while the contents of the second paragraph shall have the MyStyle paragraph style applied, since it does not explicitly reference a paragraph style and therefore inherits the default. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

styleId (Style ID)

Specifies a unique identifier for the parent style definition. This identifier shall be used in multiple contexts to uniquely reference this style definition within the document.

[Example: The following are examples of elements which reference a style via its styleId attribute value:

To reference a style from content using elements like the pStyle element (§2.3.1.27), rStyle element (§2.3.2.27), and the tblStyle element (§2.4.59) for paragraphs, runs, and tables, respectively.

To link the paragraph and character versions of a style via the link element (§2.7.3.6)

To reference the parent style for style inheritance via the basedOn element (§2.7.3.3)

end example]

If multiple style definitions each declare the same value for their styleId, then the first such instance shall keep its current identifier with all other instances being reassigned in any manner desired. This reassignment shall not require references to those style definitions to be 'repaired' in the content (i.e. some content may lose its style definition information, since the document was ill-formed).

If this attribute is not specified, then a style ID may be assigned in any manner desired.

[Example: Consider a paragraph style defined as follows:

<w:style w:type="paragraph" w:styleId="MyStyle" > <w:name w:val="My Paragraph Style"/> <w:rPr> <w:b/> </w:rPr></w:style>

This paragraph style specifies that its style identifier shall be MyStyle using the styleId attribute.

Now consider the following paragraphs from the same WordprocessingML document:

<w:p> <w:pPr> <w:pStyle w:val="MyStyle"/> </w:pPr> …</w:p>

<w:p> …</w:p>

The contents of the first paragraph shall have the bold paragraph property applied to them because their paragraph properties specify that they shall inherit the paragraph style whose styleId is MyStyle therefore inheriting its properties using the rules of the style hierarchy. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

type (Style Type)

Specifies the type of style definition defined by this element. WordprocessingML supports six types of style definitions:

Paragraph styles

Character styles

Table styles

Numbering styles

Linked styles (paragraph + character)

Default paragraph + character properties

Each of the first four types corresponds to a different value in this attribute, and therefore defines the type of the current style. [Note: The last two types are unique in that they are not simply a style type: a linked style is a pairing of a character and paragraph style via the link element (§2.7.3.6); and the document default properties are defined via the docDefaults element (§2.7.4.1). end note]

If this attribute is not specified, then the default value shall be assumed to be paragraph.

[Example: Consider a style defined as follows:

<w:style w:type="paragraph" … > <w:name w:val="My Paragraph Style"/> <w:rPr> <w:b/> </w:rPr></w:style>

The type attribute value of paragraph specifies that this style definition creates a paragraph style. end example]

The possible values for this attribute are defined by the ST_StyleType simple type (§2.18.90).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

styles (Style Definitions)

This element specifies all of the style information stored in the WordprocessingML document: style definitions as well as latent style information.

Parent Elements

Root element of WordprocessingML Style Definitions part

Child Elements

Subclause

docDefaults (Document Default Paragraph and Run Properties)

§2.7.4.1

latentStyles (Latent Style Information)

§2.7.3.5

style (Style Definition)

§2.7.3.17

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

uiPriority (Optional User Interface Sorting Order)

This element specifies a number which may be used to sort the set of style definitions in a user interface when this document is loaded by an application and the recommended setting is specified in the stylePaneSortMethod element (§2.15.1.87). If this element is set, then this priority shall be used to sort all available styles in ascending value order.

If this element is omitted, then the style shall not have an associated priority value and shall be sorted to the end of the list of style definitions (more or less equivalent to a priority value of infinity) when the recommended sort order setting is specified.

[Example: Consider a style with a primary name of Comment Style that should have an associated priority value of ten. This requirement would be specified using the following WordprocessingML:

<w:style … w:styleId="CStyle"> <w:name w:val="Comment Style"/> <w:uiPriority w:val="10"/> …</w:style>

The uiPriority element specifies that this style definition should be sorted into the list of styles using a value of 10 when the styles are listed in recommended order using the stylePaneSortMethod element (§2.15.1.87). end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

unhideWhenUsed (Remove Semi-Hidden Property When Style Is Used)

This element specifies whether the semiHidden property (§2.7.3.16) shall be removed when this style is used by the content of the document. If this element is set, then an application shall ensure that even if the semiHidden element is specified on a style, that this property is removed when the document is resaved if the style is referenced by any content in the document.

If this element is omitted, then the style shall not automatically lose the semi-hidden property when it is used in the document contents.

[Example: Consider a style with a primary name of Test Paragraph Style that should not be displayed in the main user interface until it is used. This requirement would be specified using the following WordprocessingML:

<w:style … w:styleId="TestStyle"> <w:name w:val="Test Paragraph Style"/> <w:semiHidden/> <w:unhideWhenUsed/> …</w:style>

The unhideWhenUsed element specifies that this style definition should not be displayed in any main user interface associated with an application which processes this document until it is referenced by document content. If a paragraph was added to the document which referenced this style:

<w:p> <w:pPr> <w:pStyle w:val="TestStyle"/> </w:pPr> …</w:p>

This style is now referenced by the document's contents and would have the semiHidden element removed on save. end example]

Parent Elements

style (§2.7.3.17)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

Document Defaults

The first formatting information which is applied to all regions of text in a WordprocessingML document when that document is displayed is the document defaults. The document defaults specify the default set of properties which shall be inherited by every paragraph and run of text within all stories of the current WordprocessingML document. If no other formatting information was referenced by that text, these properties would solely define the formatting of the resulting text.

[Example: Consider the following fragment from the main document part of a WordprocessingML document:

<w:body> <w:p> <w:r> <w:t>Hello world!</w:t> </w:r> </w:p></w:body>

This paragraph and run of text both specify no formatting information (i.e. the paragraph and run possess neither a pPr element nor an rPr element respectively). Therefore, the only formatting applied to this text shall be the formatting in the document defaults which is applied to all paragraphs and runs in the document.

Note that this does not imply that these properties are only applied to text with no formatting - they are rather applied to all text before all other formatting (and in this case, there is no other formatting). end example]

docDefaults (Document Default Paragraph and Run Properties)

This element specifies the set of default paragraph and run properties which shall be applied to every paragraph and run in the current WordprocessingML document. These properties are applied first in the style hierarchy; therefore they are superseded by any further conflicting formatting, but apply if no further formatting is present.

If this element is omitted, then the document defaults shall be application-defined by the hosting application.

[Example: Consider the following definition for the document defaults for a WordprocessingML document:

<w:docDefaults> <w:pPrDefault> <w:pPr> <w:jc w:val="center"/> </w:pPr> </w:pPrDefault> <w:rPrDefault> <w:rPr> <w:b/> </w::rPr> </w:rPrDefault></w:docDefaults>

The child elements of docDefaults specify a default paragraph property of centered text and a default run property of bold text. Applying this formatting to the following fragment from the main document part of the same document:

<w:body> <w:p> <w:r> <w:t>Hello world!</w:t> </w:r> </w:p></w:body>

This paragraph contains no formatting properties, therefore, using the style hierarchy the document default paragraph and run properties are applied as specified within the docDefaults element and the resulting paragraph is centered as specified in the jc element (§2.3.1.13) as well as bold as specified via the b element (§2.3.2.1). end example]

Parent Elements

styles (§2.7.3.18)

Child Elements

Subclause

pPrDefault (Default Paragraph Properties)

§2.7.4.3

rPrDefault (Default Run Properties)

§2.7.4.5

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

pPr (Paragraph Properties)

This element specifies the set of paragraph properties which comprise the default paragraph properties for the current WordprocessingML document. [Rationale: The reason that a pPr element is present within the pPrDefault element is to allow for easy repurposing of any set of paragraph properties within a WordprocessingML document - since the paragraph properties are always child elements of a single pPr element, that element can simply be relocated in its entirety to the desired new location without additional modifications. end rationale]

If this element is omitted, then the default paragraph properties for the current document are non-existent (i.e. there are no default paragraph properties, and the defaults are therefore application-defined).

[Example: Consider the following definition for the document defaults for a WordprocessingML document:

<w:docDefaults> <w:pPrDefault> <w:pPr> <w:jc w:val="center"/> </w:pPr> </w:pPrDefault> …</w:docDefaults>

The pPr element as a child of the pPrDefault element contains the set of default paragraph properties for this document - in this case, a justification value of center. end example]

Parent Elements

pPrDefault (§2.7.4.3)

Child Elements

Subclause

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

§2.3.1.1

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

§2.3.1.2

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

§2.3.1.3

bidi (Right to Left Paragraph Layout)

§2.3.1.6

cnfStyle (Paragraph Conditional Formatting)

§2.3.1.8

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

§2.3.1.9

divId (Associated HTML div ID)

§2.3.1.10

framePr (Text Frame Properties)

§2.3.1.11

ind (Paragraph Indentation)

§2.3.1.12

jc (Paragraph Alignment)

§2.3.1.13

keepLines (Keep All Lines On One Page)

§2.3.1.14

keepNext (Keep Paragraph With Next Paragraph)

§2.3.1.15

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

§2.3.1.16

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

§2.3.1.18

numPr (Numbering Definition Instance Reference)

§2.3.1.19

outlineLvl (Associated Outline Level)

§2.3.1.20

overflowPunct (Allow Punctuation to Extent Past Text Extents)

§2.3.1.21

pageBreakBefore (Start Paragraph on Next Page)

§2.3.1.23

pBdr (Paragraph Borders)

§2.3.1.24

pPrChange (Revision Information for Paragraph Properties)

§2.13.5.31

pStyle (Referenced Paragraph Style)

§2.3.1.27

rPr (Run Properties for the Paragraph Mark)

§2.3.1.29

sectPr (Section Properties)

§2.6.19

shd (Paragraph Shading)

§2.3.1.31

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

§2.3.1.32

spacing (Spacing Between Lines and Above/Below Paragraph)

§2.3.1.33

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

§2.3.1.34

suppressLineNumbers (Suppress Line Numbers for Paragraph)

§2.3.1.35

suppressOverlap (Prevent Text Frames From Overlapping)

§2.3.1.36

tabs (Set of Custom Tab Stops)

§2.3.1.38

textAlignment (Vertical Character Alignment on Line)

§2.3.1.39

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

§2.3.1.40

textDirection (Paragraph Text Flow Direction)

§2.3.1.41

topLinePunct (Compress Punctuation at Start of a Line)

§2.3.1.43

widowControl (Allow First/Last Line to Display on a Separate Page)

§2.3.1.44

wordWrap (Allow Line Breaking At Character Level)

§2.3.1.45

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

pPrDefault (Default Paragraph Properties)

This element specifies the presence of a set of default paragraph properties for the current document. The actual paragraph properties are stored within the pPr child element of the current element.

If this element is omitted, then the default paragraph properties for the current document are non-existent (i.e. there are no default paragraph properties in the document, and the defaults are therefore application-defined).

[Example: Consider the following definition for the document defaults for a WordprocessingML document:

<w:docDefaults> <w:pPrDefault> <w:pPr> <w:jc w:val="center"/> </w:pPr> </w:pPrDefault> …</w:docDefaults>

The pPrDefault element is a container for the set of default paragraph properties for this document. end example]

Parent Elements

docDefaults (§2.7.4.1)

Child Elements

Subclause

pPr (Paragraph Properties)

§2.7.4.2

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

rPr (Run Properties)

This element specifies the set of run properties which comprise the default run properties for the current WordprocessingML document. [Rationale: The reason that an rPr element is present within the rPrDefault element is to allow for easy repurposing of any set of run properties within a WordprocessingML document - since the run properties are always child elements of a single rPr element, that element can simply be relocated in its entirety to the desired new location without additional modifications. end rationale]

If this element is omitted, then the default run properties for the current document are non-existent (i.e. there are no default run properties, and the defaults are therefore application-defined).

[Example: Consider the following definition for the document defaults for a WordprocessingML document:

<w:docDefaults> … <w:rPrDefault> <w:rPr> <w:b/> </w::rPr> </w:rPrDefault></w:docDefaults>

The rPr element as a child of the rPrDefault element contains the set of default run properties for this document - in this case, bold text. end example]

Parent Elements

rPrDefault (§2.7.4.5)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

rPrDefault (Default Run Properties)

This element specifies the presence of a set of default run properties for the current document. The actual run properties are stored within the rPr child element of the current element.

If this element is omitted, then the default run properties for the current document are non-existent (i.e. there are no default run properties in the document, and the defaults are therefore application-defined).

[Example: Consider the following definition for the document defaults for a WordprocessingML document:

<w:docDefaults> … <w:rPrDefault> <w:rPr> <w:b/> </w::rPr> </w:rPrDefault></w:docDefaults>

The rPrDefault element is a container for the set of default run properties for this document. end example]

Parent Elements

docDefaults (§2.7.4.1)

Child Elements

Subclause

rPr (Run Properties)

§2.7.4.4

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

Table Styles

Table styles are style definitions which apply to the contents of zero or more tables within a document. This definition may imply that the style can only define table properties (properties which apply to the table and its constituent rows and cells), however a table style can also define paragraph properties (properties which apply to the positioning and appearance of paragraphs) as well as character properties (properties which apply to runs) for all of the paragraphs and runs within the specified table in the document.

Table styles can only be referenced by tables within a document, and they must be referenced by the tblStyle element (§2.4.59) within a table’s table properties.

As discussed above, table styles can specify all of the properties that can be applied to a table, as well as paragraph and character properties for the table’s contents. However, unlike other style definitions, table styles allow for the definition of conditional formats for different regions of the table.

These table conditional formats are applied to different regions of the table as follows:

All rows in the table can also have conditional formatting on an alternating row/column basis as well as follows:

When specified, these conditional formats shall be applied in the following order (therefore subsequent formats override properties on previous formats):

Whole table

Banded columns, even column banding

Banded rows, even row banding

First row, last row

First column, last column

Top left, top right, bottom left, bottom right

[Example: Consider a table style Test Table Style defined as follows:

All cells with 1pt table borders on all sides

0.1” cell margins on left and right of cells

0” cell margins on top and bottom of cells

As well as header row specific formatting of

Red shading

Bold text

<w:style w:type="table" w:styleId="TestTableStyle"> <w:name w:val="Test Table Style"/> <w:basedOn w:val="TableNormal"/> <w:priority w:val="99"/> <w:rsid w:val="00340CC4"/> <w:tblPr> <w:tblBorders> <w:top w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:left w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:bottom w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:right w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:insideH w:val="single" w:sz="4" w:space="0" w:color="auto"/> <w:insideV w:val="single" w:sz="4" w:space="0" w:color="auto"/> </w:tblBorders> <w:tblCellMar> <w:top w:w="0" w:type="dxa"/> <w:left w:w="108" w:type="dxa"/> <w:bottom w:w="0" w:type="dxa"/> <w:right w:w="108" w:type="dxa"/> </w:tblCellMar> </w:tblPr> <w:tblStylePr w:type="firstRow"> <w:rPr> <w:b/> </w:rPr> <w:tcPr> <w:shd w:val="clear" w:color="auto" w:fill="ED1C24"/> </w:tcPr> </w:tblStylePr></w:style>

The tblPr element holds the formatting which is applied to the entire table, and the tblStylePr element with a type attribute value of firstRow holds the formatting for the first table row, specifically the bold run property and red cell shading. end example]

An individual instance of a table defines an association with a table style using the tblStyle element in the table’s properties (tblPr), as discussed above. However, individual tables can choose whether to apply the following aspects of the table’s conditional formats individually:

First row

Last row

First column

Last column

Row banding

Column banding

The use or omission conditional formats shall be specified using the tblLook element, which contains a bitmask representing which properties are applied and omitted.

[Example: Consider two tables using the table style Style2; one which specifies that it should only use the header row and footer row conditional formatting properties from the table style, and the other which specifies that it should use the header row, footer row, and banded row conditional formatting:

<w:tbl>

<w:tblPr>

<w:tblStyle w:val="Style2"/>

<w:tblW w:w="0" w:type="auto"/>

<w:tblLook w:val="0660"/>

</w:tblPr>

…

</w:tbl>

…

<w:tbl>

<w:tblPr>

<w:tblStyle w:val="Style2"/>

<w:tblW w:w="0" w:type="auto"/>

<w:tblLook w:val="0460"/>

</w:tblPr>

…

</w:tbl>

The tables each specify the appropriate set of conditional formats using the tblLook element, as seen by the identical table styles in the tblStyle element, and different tblLook values. end example]

pPr (Table Style Conditional Formatting Paragraph Properties)

This element specifies the set of paragraph properties which shall be applied to all paragraphs within a table which match the conditional formatting type specified on the parent tblStylePr element. These properties are applied in the order specified via the style hierarchy.

[Example: Consider a table style which contains conditional formatting for its firstRow, defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> … <w:tblStylePr w:type="firstRow"> <w:pPr> <w:jc w:val="center"/> </w:pPr> … </w:tblStylePr></w:style>

The pPr element specified within the tblStylePr element specifies the set of paragraph properties which shall be applied to all parts of the table which meet the criteria specified by the type value of firstRow - all of the header rows of the table. In this example, the single paragraph property applied is an alignment value of center via the jc element (§2.3.1.13). end example]

Parent Elements

tblStylePr (§2.7.5.6)

Child Elements

Subclause

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

§2.3.1.1

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

§2.3.1.2

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

§2.3.1.3

bidi (Right to Left Paragraph Layout)

§2.3.1.6

cnfStyle (Paragraph Conditional Formatting)

§2.3.1.8

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

§2.3.1.9

divId (Associated HTML div ID)

§2.3.1.10

framePr (Text Frame Properties)

§2.3.1.11

ind (Paragraph Indentation)

§2.3.1.12

jc (Paragraph Alignment)

§2.3.1.13

keepLines (Keep All Lines On One Page)

§2.3.1.14

keepNext (Keep Paragraph With Next Paragraph)

§2.3.1.15

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

§2.3.1.16

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

§2.3.1.18

numPr (Numbering Definition Instance Reference)

§2.3.1.19

outlineLvl (Associated Outline Level)

§2.3.1.20

overflowPunct (Allow Punctuation to Extent Past Text Extents)

§2.3.1.21

pageBreakBefore (Start Paragraph on Next Page)

§2.3.1.23

pBdr (Paragraph Borders)

§2.3.1.24

pPrChange (Revision Information for Paragraph Properties)

§2.13.5.31

pStyle (Referenced Paragraph Style)

§2.3.1.27

rPr (Run Properties for the Paragraph Mark)

§2.3.1.29

sectPr (Section Properties)

§2.6.19

shd (Paragraph Shading)

§2.3.1.31

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

§2.3.1.32

spacing (Spacing Between Lines and Above/Below Paragraph)

§2.3.1.33

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

§2.3.1.34

suppressLineNumbers (Suppress Line Numbers for Paragraph)

§2.3.1.35

suppressOverlap (Prevent Text Frames From Overlapping)

§2.3.1.36

tabs (Set of Custom Tab Stops)

§2.3.1.38

textAlignment (Vertical Character Alignment on Line)

§2.3.1.39

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

§2.3.1.40

textDirection (Paragraph Text Flow Direction)

§2.3.1.41

topLinePunct (Compress Punctuation at Start of a Line)

§2.3.1.43

widowControl (Allow First/Last Line to Display on a Separate Page)

§2.3.1.44

wordWrap (Allow Line Breaking At Character Level)

§2.3.1.45

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

rPr (Table Style Conditional Formatting Run Properties)

This element specifies the set of run properties which shall be applied to all runs within a table which match the conditional formatting type specified on the parent tblStylePr element. These properties are applied in the order specified via the style hierarchy.

[Example: Consider a table style which contains conditional formatting for its firstRow, defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> … <w:tblStylePr w:type="firstRow"> <w:rPr> <w:i/> </w:rPr> … </w:tblStylePr></w:style>

The rPr element specified within the tblStylePr element specifies the set of run properties which shall be applied to all parts of the table which meet the criteria specified by the type value of firstRow - all of the header rows of the table. In this example, the single run property applied is italics via the i element (§2.3.2.14). end example]

Parent Elements

tblStylePr (§2.7.5.6)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

tblPr (Table Style Conditional Formatting Table Properties)

This element specifies the set of table properties which shall be applied to all regions within a table which match the conditional formatting type specified on the parent tblStylePr element. These properties are applied in the order specified via the style hierarchy.

If the current conditional formatting type does not consist of one or more full table rows, then table properties which cannot be applied to a single cell or column [Example: Table justification. end example] may be ignored.

[Example: Consider a table style which contains conditional formatting for its firstRow, defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> … <w:tblStylePr w:type="firstRow"> <w:tblPr> <w:tblCellSpacing w:w="29" w:type="dxa"/> </w:tblPr> … </w:tblStylePr></w:style>

The tblPr element specified within the tblStylePr element specifies the set of table properties which shall be applied to all parts of the table which meet the criteria specified by the type value of firstRow - all of the header rows of the table. In this example, the single table property applied is a default table cell spacing value of 0.02 inches via the tblCellSpacing element (§2.4.43). end example]

Parent Elements

tblStylePr (§2.7.5.6)

Child Elements

Subclause

bidiVisual (Visually Right to Left Table)

§2.4.1

jc (Table Alignment)

§2.4.23

shd (Table Shading)

§2.4.35

tblBorders (Table Borders)

§2.4.38

tblCellMar (Table Cell Margin Defaults)

§2.4.39

tblCellSpacing (Table Cell Spacing Default)

§2.4.43

tblInd (Table Indent from Leading Margin)

§2.4.48

tblLayout (Table Layout)

§2.4.49

tblLook (Table Style Conditional Formatting Settings)

§2.4.51

tblOverlap (Floating Table Allows Other Tables to Overlap)

§2.4.53

tblpPr (Floating Table Positioning)

§2.4.54

tblStyle (Referenced Table Style)

§2.4.59

tblStyleColBandSize (Number of Columns in Column Band)

§2.7.5.5

tblStyleRowBandSize (Number of Rows in Row Band)

§2.7.5.7

tblW (Preferred Table Width)

§2.4.61

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

tblPr (Style Table Properties)

This element specifies the set of table properties which shall be applied to the table. These properties are not conditional and shall always be applied (although they are applied before all conditional formatting properties).

[Example: Consider a table style defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> <w:tblPr> <w:tblCellSpacing w:w="15" w:type="dxa"/> </w:tblPr>

… <w:tblStylePr w:type="firstRow">- <w:tblPr> <w:tblCellSpacing w:w="29" w:type="dxa"/> </w:tblPr> … </w:tblStylePr></w:style>

The tblPr element specified within the style element specifies the set of table properties which shall be applied to all parts of the table. In this example, the single table property applied is a default table cell spacing value of 0.01 inches via the tblCellSpacing element (§2.4.43). end example]

Parent Elements

style (§2.7.3.17)

Child Elements

Subclause

bidiVisual (Visually Right to Left Table)

§2.4.1

jc (Table Alignment)

§2.4.23

shd (Table Shading)

§2.4.35

tblBorders (Table Borders)

§2.4.38

tblCellMar (Table Cell Margin Defaults)

§2.4.39

tblCellSpacing (Table Cell Spacing Default)

§2.4.43

tblInd (Table Indent from Leading Margin)

§2.4.48

tblLayout (Table Layout)

§2.4.49

tblLook (Table Style Conditional Formatting Settings)

§2.4.51

tblOverlap (Floating Table Allows Other Tables to Overlap)

§2.4.53

tblpPr (Floating Table Positioning)

§2.4.54

tblStyle (Referenced Table Style)

§2.4.59

tblStyleColBandSize (Number of Columns in Column Band)

§2.7.5.5

tblStyleRowBandSize (Number of Rows in Row Band)

§2.7.5.7

tblW (Preferred Table Width)

§2.4.61

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

tblStyleColBandSize (Number of Columns in Column Band)

This element specifies the number of columns which shall comprise each a table style column band for this table style. This element determines how many columns constitute each of the column bands for the current table, allowing column band formatting to be applied to groups of columns (rather than just single alternating columns) when the table is formatted.

If this element is omitted, then the default number of columns in a single column band shall be assumed to be 1.

[Example: Consider a table style defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> <w:tblPr> <w:tblStyleRowBandSize w:val="3" /> <w:tblStyleColBandSize w:val="2" /> </w:tblPr> …</w:style>

The tblStyleColBandSize element specifies that the width of each column band shall be 2 columns - therefore band1Vert column banding conditional formatting shall be applied to columns 1 and 2, 5 and 6, etc. in the table. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

tblStylePr (Style Conditional Table Formatting Properties)

This element specifies a set of formatting properties which shall be conditionally applied to the parts of a table which match the requirement specified on the type attribute. These table conditional formats are applied to different regions of the table as follows:

All rows in the table can also have conditional formatting on an alternating row/column basis as well as follows:

When specified, these conditional formats shall be applied in the following order (therefore subsequent formats override properties on previous formats):

Whole table

Banded columns, even column banding

Banded rows, even row banding

First row, last row

First column, last column

Top left, top right, bottom left, bottom right

[Example: Consider a table style which contains conditional formatting, defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> … <w:tblStylePr w:type="firstRow"> <w:tblPr> <w:tblCellSpacing w:w="29" w:type="dxa"/> </w:tblPr> … </w:tblStylePr></w:style>

The tblStylePr element specifies a set of table properties which shall be conditionally applied to all parts of the table which meet the criteria specified by the type attribute (in this case, all heading rows for the current table). end example]

Parent Elements

style (§2.7.3.17)

Child Elements

Subclause

pPr (Table Style Conditional Formatting Paragraph Properties)

§2.7.5.1

rPr (Table Style Conditional Formatting Run Properties)

§2.7.5.2

tblPr (Table Style Conditional Formatting Table Properties)

§2.7.5.3

tcPr (Table Style Conditional Formatting Table Cell Properties)

§2.7.5.9

trPr (Table Style Conditional Formatting Table Row Properties)

§2.7.5.10

Attributes

Description

type (Table Style Conditional Formatting Type)

Specifies the section of the table to which the current conditional formatting properties shall be applied.

[Example: Consider a table style which contains conditional formatting, defined as follows:

<w:style w:type="table" …> … <w:tblStylePr w:type="lastRow"> … </w:tblStylePr></w:style>

The type attribute value of lastRow specifies that this set of conditional formatting properties shall be applied to the last row of the table only. end example]

The possible values for this attribute are defined by the ST_TblStyleOverrideType simple type (§2.18.96).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

tblStyleRowBandSize (Number of Rows in Row Band)

This element specifies the number of rows which shall comprise each a table style row band for this table style. This element determines how many rows constitute each of the row bands for the current table, allowing row band formatting to be applied to groups of rows (rather than just single alternating rows) when the table is formatted.

If this element is omitted, then the default number of rows in a single row band shall be assumed to be 1.

[Example: Consider a table style defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> <w:tblPr> <w:tblStyleRowBandSize w:val="3" /> <w:tblStyleColBandSize w:val="2" /> </w:tblPr> …</w:style>

The tblStyleRowBandSize element specifies that the width of each row band shall be 3 columns - therefore band1Horiz row banding conditional formatting shall be applied to row 1 through 3, 7 through 9, etc. in the table. end example]

Parent Elements

tblPr (§2.7.5.3); tblPr (§2.7.5.4); tblPr (§2.4.55); tblPr (§2.4.56)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

tcPr (Style Table Cell Properties)

This element specifies the set of table cell properties which shall be applied to the table. These properties are not conditional and shall always be applied (although they are applied before all conditional formatting properties).

[Example: Consider a table style defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> <w:tcPr> <w:tcFitText/> </w:tcPr></w:style>

The tcPr element specified within the style element specifies the set of table cell properties which shall be applied to all parts of the table. In this example, the single table cell property applied is the fit text setting via the tcFitText element (§2.4.64). end example]

Parent Elements

style (§2.7.3.17)

Child Elements

Subclause

cellDel (Table Cell Deletion)

§2.13.5.1

cellIns (Table Cell Insertion)

§2.13.5.2

cellMerge (Vertically Merged/Split Table Cells)

§2.13.5.3

cnfStyle (Table Cell Conditional Formatting)

§2.4.7

gridSpan (Grid Columns Spanned by Current Table Cell)

§2.4.13

hideMark (Ignore End Of Cell Marker In Row Height Calculation)

§2.4.15

hMerge (Horizontally Merged Cell)

§2.4.16

noWrap (Don't Wrap Cell Content)

§2.4.28

shd (Table Cell Shading)

§2.4.33

tcBorders (Table Cell Borders)

§2.4.63

tcFitText (Fit Text Within Cell)

§2.4.64

tcMar (Single Table Cell Margins)

§2.4.65

tcPrChange (Revision Information for Table Cell Properties)

§2.13.5.38

tcW (Preferred Table Cell Width)

§2.4.68

textDirection (Table Cell Text Flow Direction)

§2.4.69

vAlign (Table Cell Vertical Alignment)

§2.4.80

vMerge (Vertically Merged Cell)

§2.4.81

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

tcPr (Table Style Conditional Formatting Table Cell Properties)

This element specifies the set of table cell properties which shall be applied to all regions within a table which match the conditional formatting type specified on the parent tblStylePr element. These properties are applied in the order specified via the style hierarchy.

[Example: Consider a table style which contains conditional formatting for its firstRow, defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> … <w:tblStylePr w:type="firstRow"> <w:tcPr> <w:tcBorders> <w:top w:val="nil" /> <w:left w:val="nil" /> <w:bottom w:val="nil" /> <w:right w:val="nil" /> <w:insideH w:val="nil" /> <w:insideV w:val="nil" /> </w:tcBorders> </w:tcPr> … </w:tblStylePr></w:style>

The tcPr element specified within the tblStylePr element specifies the set of table cell properties which shall be applied to all parts of the table which meet the criteria specified by the type value of firstRow - all of the header rows of the table. In this example, the single table cell property applied is a set of table cell borders via the tcBorders element (§2.4.63). In this case, these cell borders simply reset any previous cell borders to nil. end example]

Parent Elements

tblStylePr (§2.7.5.6)

Child Elements

Subclause

cellDel (Table Cell Deletion)

§2.13.5.1

cellIns (Table Cell Insertion)

§2.13.5.2

cellMerge (Vertically Merged/Split Table Cells)

§2.13.5.3

cnfStyle (Table Cell Conditional Formatting)

§2.4.7

gridSpan (Grid Columns Spanned by Current Table Cell)

§2.4.13

hideMark (Ignore End Of Cell Marker In Row Height Calculation)

§2.4.15

hMerge (Horizontally Merged Cell)

§2.4.16

noWrap (Don't Wrap Cell Content)

§2.4.28

shd (Table Cell Shading)

§2.4.33

tcBorders (Table Cell Borders)

§2.4.63

tcFitText (Fit Text Within Cell)

§2.4.64

tcMar (Single Table Cell Margins)

§2.4.65

tcPrChange (Revision Information for Table Cell Properties)

§2.13.5.38

tcW (Preferred Table Cell Width)

§2.4.68

textDirection (Table Cell Text Flow Direction)

§2.4.69

vAlign (Table Cell Vertical Alignment)

§2.4.80

vMerge (Vertically Merged Cell)

§2.4.81

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

trPr (Table Style Conditional Formatting Table Row Properties)

This element specifies the set of table row properties which shall be applied to all rows within a table which match the conditional formatting type specified on the parent tblStylePr element. These properties are applied in the order specified via the style hierarchy.

[Example: Consider a table style which contains conditional formatting for its firstRow, defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> … <w:tblStylePr w:type="firstRow"> <w:trPr> <w:tblHeader/> <w:cantSplit/> </w:trPr> … </w:tblStylePr></w:style>

The trPr element specified within the tblStylePr element specifies the set of table row properties which shall be applied to all rows of the table which meet the criteria specified by the type value of firstRow - all of the header rows of the table. In this example, the table row properties applied are the fact that these rows shall be repeated on each page via the tblHeader element (§2.4.46) and the fact that these rows shall not be split across pages using the cantSplit element (§2.4.6). end example]

Parent Elements

tblStylePr (§2.7.5.6)

Child Elements

Subclause

cantSplit (Table Row Cannot Break Across Pages)

§2.4.6

cnfStyle (Table Row Conditional Formatting)

§2.4.8

del (Deleted Table Row)

§2.13.5.14

divId (Associated HTML div ID)

§2.4.9

gridAfter (Grid Columns After Last Cell)

§2.4.10

gridBefore (Grid Columns Before First Cell)

§2.4.11

hidden (Hidden Table Row Marker)

§2.4.14

ins (Inserted Table Row)

§2.13.5.16

jc (Table Row Alignment)

§2.4.22

tblCellSpacing (Table Row Cell Spacing)

§2.4.42

tblHeader (Repeat Table Row on Every New Page)

§2.4.46

trHeight (Table Row Height)

§2.4.77

trPrChange (Revision Information for Table Row Properties)

§2.13.5.39

wAfter (Preferred Width After Table Row)

§2.4.82

wBefore (Preferred Width Before Table Row)

§2.4.83

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

trPr (Style Table Row Properties)

This element specifies the set of table row properties which shall be applied to the table. These properties are not conditional and shall always be applied (although they are applied before all conditional formatting properties).

[Example: Consider a table style defined as follows:

<w:style w:type="table" w:styleId="exampleTableStyle"> <w:trPr> <w:jc w:val="center"/> </w:trPr></w:style>

The trPr element specified within the style element specifies the set of table row properties which shall be applied to all parts of the table. In this example, the single table row property applied is the alignment setting of center via the jc element (§2.4.22). end example]

Parent Elements

style (§2.7.3.17)

Child Elements

Subclause

cantSplit (Table Row Cannot Break Across Pages)

§2.4.6

cnfStyle (Table Row Conditional Formatting)

§2.4.8

del (Deleted Table Row)

§2.13.5.14

divId (Associated HTML div ID)

§2.4.9

gridAfter (Grid Columns After Last Cell)

§2.4.10

gridBefore (Grid Columns Before First Cell)

§2.4.11

hidden (Hidden Table Row Marker)

§2.4.14

ins (Inserted Table Row)

§2.13.5.16

jc (Table Row Alignment)

§2.4.22

tblCellSpacing (Table Row Cell Spacing)

§2.4.42

tblHeader (Repeat Table Row on Every New Page)

§2.4.46

trHeight (Table Row Height)

§2.4.77

trPrChange (Revision Information for Table Row Properties)

§2.13.5.39

wAfter (Preferred Width After Table Row)

§2.4.82

wBefore (Preferred Width Before Table Row)

§2.4.83

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

Numbering Styles

Numbering styles are style definitions which specify common style properties for a multi-level numbering format within a document. This means that a numbering style defines only a single paragraph property: a reference to a numbering definition stored in the document’s numbering part, using the numPr element.

Unlike paragraph and character styles, numbering styles are never directly referenced by content in the document – instead, an abstract numbering definition (covered in the numbering section) specifies that it is actually the underlying numbering information for a numbering style.

[Example: Consider a numbering style “Test Numbering Style”:

<w:style w:type="numbering" w:styleId="TestNumberingStyle">

<w:name w:val="Test Numbering Style" />

<w:priority w:val="99" />

<w:rsid w:val="0045009F" />

<w:pPr>

<w:numPr>

<w:numId w:val="1" />

</w:numPr>

</w:pPr>

</w:style>

The only information specified in the numbering style definition is a reference to the numbering definition for the numbering information which is defined by this numbering style. end example]

Paragraph Styles

Paragraph styles are styles which apply to the contents of an entire paragraph as well as the paragraph mark. This definition implies that the style can define both character properties (properties which apply to text within the document) as well as paragraph properties (properties which apply to the positioning and appearance of the paragraph). Paragraph styles cannot be referenced by runs within a document; they must be referenced by the pStyle element (§2.3.1.27) within a paragraph’s paragraph properties element.

A paragraph style has three defining type-specific characteristics:

The type attribute on the style has a value of paragraph, which indicates that the following style definition is a paragraph style.

The next element defines an editing behavior which supplies the paragraph style to be automatically applied to the next paragraph when ENTER is pressed at the end of a paragraph of this style.

The style specifies both paragraph-level and character-level properties using the pPr and rPr elements, respectively. In this case, the run properties are the set of properties applied to each run in the paragraph.

The paragraph style is then applied to paragraphs by referencing the styleId attribute value for this style in the paragraph properties’ pStyle element.

[Example: Consider a paragraph style titled "Test Paragraph Style" which defines; font = Algerian, font size = 20; font color = red; paragraph spacing = double; paragraph indent = 1” (first line only). The resulting style definition would be:

<w:style w:type="paragraph" w:styleId="TestParagraphStyle"> <w:name w:val="Test Paragraph Style"/> <w:qformat/> <w:rsid w:val="00F85845"/> <w:pPr> <w:spacing w:line="480" w:lineRule="auto"/> <w:ind w:firstLine="1440"/> </w:pPr> <w:rPr> <w:rFonts w:ascii="Algerian" w:hAnsi="Algerian"/> <w:color w:val="ED1C24"/> <w:sz w:val="40"/> </w:rPr></w:style>

Notice that the character properties for the style are under the rPr element, and the paragraph properties are under the pPr element.

The document content for a paragraph of this style would be:

<w:p> <w:pPr> <w:pStyle w:val="TestParagraphStyle"/> </w:pPr> <w:r> <w:t xml:space="preserve">Here is some fancy Text</w:t> </w:r></w:p>

The pStyle element links the paragraph with the style definition. end example]

Numbering in Paragraph Styles

When a paragraph style references a numbering definition and level which shall also be applied, that reference shall be done in a way slightly different from the typical numbering reference as follows:

When a numbering reference is created as direct formatting, that reference consists of a reference to the numbering definition instance + a numbering level

[Example: Consider a numbered paragraph in a WordprocessingML document whose numbering is a result of direct formatting (formatting not from a style). This numbered paragraph may be represented using the following WordprocessingML:

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="5" /> </w:numPr> </w:pPr> <w:r> <w:t>Level one</w:t> </w:r></w:p>

The numPr element contains two pieces of information:

The numId element (the numbering definition instance referenced)

The ilvl element (the level within that numbering definition)

end example]

When numbering is done as part of a paragraph style, that reference consists of a reference to the numbering definition only. The numbering definition then in turn has a reference to the paragraph style on the level which shall be associated with this style

[Example: Consider a numbered paragraph in a WordprocessingML document whose numbering is a result of a paragraph style. This numbered paragraph may be represented using the following WordprocessingML:

<w:p> <w:pPr> <w:pStyle w:val="TestParagraphStyle"/> </w:pPr> <w:r> <w:t>Level one</w:t> </w:r></w:p>

The paragraph references the style via its styleId attribute, which itself looks like this:

<w:style w:styleId="TestParagraphStyle" … > <w:pPr> <w:numPr> <w:numId w:val="5" /> </w:numPr> </w:pPr></w:style>

The numPr element contains one piece of information:

The numId element (the numbering definition instance referenced)

Obviously, this is insufficient to apply the numbering since we need to know which level to apply, so this information is specified on the appropriate level using the pStyle element:

<w:abstractNum w:abstractNumId="1">

...

<w:lvl w:ilvl="0">

...

<w:pStyle w:val="TestParagraphStyle" />

<w:pPr>

<w:tabs>

<w:tab w:val="num" w:pos="720" />

</w:tabs>

<w:ind w:left="720" w:hanging="360" />

</w:pPr>

...

</w:lvl>

</w:abstractNum>

In this case, level 0 of the underlying abstract numbering definition specifies that it is associated with paragraph style TestParagraphStyle, so this level of the numbering shall be applied along with the paragraph style. end example]

When numbering is referenced by a paragraph style, its properties shall be applied before the style's properties (the style's paragraph properties shall override the numbering level's paragraph properties).

pPr (Style Paragraph Properties)

This element specifies the set of paragraph properties which shall be applied to the paragraph.

[Example: Consider a paragraph style defined as follows:

<w:style w:type="paragraph" w:styleId="TestParaStyle"> <w:pPr> <w:keepLines/> </w:pPr></w:style>

The pPr element specified within the style element specifies the set of paragraph properties which shall be applied to the referencing paragraph. In this example, the single paragraph property applied is the fact that the paragraph shall be displayed on a single page via the keepLines element (§2.3.1.14). end example]

Parent Elements

style (§2.7.3.17)

Child Elements

Subclause

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

§2.3.1.1

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

§2.3.1.2

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

§2.3.1.3

bidi (Right to Left Paragraph Layout)

§2.3.1.6

cnfStyle (Paragraph Conditional Formatting)

§2.3.1.8

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

§2.3.1.9

divId (Associated HTML div ID)

§2.3.1.10

framePr (Text Frame Properties)

§2.3.1.11

ind (Paragraph Indentation)

§2.3.1.12

jc (Paragraph Alignment)

§2.3.1.13

keepLines (Keep All Lines On One Page)

§2.3.1.14

keepNext (Keep Paragraph With Next Paragraph)

§2.3.1.15

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

§2.3.1.16

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

§2.3.1.18

numPr (Numbering Definition Instance Reference)

§2.3.1.19

outlineLvl (Associated Outline Level)

§2.3.1.20

overflowPunct (Allow Punctuation to Extent Past Text Extents)

§2.3.1.21

pageBreakBefore (Start Paragraph on Next Page)

§2.3.1.23

pBdr (Paragraph Borders)

§2.3.1.24

pPrChange (Revision Information for Paragraph Properties)

§2.13.5.31

pStyle (Referenced Paragraph Style)

§2.3.1.27

rPr (Run Properties for the Paragraph Mark)

§2.3.1.29

sectPr (Section Properties)

§2.6.19

shd (Paragraph Shading)

§2.3.1.31

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

§2.3.1.32

spacing (Spacing Between Lines and Above/Below Paragraph)

§2.3.1.33

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

§2.3.1.34

suppressLineNumbers (Suppress Line Numbers for Paragraph)

§2.3.1.35

suppressOverlap (Prevent Text Frames From Overlapping)

§2.3.1.36

tabs (Set of Custom Tab Stops)

§2.3.1.38

textAlignment (Vertical Character Alignment on Line)

§2.3.1.39

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

§2.3.1.40

textDirection (Paragraph Text Flow Direction)

§2.3.1.41

topLinePunct (Compress Punctuation at Start of a Line)

§2.3.1.43

widowControl (Allow First/Last Line to Display on a Separate Page)

§2.3.1.44

wordWrap (Allow Line Breaking At Character Level)

§2.3.1.45

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

Run (Character) Styles

Character styles are styles which apply to the contents of one or more runs of text within a document’s contents. This definition implies that the style can only define character properties (properties which apply to text within a paragraph) because it cannot be applied to paragraphs. Character styles can only be referenced by runs within a document, and they must be referenced by the rStyle element within a run’s run properties element.

A character style has two defining type-specific characteristics:

The type attribute on the style has a value of character, which indicates that the following style definition is a character style.

The style specifies only character-level properties using the rPr element. In this case, the run properties are the set of properties applied to each run which is of this style.

The character style is then applied to runs by referencing the styleId attribute value for this style in the run properties’ rStyle element.

[Example: Consider a character style titled "Test Character Style" which defines; font = Courier New, font color = yellow; underline. The resulting style definition would be:

<w:style w:type="character" w:styleId="TestCharacterStyle"> <w:name w:val="Test Character Style"/> <w:priority w:val="99"/> <w:qformat/> <w:rsid w:val="00E77BF0"/> <w:rPr> <w:rFonts w:ascii="Courier New" w:hAnsi="Courier New"/> <w:color w:val="FFF200"/> <w:u w:val="single"/> </w:rPr></w:style>

Notice that the character properties applied using this style are under the rPr element. The document content for a paragraph with a run of this style would be:

<w:p> <w:r> <w:t xml:space="preserve">The following text is in the </w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="TestCharacterStyle"/> </w:rPr> <w:t>character style</w:t> </w:r> <w:r> <w:t>.</w:t> </w:r></w:p>

The rStyle element in the second run links that run with the style definition, inheriting the formatting properties for that run. end example]

rPr (Run Properties)

This element specifies the set of run properties which shall be applied to the run.

[Example: Consider a character style defined as follows:

<w:style w:type="character" w:styleId="TestCharStyle"> <w:rPr> <w:dstrike/> </w:rPr></w:style>

The rPr element specified within the style element specifies the set of run properties which shall be applied to the referencing run. In this example, the single run property applied is the fact that the paragraph shall be displayed with double strikethrough via the dstrike element (§2.3.2.7). end example]

Parent Elements

style (§2.7.3.17)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

Fonts

The next component of a WordprocessingML document is storing information about the fonts used in the document. WordprocessingML stores two pieces of information about fonts:

(optionally) Information about the font to enable font substitution. Font substitution is a process by which an application, when it cannot locate a specific font, attempts to locate the closest possible match to the intended appearance of the font

(optionally) One or more embedded forms of the font for use on systems which do not have access to the font. When fonts are embedded, they are obfuscated to ensure that they are only used to view the contents of the document in which they are embedded, and for no other purpose.

[Example: Consider the following information stored in a document's font table part:

<w:fonts> <w:font w:name="Times New Roman"> <w:panose1 w:val="02020603050405020304" /> <w:charset w:val="00" /> <w:family w:val="roman" /> <w:pitch w:val="variable" /> <w:sig w:usb0="20002A87" w:usb1="80000000" w:usb2="00000008" w:usb3="00000000" w:csb0="000001FF" w:csb1="00000000" />

<w:embedRegular r:id="rId10" w:fontKey="{302EE813-EB4A-4642-A93A-89EF99B2457E}" /> </w:font></w:fonts>

The font table contains information about the Times New Roman font; specifically, information used to locate a substitute font when it is not available and a relationship to the embedded form of the regular form of the font. end example]

Font Embedding

Within a WordprocessingML document, font embedding refers to a process in which the some or all of the fonts used in the current document are included in that document such that it can be guaranteed that they are available for use when the document is subsequently opened.

Embedded fonts are stored in an Embedded Font part within the package.

When a font is embedded within a WordprocessingML document, it shall be obfuscated to prevent it from being used outside of this document. This obfuscation shall be done using the following algorithm:

Generate a GUID, which will be used and stored as the obfuscation key

Reverse the order of the bytes in the GUID (i.e. Big Endian ordering)

XOR the value with the first 32 bytes of the binary: once against 0-15, once against 16-31

Store the resulting file in the document, and store the obfuscation key in the fontKey attribute

[Example: Consider a font to be embedded whose first 32 bytes are as follows:

To obfuscate this font for storage:

Generate a GUID (e.g. 001B70DC-AA60-4AD5-90EC-18A0948E1EAE)

Reverse its order (e.g. AE1E8E94-A018-EC90-D54A-60AADC701B00)

XOR the GUID with the first and second 16 bytes

The resulting 32 bytes would be:

end example]

To retrieve an obfuscated font for viewing the content of this document only, repeat the procedure above to retrieve the original font.

Elements

The following elements comprise the content of the font table:

altName (Alternate Names for Font)

This element specifies a set of alternative names which may be used to locate the font specified by the parent element. This set of alternative names is stored in a comma-delimited list, with all adjacent commas ignored (i.e. a value of Name A, Name B is equivalent to Name A,,,,,,,,, Name B).

When an application cannot locate a font using the primary name stored on the font attribute of the font element (§2.8.2.10), it should use each alternate name in term to attempt to locate the font, and use the first font for which is locates a match.

If this element is omitted, then no alternate names are present for the parent font.

[Example: Consider the following information stored for a single font:

<w:font w:name="SimSun"> <w:altName w:val="Arial Unicode MS" /> …</w:font>

The altName element specifies that when no font with a name of SimSun (the primary font name) can be located, that applications should attempt to locate a font with the name Arial Unicode MS before doing substitution based on the font metrics. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

charset (Character Set Supported By Font)

This element specifies the character set which is supported by the parent font. This information may be used as defined in font substitution logic to locate an appropriate substitute font when this font is not available. This information is determined by querying the font when present and shall not be modified when the font is not available.

The value of this element shall be interpreted as follows:

Value

Description

0x00

Specifies the ANSI character set.

0x01

Specifies the default character set.

0x02

Specifies the Symbol character set.

0x4D

Specifies a Macintosh (Standard Roman) character set.

0x80

Specifies the JIS character set.

0x81

Specifies the Hangul character set.

0x82

Specifies a Johab character set.

0x86

Specifies the GB-2312 character set.

0x88

Specifies the Chinese Big Five character set.

0xA1

Specifies a Greek character set.

0xA2

Specifies a Turkish character set.

0xA3

Specifies a Vietnamese character set.

0xB1

Specifies a Hebrew character set.

0xB2

Specifies an Arabic character set.

0xBA

Specifies a Baltic character set.

0xCC

Specifies a Russian character set.

0xDE

Specifies a Thai character set.

0xEE

Specifies an Eastern European character set.

0xFF

Specifies an OEM character set not defined by this Office Open XML Standard.

Any other value

Application-defined, may be ignored.

If this element is not present, then the character set for this font shall be assumed to be the ANSI character set.

[Example: Consider the following information stored for a single font:

<w:font w:name="SimSun"> <w:charset w:val="86" /> …</w:font>

The charset element specifies via its val attribute value of 86 that this font uses the GB-2312 character set. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

val (Value)

Specifies a value specified as single octet (two digit) hexadecimal number whose contents are interpreted based on the context of the parent XML element.

[Example: Consider the following value for an attribute of type ST_UCharHexNumber:

<w:… w:val="BE"/>

This value is valid, as it contains two hexadecimal digits, an encoding of an octet of the actual decimal number value. end example]

The possible values for this attribute are defined by the ST_UcharHexNumber simple type (§2.18.106).

The following XML Schema fragment defines the contents of this element:

</complexType>

embedBold (Bold Style Font Style Embedding)

This element specifies information about the embedded font storage for the bold form of a font, when it is embedded. This form is used when bold is applied to a text run.

If this element is omitted, then no bold form of the font is stored in the document. The relationship targeted by the id attribute must be of the embedded font type, or the document shall be considered to be invalid.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedBold r:id="rId10" /></w:font>

The embedBold element specifies that the embedded font targeted with the relationship with ID rId10 may be used to retrieve the bold form of the embedded Arial font. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

fontKey (Embedded Font Obfuscation Key)

Specifies the key which was used to obfuscate this embedded font. This key may be used to retrieve the embedded font for the purposes of viewing this WordprocessingML document only, using the algorithm described in §2.8.1.

If this attribute is omitted, then no key is provided for this font.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:fontKey="{302EE813-EB4A-4642-A93A-89EF99B2457E}" /></w:font>

The fontKey attribute has a value of {302EE813-EB4A-4642-A93A-89EF99B2457E}, therefore the embedded Arial font targeted with the relationship with ID rId10 may be retrieved if needed by using this key and the algorithm above. end example]

The possible values for this attribute are defined by the ST_Guid simple type (§2.18.39).

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

subsetted (Embedded Font Is Subsetted)

Specifies that the embedded font targeted by the id attribute has been subsetted. Subsetting is a mechanism by which only the glyphs used in the contents of this WordprocessingML document are stored in an embedded font, in order to prevent the file from becoming unnecessarily large from the use of a small number of glyphs from a large embedded font.

If this attribute is omitted, then the embedded font target by the id attribute shall not be handled as though it is subsetted.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file after subsetting. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:subsetted="true" /></w:font>

The subsetted attribute has a value of true, therefore the embedded Arial font targeted with the relationship with ID rId10 shall be treated as a subsetted font. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

embedBoldItalic (Bold Italic Font Style Embedding)

This element specifies information about the embedded font storage for the bold italic form of a font, when it is embedded. This form is used when bold and italics are applied to a text run.

If this element is omitted, then no bold italic form of the font is stored in the document.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedBoldItalic r:id="rId11" /></w:font>

The embedBoldItalic element specifies that the embedded font targeted with the relationship with ID rId11 may be used to retrieve the bold italic form of the embedded Arial font. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

fontKey (Embedded Font Obfuscation Key)

If this attribute is omitted, then no key is provided for this font.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:fontKey="{302EE813-EB4A-4642-A93A-89EF99B2457E}" /></w:font>

The possible values for this attribute are defined by the ST_Guid simple type (§2.18.39).

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

subsetted (Embedded Font Is Subsetted)

If this attribute is omitted, then the embedded font target by the id attribute shall not be handled as though it is subsetted.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file after subsetting. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:subsetted="true" /></w:font>

The subsetted attribute has a value of true, therefore the embedded Arial font targeted with the relationship with ID rId10 shall be treated as a subsetted font. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

embedItalic (Italic Font Style Embedding)

This element specifies information about the embedded font storage for the italic form of a font, when it is embedded. This form is used when italics are applied to a text run.

If this element is omitted, then no italic form of the font is stored in the document.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedItalic r:id="rId12" /></w:font>

The embedItalic element specifies that the embedded font targeted with the relationship with ID rId12 may be used to retrieve the italic form of the embedded Arial font. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

fontKey (Embedded Font Obfuscation Key)

If this attribute is omitted, then no key is provided for this font.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:fontKey="{302EE813-EB4A-4642-A93A-89EF99B2457E}" /></w:font>

The possible values for this attribute are defined by the ST_Guid simple type (§2.18.39).

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

subsetted (Embedded Font Is Subsetted)

If this attribute is omitted, then the embedded font target by the id attribute shall not be handled as though it is subsetted.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file after subsetting. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:subsetted="true" /></w:font>

The subsetted attribute has a value of true, therefore the embedded Arial font targeted with the relationship with ID rId10 shall be treated as a subsetted font. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

embedRegular (Regular Font Style Embedding)

This element specifies information about the embedded font storage for the regular form of a font, when it is embedded. This form is used when neither bold nor italics is applied to a text run.

If this element is omitted, then no regular form of the font is stored in the document.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId13" /></w:font>

The embedRegular element specifies that the embedded font targeted with the relationship with ID rId13 may be used to retrieve the regular form of the embedded Arial font. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

fontKey (Embedded Font Obfuscation Key)

If this attribute is omitted, then no key is provided for this font.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:fontKey="{302EE813-EB4A-4642-A93A-89EF99B2457E}" /></w:font>

The possible values for this attribute are defined by the ST_Guid simple type (§2.18.39).

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

subsetted (Embedded Font Is Subsetted)

If this attribute is omitted, then the embedded font target by the id attribute shall not be handled as though it is subsetted.

[Example: Consider a WordprocessingML document in which the Arial font has been embedded in the file after subsetting. This status would be specified using the following WordprocessingML:

<w:font w:name="Arial"> … <w:embedRegular r:id="rId10" w:subsetted="true" /></w:font>

The subsetted attribute has a value of true, therefore the embedded Arial font targeted with the relationship with ID rId10 shall be treated as a subsetted font. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

embedSystemFonts (Embed Common System Fonts)

This element specifies that applications shall embed common system fonts when they are in use and font embedding is enabled for this document using the embedTrueTypeFonts element (§2.8.2.8). Common system fonts refer to a set of fonts which are typically always present on a machine, and are not defined by this Office Open XML Standard.

If this element is omitted, then the set of fonts defined as common system fonts should not be embedded in the current document when font embedded is turned on. If the embedTrueTypeFonts element is omitted or false, then this setting has no effect.

[Example: Consider a WordprocessingML document that specifies that it shall embed fonts, including common system fonts. This requirement would be specified using the following WordprocessingML in the document settings part:

<w:embedTrueTypeFonts w:val="true" /><w:embedSystemFonts w:val="true"/>

The embedSystemFonts element's val attribute has a value of true specifying that common system fonts should be included in this document when they are used. end example]

Parent Elements

settings (§2.15.1.78)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

embedTrueTypeFonts (Embed TrueType Fonts)

This element specifies that applications shall embed the fonts in use in this document when it is saved. These fonts shall be embedded subject to the algorithm specified in §2.8.1.

If this element is omitted, then fonts in use should not be embedded in the current document.

<w:embedTrueTypeFonts w:val="true" /><w:embedSystemFonts w:val="true"/>

The embedTrueType element's val attribute has a value of true specifying that fonts should be embedded in this document when they are used. end example]

Parent Elements

settings (§2.15.1.78)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

family (Font Family)

This element specifies the font family of the current font. This information may be used as defined in font substitution logic to locate an appropriate substitute font when this font is not available. This information is determined by querying the font when present and shall not be modified when the font is not available.

If this element is omitted, then its value shall be assumed to be auto.

[Example: Consider the following information stored for a single font:

<w:font w:name="Calibri"> <w:family w:val="swiss" /> …</w:font>

The family element specifies via its val attribute value of swiss that this font is part of the Swiss family. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

val (Font Family Value)

Specifies the font family for the parent font.

[Example: Consider the following information stored for a single font:

<w:font w:name="Times New Roman"> <w:family w:val="roman" /> …</w:font>

The val attribute value of swiss that this font is part of the Roman family. end example]

The possible values for this attribute are defined by the ST_FontFamily simple type (§2.18.34).

The following XML Schema fragment defines the contents of this element:

</complexType>

font (Properties for a Single Font)

This element specifies the properties for one of the fonts used in this document. A font element shall be written out for each font face used in the document, and includes:

The name of the font as used in the document's stories

(optionally) Font metrics allowing other applications to locate appropriate substitute fonts as needed

(optionally) Embedded forms of the font

[Example: Consider the following information stored for a single font:

<w:font w:name="Times New Roman"> <w:panose1 w:val="02020603050405020304" /> <w:charset w:val="00" /> <w:family w:val="roman" /> <w:pitch w:val="variable" /> <w:sig w:usb0="20002A87" w:usb1="80000000" w:usb2="00000008" w:usb3="00000000" w:csb0="000001FF" w:csb1="00000000" /></w:font>

The font element contains information about the Times New Roman font; specifically, information used to locate a substitute font if it is not available. end example]

Parent Elements

fonts (§2.8.2.11)

Child Elements

Subclause

altName (Alternate Names for Font)

§2.8.2.1

charset (Character Set Supported By Font)

§2.8.2.2

embedBold (Bold Style Font Style Embedding)

§2.8.2.3

embedBoldItalic (Bold Italic Font Style Embedding)

§2.8.2.4

embedItalic (Italic Font Style Embedding)

§2.8.2.5

embedRegular (Regular Font Style Embedding)

§2.8.2.6

family (Font Family)

§2.8.2.9

notTrueType (Raster or Vector Font)

§2.8.2.12

panose1 (Pansose-1 Typeface Classification Number)

§2.8.2.13

pitch (Font Pitch)

§2.8.2.14

sig (Supported Unicode Subranges and Code Pages)

§2.8.2.16

Attributes

Description

name (Primary Font Name)

Specifies the primary name of the current font. This name shall be used to link the information stored in this element with uses of this value in the rFonts element (§2.3.2.24) in document content.

[Example: Consider the following information stored for a single font:

<w:font w:name="Times New Roman"> …</w:font>

The name attribute specifies that the information contained in this element shall be used to look up information about all uses of the Times New Roman font in the document contents. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

fonts (Font Table Root Element)

This element specifies the root element for a font table part within a WordprocessingML document, and specifies information about the fonts used in this document, each contained within a child font element.

[Example: Consider the following information stored in a font table part:

<w:fonts> <w:font w:name="Times New Roman"> … </w:font> <w:font w:name="Arial"> … </w:font></w:fonts>

The fonts element contains information about all fonts used in the document - in this example, the Times New Roman and Arial fonts. end example]

Parent Elements

Root element of WordprocessingML Font Table part

Child Elements

Subclause

font (Properties for a Single Font)

§2.8.2.10

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

notTrueType (Raster or Vector Font)

This element specifies that this font is not a TrueType or OpenType font, but is rather a raster or vector font. This information may be used as defined in font substitution logic to locate an appropriate substitute font when this font is not available. This information is determined by querying the font when present and shall not be modified when the font is not available.

If this element is omitted, then the font shall be assumed to be a TrueType or OpenType font.

[Example: Consider the following information stored for a single font:

<w:font w:name="JonsFont"> <w:notTrueType w:val="true" /> …</w:font>

The notTrueType element specifies via its val attribute value of true that this font is a raster or vector font. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

panose1 (Pansose-1 Typeface Classification Number)

This element specifies the Panose-1 classification number for the current font using the PANOSE Classification Guide, Version 1.2. This information may be used as defined in font substitution logic to locate an appropriate substitute font when this font is not available. This information is determined by querying the font when present and shall not be modified when the font is not available.

If this element is omitted, then no Panose-1 information is available.

[Example: Consider the following information stored for a single font:

<w:font w:name="Times New Roman"> <w:panose1 w:val="02020603050405020304" /> …</w:font>

The panose1 element specifies its Panose-1 number via its val attribute value of 02020603050405020304. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

val (Value)

Specifies the Panose-1 classification number for the font, stored as a series of two digit hexadecimal encodings of each digits of the Panose number.

[Example: Consider the following information stored for a single font:

<w:panose1 w:val="020F0603050405020304" />

The val attribute specifies that the digits in the Panose-1 number are: 2,15,6,3,5,2,3,4. end example]

The possible values for this attribute are defined by the ST_Panose simple type (§2.18.72).

The following XML Schema fragment defines the contents of this element:

</complexType>

pitch (Font Pitch)

This element specifies the font pitch of the current font. This information may be used as defined in font substitution logic to locate an appropriate substitute font when this font is not available. This information is determined by querying the font when present and shall not be modified when the font is not available.

If this element is omitted, then its value shall be assumed to be default.

[Example: Consider the following information stored for a single font:

<w:font w:name="Courier New"> <w:pitch w:val="fixed" /> …</w:font>

The pitch element specifies via its val attribute value of fixed that this is a fixed width font. end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

val (Value)

Specifies the font pitch for the font.

[Example: Consider the following information stored for a single font:

<w:pitch w:val="variable" />

The val attribute value of variable specifies that this is a variable width font. end example]

The possible values for this attribute are defined by the ST_Pitch simple type (§2.18.73).

The following XML Schema fragment defines the contents of this element:

</complexType>

saveSubsetFonts (Subset Fonts When Embedding)

This element specifies that applications shall subset fonts when font embedding is enabled for this document using the embedTrueTypeFonts element (§2.8.2.8). Subsetting is a mechanism by which only the glyphs used in the contents of this WordprocessingML document are stored in an embedded font, in order to prevent the file from becoming unnecessarily large from the use of a small number of glyphs from a large embedded font.

If this element is omitted, then the set of fonts should not be subsetted in the current document when font embedded is turned on. If the embedTrueTypeFonts element is omitted or false, then this setting has no effect.

[Example: Consider a WordprocessingML document that specifies that it shall subset embedded fonts. This requirement would be specified using the following WordprocessingML in the document settings part:

<w:embedTrueTypeFonts w:val="true" /><w:saveSubsetFonts w:val="true"/>

The embedSystemFonts element's val attribute has a value of true specifying fonts should be subsetted in this document when they are embedded. end example]

Parent Elements

settings (§2.15.1.78)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

sig (Supported Unicode Subranges and Code Pages)

This element specifies information identifying the code pages and Unicode subranges for which the parent font provides glyphs. This information may be used as defined in font substitution logic to locate an appropriate substitute font when this font is not available. This information is determined by querying the font when present and shall not be modified when the font is not available.

When storing Unicode subrange information, the appropriate bit in the bitfield shall only be set if the entire subrange is supported by that font.

If this element is omitted, then no supported code page/Unicode subrange information is available.

[Example: Consider the following information stored for a single font:

<w:font w:name="Times New Roman"> <w:sig w:usb0="20002A87" w:usb1="80000000" w:usb2="00000008" w:usb3="00000000" w:csb0="000001FF" w:csb1="00000000" /> …</w:font>

The sig element specifies the supported code pages and Unicode sub ranges via its attributes. For example, the code pages supported are:

Latin 1

Latin 2: Eastern Europe

Cyrillic

Greek

Turkish

Baltic

end example]

Parent Elements

font (§2.8.2.10)

Attributes

Description

csb0 (Lower 32 Bits of Code Page Bit Field)

Specifies a four digit hexadecimal encoding of the first 32 bits of the 64-bit code-page bit field that identifies which specific character sets or code pages are supported by the parent font.

Each bit in this 32 bits represents the following code page:

Bit

Description

Latin 1

Latin 2: Eastern Europe

Cyrillic

Greek

Turkish

Hebrew

Arabic

Windows Baltic

8 to 16

Reserved for Alternate ANSI

Thai

JIS/Japan

Chinese (Simplified)

Korean Wansung

Chinese (Traditional)

22 to 29

Reserved for Alternate ANSI and OEM

Macintosh Character Set (Standard Roman)

Symbol Character Set

[Example: Consider font information specified as follows:

<w:font w:name="Lucida Console"> <w:sig w:csb0="0000001F" … /> …</w:font>

The csb0 attribute value of 0000001F specifies that the following code pages are supported by this font:

Latin 1

Latin 2: Eastern Europe

Cyrillic

Greek

Turkish

end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

csb1 (Upper 32 Bits of Code Page Bit Field)

Specifies a four digit hexadecimal encoding of the upper 32 bits of the 64-bit code-page bit field that identifies which specific character sets or code pages are supported by the parent font.

Each bit in this 32 bits represents the following code page:

Bit

Description

0 to 15

Reserved for OEM

IBM Greek

MS-DOS Russian

MS-DOS Nordic

Arabic

MS-DOS Canadian French

Hebrew

MS-DOS Icelandic

MS-DOS Portuguese

IBM Turkish

IBM Cyrillic

Latin 2

MS-DOS Baltic

Greek (former 437G)

Arabic (AMSO 708)

WE/Latin 1

[Example: Consider font information specified as follows:

<w:font w:name="Lucida Console"> <w:sig w:csb1="00000000" … /> …</w:font>

The csb1 attribute value of 00000000 specifies that none of the specified code pages are supported by this font. end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

usb0 (First 32 Bits of Unicode Subset Bitfield)

Specifies the first 32 bits of the 128-bit Unicode subset bit field (USB). Subranges are ordered in accordance with the ISO 10646 standard.

[Example: Consider font information specified as follows:

<w:font w:name="Times New Roman"> <w:sig w:usb0="20002A87" … /> …</w:font>

The usb0 attribute value of 20002A87 specifies that the first 32 bits of the bitfield are 00100000000000000010101010000111, which corresponds to:

Basic Latin

Latin-1 Supplement

Latin Extended-A

Basic Greek

Cyrillic

Basic Hebrew

Basic Arabic

Latin Extended Additional

end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

usb1 (Second 32 Bits of Unicode Subset Bitfield)

Specifies the second 32 bits of the 128-bit Unicode subset bit field (USB). Subranges are ordered in accordance with the ISO 10646 standard.

[Example: Consider font information specified as follows:

<w:font w:name="Times New Roman"> <w:sig w:usb1="80000000" … /> …</w:font>

The usb0 attribute value of 80000000 specifies that the first 32 bits of the bitfield are 10000000000000000000000000000000, which corresponds to:

Arabic Presentation Forms-A

end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

usb2 (Third 32 Bits of Unicode Subset Bitfield)

Specifies the third 32 bits of the 128-bit Unicode subset bit field (USB). Subranges are ordered in accordance with the ISO 10646 standard.

[Example: Consider font information specified as follows:

<w:font w:name="Times New Roman"> <w:sig w:usb2="00000008" … /> …</w:font>

The usb0 attribute value of 80000000 specifies that the first 32 bits of the bitfield are 00000000000000000000000000001000, which corresponds to:

Arabic Presentation Forms-B

end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

usb3 (Fourth 32 Bits of Unicode Subset Bitfield)

Specifies the fourth 32 bits of the 128-bit Unicode subset bit field (USB). Subranges are ordered in accordance with the ISO 10646 standard.

[Example: Consider font information specified as follows:

<w:font w:name="Times New Roman"> <w:sig w:usb3="00000000" … /> …</w:font>

The usb3 attribute value of 00000000 specifies that the first 32 bits of the bitfield are 00000000000000000000000000000000, which corresponds to no subranges. end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</complexType>

Numbering

Numbering refers to symbols - Arabic numerals, Roman numerals, symbol characters ("bullets"), text strings, etc. - in WordprocessingML that are used to label individual paragraphs of text.

[Example: The following two paragraphs each contain numbering as defined by WordprocessingML: the first uses an Arabic numeral, the second a symbol character:

This is a paragraph with numbering information.

This is also a paragraph with numbering information.

end example]

The basis for all numbering in WordprocessingML is specified via two structures:

abstract numbering definitions

numbering definition instances

Abstract numbering definitions define the appearance and behavior of a specific set of numbered paragraphs in a document. Because this construct is abstract, they are not be directly referenced by document content, but rather they must be inherited by a numbering definition instance, which itself is referenced by document content.

[Example: Consider the following example of an abstract numbering definition in a WordprocessingML document:

<w:abstractNum w:abstractNumId="4"> <w:nsid w:val="FFFFFF7F" /> <w:multiLevelType w:val="singleLevel" /> <w:lvl w:ilvl="0"> <w:start w:val="1" /> <w:lvlText w:val="%1." /> <w:lvlJc w:val="left" /> <w:pPr> <w:tabs> <w:tab w:val="num" w:pos="720" /> </w:tabs> <w:ind w:left="720" w:hanging="360" /> </w:pPr> </w:lvl></w:abstractNum>

This abstractNum element defines an abstract numbering definition which defines a set of numbering properties. It is inherited by any numbering definition instance which inherits from an abstractNumId equal to 4:

<w:num w:numId="2"> <w:abstractNumId w:val="4" /></w:num>

This num element defines an numbering definition instance which may define overrides to the abstract numbering definition (in this case it does not), and is used by any paragraphs with a numId equal to 2:

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="2" /> </w:numPr> </w:pPr> <w:r> <w:t>Level one</w:t> </w:r></w:p>

The resulting paragraph will inherit the properties of level 0 in the numbering definition instance of 2 which is simply a instance of the abstract numbering definition of 4. end example]

abstractNum (Abstract Numbering Definition)

This element specifies a set of properties which shall dictate the appearance and behavior of a set of numbered paragraphs in a WordprocessingML document. These properties are collectively called an abstract numbering definition, and are the basis for all numbering information in a WordprocessingML document.

Although an abstract numbering definition contains a complete set of numbering, it shall not be directly referenced by content (hence the use of abstract). Instead, these properties shall be inherited by a numbering definition instance using the num element (§2.9.16), which can then itself be referenced by content.

[Example: Consider the following example of an abstractNum in a WordprocessingML document:

This abstractNum element defines an abstract numbering definition which shall be inherited by any numbering definition instance which inherits from abstract numbering definition with an abstractNumId equal to 4. end example]

Parent Elements

numbering (§2.9.17)

Child Elements

Subclause

lvl (Numbering Level Definition)

§2.9.7

multiLevelType (Abstract Numbering Definition Type)

§2.9.13

name (Abstract Numbering Definition Name)

§2.9.14

nsid (Abstract Numbering Definition Identifier)

§2.9.15

numStyleLink (Numbering Style Reference)

§2.9.22

styleLink (Numbering Style Definition)

§2.9.29

tmpl (Numbering Template Code)

§2.9.31

Attributes

Description

abstractNumId (Abstract Numbering Definition ID)

Specifies a unique number which shall be used as the identifier for this abstract numbering definition. This unique number shall be referenced by any numbering definition instance in order to inherit the properties specified by this abstract numbering definition.

[Example: Consider the WordprocessingML for an abstract numbering definition with an abstractNumId attribute of 4:

The abstractNumId attribute serves as a unique identifier for the abstract numbering definition, allowing numbering definition instances (§2.9.16) with a abstractNumId element with a matching attribute value to inherit the abstract numbering definition properties, for example:

<w:numbering> ... <w:num w:numId="2"> <w:abstractNumId w:val="0" /> </w:num> <w:num w:numId="3"> <w:abstractNumId w:val="1" /> </w:num> <w:num w:numId="4"> <w:abstractNumId w:val="4" /> </w:num> <w:num w:numId="5"> <w:abstractNumId w:val="4" /> </w:num></w:numbering>

In this case, the final two numbering definition instances both inherit from the abstract numbering definition with a abstractNumId of 4. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

abstractNumId (Abstract Numbering Definition Reference)

This element specifies the abstract numbering definition information whose properties shall be inherited by the parent numbering definition instance.

[Example: Consider the WordprocessingML for a document with two numbering definition instances, each referencing a different abstract numbering definition:

<w:numbering> <w:abstractNum w:abstractNumId="0">

<w:abstractNum w:abstractNumId="1">

... <w:num w:numId="1"> <w:abstractNumId w:val="0" /> </w:num> <w:num w:numId="2"> <w:abstractNumId w:val="1" /> </w:num>

...

</w:numbering>

The two numbering definition instances reference the abstract numbering definitions with abstractNumId attribute values of 0 and 1 respectively, via their abstractNumId elements. end example]

Parent Elements

num (§2.9.16)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

ilvl (Numbering Level Reference)

This element specifies the numbering level of the numbering definition instance which shall be applied to the parent paragraph.

This numbering level is specified on either the abstract numbering definition's lvl element (§2.9.7), and may be overridden by a numbering definition instance level override's lvl element (§2.9.6).

[Example: Consider the following numbered paragraphs in a WordprocessingML document:

1. Level one

a. Level two

These numbered paragraphs may be represented using the following WordprocessingML:

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="5" /> </w:numPr> </w:pPr> <w:r> <w:t>Level one</w:t> </w:r></w:p>

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="1" /> <w:numId w:val="5" /> </w:numPr> </w:pPr> <w:r> <w:t>Level two</w:t> </w:r></w:p>

The WordprocessingML above specifies that the first numbered paragraph references the numbering level of 0, within the numbering definition of the num element (§2.9.16) with a numId attribute equal to 5.

The second numbered paragraph references the numbering of 1, within the same numbering definition instance. The WordprocessingML referenced by the ilvl elements above is given below:

<w:num w:numId="5"> <w:abstractNumId w:val="0" /></w:num>

...

<w:abstractNum w:abstractNumId="0"> <w:nsid w:val="FFFFFF7F" /> <w:multiLevelType w:val="singleLevel" /> <w:lvl w:ilvl="0"> ... </w:lvl>

<w:lvl w:ilvl="1"> ... </w:lvl></w:abstractNum>

In this case, the resulting paragraphs would inherit the properties of the abstract numbering definition levels with ilvl attributes of 0 and 1, respectively. end example]

Parent Elements

numPr (§2.3.1.19)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

isLgl (Display All Levels Using Arabic Numerals)

This element specifies whether or not all previous levels displayed for a given numbering level's text shall be displayed using the decimal number format, regardless of the actual number format of that level in the list. [Note: This numbering style is often referred to as the legal numbering style. end note]

If this element is present, then all numbering levels present in the lvlTxt element (§2.9.12) shall be converted to their decimal equivalents when they are displayed in this level in the numbering format. If this element is omitted, then each level is displayed using the numFmt (§2.9.18) of that level.

[Example: Consider the numbering set below. In this set of blank numbered paragraphs, three numbering levels have been used and the third has the isLgl property applied, resulting in the following:

A.a

A.b

1.2.1

1.2.2

B.a

2.1.1

As shown above, each number in the third level in the list has been converted to its decimal equivalent. The WordprocessingML necessary to turn on the legal numbering rule for the third numbering level is given below:

<w:lvl w:ilvl="2">

...

<w:isLgl />

...

</w:lvl>

end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

legacy (Legacy Numbering Level Properties)

This element specifies that a given numbering level is from an earlier word processing application which did not support the full richness of the numbering properties supported by WordprocessingML.

These properties shall be used to render any numbered paragraph which references this numbering level if the legacy attribute is set. [Note: Using this element in generated WordprocessingML documents is not recommended, as updated numbering structures in WordprocessingML should be used in its place. This element is provided solely to save and roundtrip the numbering properties of legacy word processing products in WordprocessingML such that they are recreated if the document is resaved in an older word processor format. end note]

[Example: Consider the following WordprocessingML numbering level:

<w:lvl w:ilvl="0">

...

<w:legacy w:legacySpace="820" w:legacyIndent="960" />

<w:lvlJc w:val="left" />

<w:pPr>

<w:ind w:left="360" w:hanging="360" />

</w:pPr>

</w:lvl>

This level has the legacy element present, therefore the legacy numbering level properties shall be used to format all paragraphs which reference this level. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

legacy (Use Legacy Numbering Properties)

Specifies whether the legacy numbering properties present for this numbering level shall be used to format the numbering for any paragraph which references it.

A value of on, 1, or true for this attribute value specifies that the legacy numbering properties shall be applied. This is the default value for this attribute, and is implied when the attribute is omitted.

A value of off, 0, or false for this attribute value specifies that the legacy numbering properties shall not be used, and shall be explicitly turned off.

[Example: For example, consider the set of legacy numbering properties from a document:

<w:legacy w:legacy="off" w:legacySpace="820" w:legacyIndent="960" />

This set of legacy properties are explicitly not used when processing the numbering level via the fact that the legacy attribute is turned off for this example. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

legacyIndent (Legacy Indent)

Specifies the indentation which shall be applied to a legacy numbering symbol from the text margin of the document. This value is specified in twentieths of a point.

If this attribute is not present, then no indentation shall be applied with respect to the margin.

[Example: For example, consider the set of legacy numbering properties from a document:

<w:legacy w:legacySpace="820" w:legacyIndent="960" />

This set of legacy properties specify that there shall be exactly 960 twentieths of a point (⅔ of an inch) between the text margin and the start of the numbering on the paragraph. end example]

The possible values for this attribute are defined by the ST_SignedTwipsMeasure simple type (§2.18.88).

legacySpace (Legacy Spacing)

Specifies the indentation which shall be applied between a legacy numbering symbol and the accompanying text of the associated paragraph in the document. This value is specified in twentieths of a point.

If this attribute is not present, then no indentation shall be applied with respect to the paragraph text.

[Example: For example, consider the set of legacy numbering properties from a document:

<w:legacy w:legacySpace="820" w:legacyIndent="960" />

This set of legacy properties specify that there shall be exactly 860 twentieths of a point between the end of the numbering on the paragraph and the associated paragraph text. end example]

The possible values for this attribute are defined by the ST_TwipsMeasure simple type (§2.18.105).

The following XML Schema fragment defines the contents of this element:

</complexType>

lvl (Numbering Level Override Definition)

This element specifies the appearance and behavior of a specific numbering level within a given numbering level definition override defined using the lvlOverride element (§2.9.9).

A numbering level override definition is identical to a numbering level definition, except for the fact that it is defined as part of a numbering definition instance using the num element (§2.9.16) rather than as part of an abstract numbering definition using the abstractNum element (§2.9.1).

[Example: Consider a numbering definition instance which inherits its information from the abstract numbering definition with abstractNumId of 4, but should use a different set of properties for level 0 of the numbering definition. The resulting WordprocessingML would look like:

<w:num w:numId="6"> <w:abstractNumId w:val="4" /> <w:lvlOverride w:ilvl="0"> <w:lvl w:ilvl="0"> <w:start w:val="4" /> <w:lvlText w:val="%1)" /> <w:lvlJc w:val="left" /> <w:pPr> <w:ind w:left="360" w:hanging="360" /> </w:pPr> </w:lvl> </w:lvlOverride></w:num>

This numbering definition instance overrides level 0 of the list with the specified numbering level override definition, replacing those in the abstract numbering level definition. end example]

[Note: The ability to set level overrides optimizes use of numbering in WordprocessingML as it prevents writing out redundant abstract numbering definitions if numbering sets only slightly differ.

Consider using WordprocessingML to create two numbered sets that only differ only in the appearance and style of the first numbering level. Both could use the same abstract numbering definition as long as each references a different numbering definition instance with one of the numbering definition instances leveraging a level override for the first numbering level. Below is WordprocessingML that illustrates this:

<w:num w:numId="5"> <w:abstractNumId w:val="4" /></w:num>

end note]

Parent Elements

lvlOverride (§2.9.9)

Child Elements

Subclause

isLgl (Display All Levels Using Arabic Numerals)

§2.9.4

legacy (Legacy Numbering Level Properties)

§2.9.5

lvlJc (Justification)

§2.9.8

lvlPicBulletId (Picture Numbering Symbol Definition Reference)

§2.9.10

lvlRestart (Restart Numbering Level Symbol)

§2.9.11

lvlText (Numbering Level Text)

§2.9.12

numFmt (Numbering Format)

§2.9.18

pPr (Numbering Level Associated Paragraph Properties)

§2.9.24

pStyle (Paragraph Style's Associated Numbering Level)

§2.9.25

rPr (Numbering Symbol Run Properties)

§2.9.26

start (Starting Value)

§2.9.27

suff (Content Between Numbering Symbol and Paragraph Text)

§2.9.30

Attributes

Description

ilvl (Numbering Level)

Specifies the numbering level definition that is to be defined by this set of numbering properties.

This override is a zero-based index of the number of list levels in the document. [Example: A value of 2 is the 3rd list level in the document. end example]

[Example: Consider the following WordprocessingML for a numbering definition instance:

<w:num w:numId="6"> <w:abstractNumId w:val="4" />

<w:lvlOverride w:ilvl="0">

…

</w:num>

In this example, the first numbering level definition (with an ilvl of 0) within the referenced abstract numbering definition will be overridden. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

tentative (Tentative Numbering)

Specifies that a given numbering level was been saved by a producer but was not used in the parent document. This means that this numbering level may be redefined by a future consumer without changing the actual content of the document.

A value of on, 1, or true for this attribute value specifies that the numbering level is not used in the current document's contents.

A value of off, 0, or false for this attribute value specifies that the numbering level is used in the parent document and cannot be redefined without changing its contents. This is the default value for this attribute, and is implied when this attribute is omitted.

[Example: Consider the following WordprocessingML numbering level:

<w:lvl w:ilvl="0" w:tentative="on" >

...

</w:lvl>

This level has the tentative attribute set to on, therefore the contents of this numbering level have not been used in the document and may be redefined by a consumer as desired. end example]

If this attribute is equal to on, 1, or true, the WordprocessingML for a given document will contain the numbering level information associated with this numbering level, but the 'tentative' numbering level(s) shall not be represented in any of the hosting application's user interface pertaining to numbering levels.

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

tplc (Template Code)

Specifies a unique hexadecimal value which may be used to specify a location within an application's user interface in which this numbering level shall be displayed. The method by which this value is interpreted shall be application-defined.

If this attribute is omitted, then this numbering may be displayed in any location chosen by the consumer.

[Example: Consider the following abstract numbering definition:

<w:abstractNum w:abstractNumId="1" w:tplc="04090019">

…

</w:abstractNum>

In this example the abstractNum element with attribute abstractNumId equal to 1, would appear in the area within a consumer's application user interface specified by the template code 04090019.end example]

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

lvl (Numbering Level Definition)

This element specifies the appearance and behavior of a numbering level within a given abstract numbering definition. A numbering level contains a set of properties for the display of the numbering for a given numbering level within an abstract numbering definition.

A numbering level definition is identical to a numbering level override definition, except for the fact that it is defined as part of a numbering definition instance using the abstractNum element (§2.9.1) rather than as part of an abstract numbering definition using the num element (§2.9.16).

[Example: Consider the WordprocessingML below:

<w:abstractNum w:abstractNumId="4"> <w:nsid w:val="1DE04504" /> <w:multiLevelType w:val="hybridMultilevel" /> <w:lvl w:ilvl="0" w:tplc="0409000F"> ... </w:lvl> <w:lvl w:ilvl="1" w:tplc="04090019"> ... </w:lvl> <w:lvl w:ilvl="2" w:tplc="04090019"> ... </w:lvl> <w:lvl w:ilvl="3" w:tplc="0409000F"> ... </w:lvl> ...</w:abstractNum>

This example shows that any paragraph whose numbering properties use the ilvl elements with the attribute val set equal to 0, 1, 2, or 3 will have the appearance and behavior of their first four numbered levels specified by the lvl elements given above (assuming that no level overrides have been specified). end example]

Parent Elements

abstractNum (§2.9.1)

Child Elements

Subclause

isLgl (Display All Levels Using Arabic Numerals)

§2.9.4

legacy (Legacy Numbering Level Properties)

§2.9.5

lvlJc (Justification)

§2.9.8

lvlPicBulletId (Picture Numbering Symbol Definition Reference)

§2.9.10

lvlRestart (Restart Numbering Level Symbol)

§2.9.11

lvlText (Numbering Level Text)

§2.9.12

numFmt (Numbering Format)

§2.9.18

pPr (Numbering Level Associated Paragraph Properties)

§2.9.24

pStyle (Paragraph Style's Associated Numbering Level)

§2.9.25

rPr (Numbering Symbol Run Properties)

§2.9.26

start (Starting Value)

§2.9.27

suff (Content Between Numbering Symbol and Paragraph Text)

§2.9.30

Attributes

Description

ilvl (Numbering Level)

Specifies the numbering level definition that is to be defined by this set of numbering properties.

This override is a zero-based index of the number of list levels in the document. [Example: A value of 2 is the 3rd list level in the document. end example]

[Example: Consider the following WordprocessingML for a numbering definition instance:

<w:num w:numId="6"> <w:abstractNumId w:val="4" />

<w:lvlOverride w:ilvl="0">

…

</w:num>

In this example, the first numbering level definition (with an ilvl of 0) within the referenced abstract numbering definition will be overridden. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

tentative (Tentative Numbering)

A value of on, 1, or true for this attribute value specifies that the numbering level is not used in the current document's contents.

[Example: Consider the following WordprocessingML numbering level:

<w:lvl w:ilvl="0" w:tentative="on" >

...

</w:lvl>

This level has the tentative attribute set to on, therefore the contents of this numbering level have not been used in the document and may be redefined by a consumer as desired. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

tplc (Template Code)

If this attribute is omitted, then this numbering may be displayed in any location chosen by the consumer.

[Example: Consider the following abstract numbering definition:

<w:abstractNum w:abstractNumId="1" w:tplc="04090019">

…

</w:abstractNum>

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

lvlJc (Justification)

This element specifies the type of justification used on a numbering level's text within a given numbering level. This justification is applied relative to the text margin of the parent numbered paragraph in the document.

If omitted, the paragraph shall have left justification relative to the text margin in left-to-right paragraphs, and right justification relative to the text margin in right-to-left paragraphs.

[Example: Consider the numbering level defined below:

<w:lvl w:ilvl="8" w:tplc="756C1446" w:tentative="1">

<w:start w:val="1" />

<w:nfc w:val="23" />

<w:lvlText w:val="•" />

<w:lvlJc w:val="left" />

…

</w:lvl>

In this numbering level, the given numbering symbol will be left justified with respect to the text margin, therefore the numbering will extend left from the text margin towards the text (assuming a left-to-right paragraph). end example]

A numbering level's text is the numeral, symbol, character, graphic, etc. used to create a numbered paragraph as defined by the lvlText element (§2.9.12).

[Example: Consider the numbered paragraphs below:

1) Example one

a. Example two

• Example three

The numbering symbol in these three numbered paragraphs are "1", "a", and "•", respectively. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (Alignment Type)

Specifies the justification which should be applied to the parent object within a document.

The possible values (see below) for this attribute are always specified relative to the page, and do not change semantic from right-to-left and left-to-right documents.

[Example: Consider the following WordprocessingML fragment for a paragraph in a document:

<w:pPr>

<w:jc w:val="right" />

</w:pPr>

This paragraph is now right justified on the page, regardless of the paragraph or section settings. end example]

The possible values for this attribute are defined by the ST_Jc simple type (§2.18.50).

The following XML Schema fragment defines the contents of this element:

</complexType>

lvlOverride (Numbering Level Definition Override)

This element specifies an optional override which shall be applied in place of zero or more levels from the abstract numbering definition for a given numbering definition instance. Each instance of this element is used to override the appearance and behavior of a given numbering level definition within the given abstract numbering definition.

[Example: Consider a numbering definition instance which inherits its information from the abstract numbering definition with abstractNumId of 4, but wishes to use a different set of properties for level 0 and level 1 of the numbering definition. The resulting WordprocessingML would look like:

<w:lvlOverride w:ilvl="1"> <w:lvl w:ilvl="1"> <w:start w:val="5" /> <w:lvlText w:val="%Test)" /> <w:lvlJc w:val="left" /> <w:pPr> <w:ind w:left="360" w:hanging="360" /> </w:pPr> </w:lvl> </w:lvlOverride></w:num>

end example]

[Note: The ability to set level overrides optimizes use of numbering in WordprocessingML as it prevents writing out redundant abstract numbering definitions if numbering sets only slightly differ.

<w:num w:numId="5"> <w:abstractNumId w:val="4" /></w:num>

end note]

Parent Elements

num (§2.9.16)

Child Elements

Subclause

lvl (Numbering Level Override Definition)

§2.9.6

startOverride (Numbering Level Starting Value Override)

§2.9.28

Attributes

Description

ilvl (Numbering Level ID)

Specifies the numbering level of a given abstract numbering definition to be overridden.

If this number conflicts with the ilvl of the child lvl element, then the latter shall be ignored.

[Example: Consider a numbering definition instance which inherits its information from the abstract numbering definition with abstractNumId of 4, but wishes to use a different set of properties for level 0 of the numbering definition. The resulting WordprocessingML would look like:

This level overrides level 0 of the abstract numbering definition's level properties with the specified set of numbering properties, replacing those in the abstract numbering definition. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

lvlPicBulletId (Picture Numbering Symbol Definition Reference)

This element specifies a picture which shall be used as a numbering symbol for a given numbering level by referring to a picture numbering symbol definition's numPictBullet element (§2.9.21). This reference is made through this element's val attribute.

The picture shall be added to the numbering level by replacing each character in the lvlText with on instance of this image

[Example: Consider the WordprocessingML below illustrating how the lvlPicBulletId references a picture numbering symbol definition thought its val attribute:

<w:numPicBullet w:numPicBulletId="1">

<w:pict>

<v:shape id="_x0000_i1031" type="#_x0000_t75" style="width:3in;height:276.75pt" o:bullet="t">

<v:imagedata r:id="rId2" o:title="testpic" />

</v:shape>

</w:pict>

</w:numPicBullet>

…

<w:abstractNum w:abstractNumId="7">

<w:nsid w:val="71A06359" />

<w:multiLevelType w:val="hybridMultilevel" />

<w:tmpl w:val="10643FE6" />

<w:lvl w:ilvl="0" w:tplc="B7663E56">

<w:start w:val="1" />

<w:nfc w:val="23" />

<w:lvlText w:val="AA" />

<w:lvlPicBulletId w:val="1" />

</w:lvl>

</w:abstractNum>

The resulting numbering shall consist of two instances of the image specified using the numPicBullet element. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

lvlRestart (Restart Numbering Level Symbol)

This element specifies a one-based index which determines when a numbering level should restart to its start value (§2.9.27). A numbering level restarts when an instance of the specified numbering level, which shall be higher (earlier than the this level) is used in the given document's contents.

If this element is omitted, the numbering level shall restart each time the previous numbering level is used. If the specified level is higher than the current level, then this element shall be ignored. As well, a value of 0 shall specify that this level shall never restart.

[Example: Consider a set of numbered paragraphs in a WordprocessingML document where numbering level with ilvl of 2 is set to never restart:

<w:lvl w:ilvl="0">

<w:start w:val="1" />

<w:lvlText w:val="%1)" />

<w:lvlJc w:val="left" />

<w:pPr>

<w:ind w:left="360" w:hanging="360" />

</w:pPr>

<w:rPr>

<w:rFonts w:hint="default" />

</w:rPr>

</w:lvl>

<w:lvl w:ilvl="1">

<w:start w:val="1" />

<w:numFmt w:val="upperLetter" />

<w:lvlText w:val="%2)" />

<w:lvlJc w:val="left" />

<w:pPr>

<w:ind w:left="720" w:hanging="360" />

</w:pPr>

<w:rPr>

<w:rFonts w:hint="default" />

</w:rPr>

</w:lvl>

<w:lvl w:ilvl="2">

<w:start w:val="1" />

<w:numFmt w:val="lowerRoman" />

<w:lvlRestart w:val="0">

<w:lvlText w:val="%3)" />

<w:lvlJc w:val="left" />

<w:pPr>

<w:ind w:left="1080" w:hanging="360" />

</w:pPr>

<w:rPr>

<w:rFonts w:hint="default" />

</w:rPr>

</w:lvl>

Since the lvlRestart element is omitted in numbering level 1 (a,b,…), the numbering level restarts after numbering level 0 (1,2,…) is used. Numbering level two (i, ii, iii …) never restarts as lvlRestart has a val equal to 0. An example of the resulting content would be as follows:

1)Level one

a)Level two

i)Level three

ii)Level three

2)Level one

a)Level two

iii)Level three

iv)Level four

The resulting set of paragraphs has level two restarting to its start value after each level one (after 2), the next level two is again a)), but level three never restarts and continues at iii) even after the use of a level two and one. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

lvlText (Numbering Level Text)

This element specifies the textual content which shall be displayed when displaying a paragraph with the given numbering level.

All text in this element's val attribute shall be taken as literal text to be repeated in each instance of this numbering level, except for any use of the percent symbol (%) followed by a number, which shall be used to indicate the one-based index of the number to be used at this level. Any number of a level higher than this level shall be ignored.

When the % syntax is used, the number shall be incremented for each subsequent paragraph of that level (sequential or not), until the restart level is seen between two subsequent paragraphs of this level.

[Example: Consider the following WordprocessingML for a numbering level:

<w:lvl w:ilvl="1"> …

<w:lvlText w:val="StringA %2 StringB %1 StringC %3"/>

…

</w:lvl>

This specifies that three strings (StringA, StringB, StringC) shall be used as string literals in the numbering for level two (ilvl of 1) along with the numbering symbol used for level one and level zero. Although level two is also referenced here, it is ignored as it is a higher level than the current numbering level.

Therefore, assuming the numbering symbol used by numbering level zero is an Arabic numeral, and the numbering symbol used by numbering level one is a Roman numeral, a set of numbered paragraphs using this WordprocessingML numbering set shall be output as:

StringA I StringB 1 StringC

StringA II StringB 1 StringC

StringA III StringB 1 StringC

StringA I StringB 2 StringC

StringA II StringB 2 StringC

with the %1 and %2 values corresponding to the current numbering symbol value for numbering level zero and one, respectively. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

null (Level Text Is Null Character)

Specifies that a null character shall be used as the numbering symbol for a given numbering level.

If the val attribute contains any content, then this attribute shall be ignored.

If this attribute is omitted, then the null string shall not be used in place of the empty string. [Note: A null character is different from an empty string. end note]

[Example: Consider the WordprocessingML below:

<w:lvl w:ilvl="1">

…

<w:lvlText w:null="on" />

…

</w:lvl>

This level text consists of a single null character, and not the empty string, as the null attribute is set. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

val (Level Text)

Specifies the actual text to be used for the numbering level when it is referenced in the document's content.

If this attribute is not specified, then the empty string shall be used as the level's text.

[Example: Consider the WordprocessingML below:

<w:lvl w:ilvl="1">

…

<w:lvlText w:val="test" />

…

</w:lvl>

Here the val attribute specifies that the literal string test is to be surfaced as the text for the given numbering level, regardless of its position. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

multiLevelType (Abstract Numbering Definition Type)

This element specifies the type of numbering defined by a given abstract numbering type. This information shall only be used by a consumer to determine user interface behaviors for this numbering definition, and shall not be used to limit the behavior of the list (i.e. a list with multiple levels marked as singleLevel shall not be prevented from using levels 2 through 9).

If this element is omitted, then the list shall be assumed to be of any type desired by the consumer.

[Example: Consider the WordprocessingML below:

<w:abstractNum w:abstractNumId="8">

…

<w:multiLevelType w:val="singleLevel" />

…

</w:abstractNum>

This abstract numbering definition is specified to be of the singleLevel type by the multiLevelType element. end example]

Parent Elements

abstractNum (§2.9.1)

Attributes

Description

val (Abstract Numbering Definition Type)

Specifies the specific type of numbering enabled by a given abstract numbering definition.

[Example: Consider the WordprocessingML below:

<w:abstractNum w:abstractNumId="8">

…

<w:multiLevelType w:val="multiLevel" />

…

</w:abstractNum>

This abstract numbering definition is specified to be of the multiLevel type, which may be used by consumers to place this numbering correctly within a user interface. end example]

The possible values for this attribute are defined by the ST_MultiLevelType simple type (§2.18.65).

The following XML Schema fragment defines the contents of this element:

</complexType>

name (Abstract Numbering Definition Name)

This element specifies the name of a given abstract numbering definition. This name may be surfaced in order to provide a user friendly alias for a given numbering definition, but shall not influence the behavior of the list - two identical definitions with different name elements shall behave identically.

If this element is omitted, then this abstract numbering definition shall have no name.

[Example: Consider the WordprocessingML below:

<w:abstractNum w:abstractNumId="4">

<w:nsid w:val="5C294B5B" />

<w:multiLevelType w:val="multilevel" />

<w:tmpl w:val="6F8A81B0" />

<w:name w:val="Example Name" />

…

</w:abstractNum>

In this example, the given abstract numbering definition is named Example Name by use of the name element. end example]

Parent Elements

abstractNum (§2.9.1)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

nsid (Abstract Numbering Definition Identifier)

This element associates a unique hexadecimal ID to the parent abstract numbering definition. This number shall be identical for two abstract numbering definitions that are based from the same initial numbering definition - if a document is repurposed and the underlying numbering definition is changed, it shall maintain its original nsid.

If this element is omitted, then the list shall have no nsid and one may be added by a producer arbitrarily.

[Note: This element may be used to determine the abstract numbering definition to be applied to a numbered paragraph copied from one document and pasted into another. Consider a case in which a given numbered paragraph associated with a abstract numbering definition with nsid FFFFFF23, is pasted among numbered paragraphs associated with a completely different appearance and an abstract numbering definition with an nsid of FFFFFF23. Here, because of the distinction enabled by the identical nsid values, the hosting application would not have to arbitrarily keep the pasted numbered paragraph associated with its original abstract numbering definition, as it may use the information provided by the abstract numbering definition's identical nsid values to know that those two numbering sets are identical, and merge the paragraphs into the target numbering format. end note]

[Example: Consider the WordprocessingML for an abstract numbering definition below:

<w:abstractNum w:abstractNumId="3">

<w:nsid w:val="FFFFFF89" />

<w:multiLevelType w:val="singleLevel" />

<w:tmpl w:val="D9842532" />

…

</w:abstractNum>

In this example, the given abstract numbering definition is associated with the unique hexadecimal ID FFFFFF89. end example]

Parent Elements

abstractNum (§2.9.1)

Attributes

Description

val (Long Hexadecimal Number Value)

Specifies a number value specified as a four digit hexadecimal number), whose contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following value for an attribute of type ST_LongHexNumber: 00BE2C6C.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</complexType>

num (Numbering Definition Instance)

This element specifies a unique instance of numbering information that can be referenced by zero or more paragraphs within the parent WordprocessingML document.

This instance requires the referencing of a base abstract numbering definition through the abstractNumId child element (§2.9.2). This element also can be used to specify a set of optional overrides applied to zero or more levels from the abstract numbering definition inherited by this instance second though the optional lvlOverride child elements (§2.9.9).

[Example: Consider the WordprocessingML for a document with four numbering definition instances, two of which reference the same underlying abstract numbering definition:

As shown above, the first two numbering definition instances reference abstractNumId values of 0 and 1 respectively, and the last two both reference the abstract numbering definition with an abstractNumId of 4. end example]

[Example: Consider a numbering definition instance which inherits its information from the abstract numbering definition with abstractNumId of 4, but wishes to use a different set of properties for level 0 of the numbering definition. The resulting WordprocessingML would look like:

The lvlOverride element specifies an override for level 0 of the abstract numbering definition. end example]

Parent Elements

numbering (§2.9.17)

Child Elements

Subclause

abstractNumId (Abstract Numbering Definition Reference)

§2.9.2

lvlOverride (Numbering Level Definition Override)

§2.9.9

Attributes

Description

numId (Numbering Definition Instance ID)

Specifies a unique ID which any numbered paragraph which wishes to inherit these numbering properties shall reference using the numPr element (§2.3.1.19).

[Example: Consider the WordprocessingML below for an example numbered paragraph:

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="5" /> </w:numPr> </w:pPr>

…

</w:p>

This paragraph references a numbering definition instance with a numId attribute of 5:

<w:num w:numId="5"> <w:abstractNumId w:val="4" />

</w:num>

The numbering definition instance with a numId attribute of 5 correlates with the numbered paragraph with the numbering definition instance referent element with a val of 5, so the numbered paragraph inherits its properties. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

numbering (Numbering Definitions)

This element specifies the formatting, display, and functionality of numbering - Arabic numerals, Roman numerals, symbol characters ("bullets"), text strings, etc. - in WordprocessingML documents, which are used to label individual paragraphs of text.

[Example: The following two paragraphs each contain numbering as defined by WordprocessingML: the first uses an Arabic numeral, the second a symbol character:

This is a paragraph with numbering information.

This is also a paragraph with numbering information.

end example]

Parent Elements

Root element of WordprocessingML Numbering Definitions part

Child Elements

Subclause

abstractNum (Abstract Numbering Definition)

§2.9.1

num (Numbering Definition Instance)

§2.9.16

numIdMacAtCleanup (Last Reviewed Abstract Numbering Definition)

§2.9.20

numPicBullet (Picture Numbering Symbol Definition)

§2.9.21

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

numFmt (Numbering Format)

This element specifies the number format which shall be used to display all numbering at this level in the numbering definition. This information is used to replace the level text string %x, where x is a particular one-based level index, with the appropriate value. This value shall be calculated by counting the number of paragraphs at this level since the last restart using the numbering system defined in the val attribute.

If omitted, the level shall be assumed to be of type decimal.

[Example: Consider the following WordprocessingML fragment for a numbering level in a numbering definition:

<w:lvl w:ilvl="2">

<w:start w:val="1" />

<w:numFmt w:val="lowerRoman" />

<w:lvlRestart w:val="0">

<w:lvlText w:val="%3)" />

<w:lvlJc w:val="left" />

<w:pPr>

<w:ind w:left="1080" w:hanging="360" />

</w:pPr>

<w:rPr>

<w:rFonts w:hint="default" />

</w:rPr>

</w:lvl>

A numFmt value of lowerLetter indicates that a consumer shall use lowercase letters for all numbering of this level: a,b,c… end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (Numbering Format Type)

Specifies the number format that shall be used for all numbering in the parent object.

[Example: A value of lowerLetter indicates that a consumer shall use lowercase letters for each number in this grouping: a,b,c… end example]

The possible values for this attribute are defined by the ST_NumberFormat simple type (§2.18.66).

The following XML Schema fragment defines the contents of this element:

</complexType>

numId (Numbering Definition Instance Reference)

This element specifies the numbering definition instance which shall be used for the given parent numbered paragraph in the WordprocessingML document.

A value of 0 for the val attribute shall never be used to point to a numbering definition instance, and shall instead only be used to designate the removal of numbering properties at a particular level in the style hierarchy (typically via direct formatting).

[Example: Consider the WordprocessingML below for an example numbered paragraph:

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="5" /> </w:numPr> </w:pPr>

…

</w:p>

This paragraph references a numbering definition instance with a numId attribute of 5, as follows:

<w:num w:numId="5"> <w:abstractNumId w:val="4" />

</w:num>

The numbering definition instance reference specifies the given numbering definition instance to be applied to the given paragraph, which itself inherits its properties from abstract numbering definition with abstractNumId of 4. end example]

Parent Elements

numPr (§2.3.1.19)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

numIdMacAtCleanup (Last Reviewed Abstract Numbering Definition)

This element specifies to a consumer the progress in the last attempt made by the application to remove unused abstract numbering definitions from a given document. If a legacy document is opened by a consumer, it may choose to remove abstract numbering definition which are 'orphaned' (have no associated numbering definition instances). This element is used by those consumers to indicate their progress (if not complete) in reviewing existing abstract numbering definitions. [Note: Removing unused abstract numbering definition from a document will reduce the file size, but is not required. end note]

If omitted, then all abstract numbering definitions shall be considered reviewed.

[Example: Consider a document with 32 abstract numbering definitions, with abstractNumId values ranging from 0 to 85. If an application has only reviewed those abstract numbering definitions with abstractNumId values lower than 25 at save time, it would indicate that state as follows:

<w:numIdMacAtCleanup w:val="25"/>

This value specifies that all abstract numbering definitions with an abstractNumId value higher than 25 have not yet been reviewed. end example]

Parent Elements

numbering (§2.9.17)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

numPicBullet (Picture Numbering Symbol Definition)

This element specifies the appearance and behavior of a specific picture to be used as the numbering symbol within a numbering level definition in a document, and is the basis for all picture numbering symbol information in a WordprocessingML document.

This element is not used directly within abstract numbering definitions but rather is referenced through its numPicBulletId attribute by the lvlPicBulletId element (§2.9.10) used within numbering level definitions.

[Example: Consider the WordprocessingML fragment below which illustrates how a numPicBullet definition is referenced by a picture numbering symbol definition reference through its numPicBulletId attribute:

<w:numPicBullet w:numPicBulletId="1">

<w:pict>

<v:shape id="_x0000_i1031" type="#_x0000_t75" style="width:3in;height:276.75pt" o:bullet="t">

<v:imagedata r:id="rId2" o:title="testpic" />

</v:shape>

</w:pict>

</w:numPicBullet>

...

<w:abstractNum w:abstractNumId="7">

<w:nsid w:val="71A06359" />

<w:multiLevelType w:val="hybridMultilevel" />

<w:tmpl w:val="10643FE6" />

<w:lvl w:ilvl="0" w:tplc="B7663E56">

<w:start w:val="1" />

<w:nfc w:val="23" />

<w:lvlText w:val="" />

<w:lvlPicBulletId w:val="1" />

</w:lvl>

</w:abstractNum>

The lvlPicBulletId element references a numPicBullet element, which defines the size and appearance of all picture bullets of this type the document. It is important to note that this picture bullet may be referenced by multiple levels of various numbering definitions. end example]

Parent Elements

numbering (§2.9.17)

Child Elements

Subclause

pict (Picture Numbering Symbol Properties)

§2.9.23

Attributes

Description

numPicBulletId (Picture Numbering Symbol ID)

Specifies a unique ID for this picture bullet definition which shall be used to reference this picture bullet from a numbering level definition.

<w:numPicBullet w:numPicBulletId="1">

…

</w:numPicBullet>

...

<w:abstractNum w:abstractNumId="7">

<w:lvl w:ilvl="0" w:tplc="B7663E56">

…

<w:lvlPicBulletId w:val="1" />

</w:lvl>

</w:abstractNum>

The lvlPicBulletId element references the ID in the numPicBulletId attribute directly. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

numStyleLink (Numbering Style Reference)

This element specifies an abstract numbering does not contain the actual numbering properties for its type, but rather serves as a reference to a numbering style stored in the document, which shall be applied when this abstract numbering definition is referenced, and itself points at the actual underlying abstract numbering definition to be used.

The numbering style that is to be applied when this abstract numbering definition is referenced is identified by the string contained in numStyleLink's val attribute.

[Example: Consider the abstract numbering definition below:

<w:abstractNum w:abstractNumId="0"> <w:nsid w:val="38901FA4" /> <w:multiLevelType w:val="multilevel" /> <w:numStyleLink w:val="TestNumberingStyle" /></w:abstractNum>

This abstract numbering definition references the numbering style with a styleId attribute equal to TestNumberingStyle, as follows below:

<w:style w:type="numbering" w:styleId="TestNumberingStyle">

…

</w:style>

Therefore, this numbering style shall be applied whenever the base abstract numbering definition is inherited by a numbered paragraph. end example]

Parent Elements

abstractNum (§2.9.1)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

pict (Picture Numbering Symbol Properties)

This element specifies the properties for a picture which shall be used as a picture numbering symbol in a given document, using the VML syntax.

[Example: Consider the WordprocessingML below illustrating the usage of the pict element in a document containing a single picture numbering symbol:

<w:numPicBullet w:numPicBulletId="0">

<w:pict>

<v:shapetype id="_x0000_t75" coordsize="21600,21600" o:spt="75" o:preferrelative="t" path="m@4@5l@4@11@9@11@9@5xe" filled="f" stroked="f">

<v:stroke joinstyle="miter" />

<v:formulas>

<v:f eqn="if lineDrawn pixelLineWidth 0" />

<v:f eqn="sum @0 1 0" />

<v:f eqn="sum 0 0 @1" />

<v:f eqn="prod @2 1 2" />

<v:f eqn="prod @3 21600 pixelWidth" />

<v:f eqn="prod @3 21600 pixelHeight" />

<v:f eqn="sum @0 0 1" />

<v:f eqn="prod @6 1 2" />

<v:f eqn="prod @7 21600 pixelWidth" />

<v:f eqn="sum @8 21600 0" />

<v:f eqn="prod @7 21600 pixelHeight" />

<v:f eqn="sum @10 21600 0" />

</v:formulas>

<v:path o:extrusionok="f" gradientshapeok="t" o:connecttype="rect" />

<o:lock v:ext="edit" aspectratio="t" />

</v:shapetype>

<v:shape id="_x0000_i1029" type="#_x0000_t75" style="width:11.25pt;height:11.25pt" o:bullet="t">

<v:imagedata r:id="rId1" o:title="sample picture" />

</v:shape>

</w:pict>

end example]

Parent Elements

numPicBullet (§2.9.21)

Child Elements

Subclause

Any element from the urn:schemas-microsoft-com:vml namespace

§6.1

Any element from the urn:schemas-microsoft-com:office:office namespace

§6.2

control (Floating Embedded Control)

§2.3.3.2

movie (Embedded Video)

§2.3.3.17

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

pPr (Numbering Level Associated Paragraph Properties)

This element specifies the paragraph properties which shall be applied as part of a given numbering level within the parent numbering definition. These paragraph properties are applied to any numbered paragraph that references the given numbering definition and numbering level.

Paragraph properties specified on the numbered paragraph itself override the paragraph properties specified by pPr elements within a numbering lvl element (§2.9.6, §2.9.7).

[Example: Consider the WordprocessingML below which specifies numbering level paragraph properties:

<w:abstractNum w:abstractNumId="1">

...

<w:lvl w:ilvl="0">

...

<w:pPr>

<w:tabs>

<w:tab w:val="num" w:pos="720" />

</w:tabs>

<w:ind w:left="720" w:hanging="360" />

</w:pPr>

</w:lvl>

</w:abstractNum>

Each of the paragraph properties specified inside the pPr element are applied to any numbered paragraph which inherits this numbering level definition as part of the numbering properties in the order defined by the style hierarchy. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Child Elements

Subclause

adjustRightInd (Automatically Adjust Right Indent When Using Document Grid)

§2.3.1.1

autoSpaceDE (Automatically Adjust Spacing of Latin and East Asian Text)

§2.3.1.2

autoSpaceDN (Automatically Adjust Spacing of East Asian Text and Numbers)

§2.3.1.3

bidi (Right to Left Paragraph Layout)

§2.3.1.6

cnfStyle (Paragraph Conditional Formatting)

§2.3.1.8

contextualSpacing (Ignore Spacing Above and Below When Using Identical Styles)

§2.3.1.9

divId (Associated HTML div ID)

§2.3.1.10

framePr (Text Frame Properties)

§2.3.1.11

ind (Paragraph Indentation)

§2.3.1.12

jc (Paragraph Alignment)

§2.3.1.13

keepLines (Keep All Lines On One Page)

§2.3.1.14

keepNext (Keep Paragraph With Next Paragraph)

§2.3.1.15

kinsoku (Use East Asian Typography Rules for First and Last Character per Line)

§2.3.1.16

mirrorIndents (Use Left/Right Indents as Inside/Outside Indents)

§2.3.1.18

numPr (Numbering Definition Instance Reference)

§2.3.1.19

outlineLvl (Associated Outline Level)

§2.3.1.20

overflowPunct (Allow Punctuation to Extent Past Text Extents)

§2.3.1.21

pageBreakBefore (Start Paragraph on Next Page)

§2.3.1.23

pBdr (Paragraph Borders)

§2.3.1.24

pPrChange (Revision Information for Paragraph Properties)

§2.13.5.31

pStyle (Referenced Paragraph Style)

§2.3.1.27

rPr (Run Properties for the Paragraph Mark)

§2.3.1.29

sectPr (Section Properties)

§2.6.19

shd (Paragraph Shading)

§2.3.1.31

snapToGrid (Use Document Grid Settings for Inter-Line Paragraph Spacing)

§2.3.1.32

spacing (Spacing Between Lines and Above/Below Paragraph)

§2.3.1.33

suppressAutoHyphens (Suppress Hyphenation for Paragraph)

§2.3.1.34

suppressLineNumbers (Suppress Line Numbers for Paragraph)

§2.3.1.35

suppressOverlap (Prevent Text Frames From Overlapping)

§2.3.1.36

tabs (Set of Custom Tab Stops)

§2.3.1.38

textAlignment (Vertical Character Alignment on Line)

§2.3.1.39

textboxTightWrap (Allow Surrounding Paragraphs to Tight Wrap to Text Box Contents)

§2.3.1.40

textDirection (Paragraph Text Flow Direction)

§2.3.1.41

topLinePunct (Compress Punctuation at Start of a Line)

§2.3.1.43

widowControl (Allow First/Last Line to Display on a Separate Page)

§2.3.1.44

wordWrap (Allow Line Breaking At Character Level)

§2.3.1.45

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

pStyle (Paragraph Style's Associated Numbering Level)

This element specifies the name of a paragraph style which shall automatically this numbering level when applied to the contents of the document. When a paragraph style is defined to include a numbering definition, any numbering level defined by the numPr element (§2.3.1.19) shall be ignored, and instead this element shall specify the numbering level associated with that paragraph style.

If this element references a style which does not exist, or is not a paragraph style, then it may be ignored.

[Example: Consider the WordprocessingML below which specifies that the paragraph style with styleId example, when applied to paragraphs in the document, shall also apply the first numbering level of the abstract numbering definition with an abstractNumId equal to 1, as follows:

<w:abstractNum w:abstractNumId="1">

...

<w:lvl w:ilvl="0">

...

<w:pStyle w:val="example" />

<w:pPr>

<w:tabs>

<w:tab w:val="num" w:pos="720" />

</w:tabs>

<w:ind w:left="720" w:hanging="360" />

</w:pPr>

...

</w:lvl>

</w:abstractNum>

The style definition for the paragraph style would only include the numId of the numbering definition instance, and not its level:

<w:style w:styleId="example" w:type="paragraph"> … <w:pPr> <w:numPr> <w:numId w:val="0" /> </w:numPr> </w:pPr></w:style>

end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

rPr (Numbering Symbol Run Properties)

This element specifies the run properties which shall be applied to the numbering level's text specified in the lvlText element (§2.9.12) when it is applied to paragraphs in this document.

These run properties are applied to all numbering level text used by a given abstract numbering definition and numbering level. It should be noted that run properties specified on a numbered paragraph itself, or on text runs within a numbered paragraph, are separate from the run properties specified by rPr elements within a numbering level, as the latter affects only the numbering text itself, not the remainder of runs in the numbered paragraph.

[Example: Consider the WordprocessingML below which uses the rPr element to specify that the numbering symbol used within a given numbering level should be bold and of a 16 point font size:

<w:lvl w:ilvl="1">

…

<w:rPr>

<w:b />

<w:sz w:val="32" />

</w:rPr>

</w:lvl>

The resulting paragraph will use its regular paragraph formatting, but the numbering level text itself shall be specifically formatted as bold in 16 point font. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Child Elements

Subclause

b (Bold)

§2.3.2.1

bCs (Complex Script Bold)

§2.3.2.2

bdr (Text Border)

§2.3.2.3

caps (Display All Characters As Capital Letters)

§2.3.2.4

color (Run Content Color)

§2.3.2.5

cs (Use Complex Script Formatting on Run)

§2.3.2.6

dstrike (Double Strikethrough)

§2.3.2.7

eastAsianLayout (East Asian Typography Settings)

§2.3.2.8

effect (Animated Text Effect)

§2.3.2.9

em (Emphasis Mark)

§2.3.2.10

emboss (Embossing)

§2.3.2.11

fitText (Manual Run Width)

§2.3.2.12

highlight (Text Highlighting)

§2.3.2.13

i (Italics)

§2.3.2.14

iCs (Complex Script Italics)

§2.3.2.15

imprint (Imprinting)

§2.3.2.16

kern (Font Kerning)

§2.3.2.17

lang (Languages for Run Content)

§2.3.2.18

noProof (Do Not Check Spelling or Grammar)

§2.3.2.19

oMath (Office Open XML Math)

§2.3.2.20

outline (Display Character Outline)

§2.3.2.21

position (Vertically Raised or Lowered Text)

§2.3.2.22

rFonts (Run Fonts)

§2.3.2.24

rPrChange (Revision Information for Run Properties)

§2.13.5.32

rStyle (Referenced Character Style)

§2.3.2.27

rtl (Right To Left Text)

§2.3.2.28

shadow (Shadow)

§2.3.2.29

shd (Run Shading)

§2.3.2.30

smallCaps (Small Caps)

§2.3.2.31

snapToGrid (Use Document Grid Settings For Inter-Character Spacing)

§2.3.2.32

spacing (Character Spacing Adjustment)

§2.3.2.33

specVanish (Paragraph Mark Is Always Hidden)

§2.3.2.34

strike (Single Strikethrough)

§2.3.2.35

sz (Font Size)

§2.3.2.36

szCs (Complex Script Font Size)

§2.3.2.37

u (Underline)

§2.3.2.38

vanish (Hidden Text)

§2.3.2.39

vertAlign (Subscript/Superscript Text)

§2.3.2.40

w (Expanded/Compressed Text)

§2.3.2.41

webHidden (Web Hidden Text)

§2.3.2.42

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

start (Starting Value)

This element specifies the starting value for the numbering used by the parent numbering level within a given numbering level definition. This value is used when this level initially starts in a document, as well as whenever it is restarted via the properties set in the lvlRestart element (§2.9.11).

If this element is omitted, then the starting value shall be zero (0).

[Example: Consider the following WordprocessingML fragment for an abstract numbering definition:

<w:abstractNum w:abstractNumId="1">

…

<w:lvl w:ilvl="0">

<w:start w:val="2" />

<w:numFmt w:val="upperLetter"/>

…

</w:lvl>

</w:abstractNum>

In this example, since upper case Western letters (upperLetter) are being used as numbering symbols for this numbering level, the first instance of a numbering paragraph associated with this abstract numbering definition and numbering level would have the numbering symbol B, the second letter in the number format.

Subsequent numbered paragraphs with this abstract numbering definition and at this level would have their numbering symbols incremented from B (the starting value for this numbering level). end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

startOverride (Numbering Level Starting Value Override)

This element specifies the number which the specified level override shall begin with. This value is used when this level initially starts in a document, as well as whenever it is restarted via the properties set in the lvlRestart element (§2.9.11).

If they disagree, this value shall override the starting number of the child lvl element (§2.9.6).

[Example: Consider the WordprocessingML fragment for a numbering level definition in a WordprocessingML document:

<w:abstractNum w:abstractNumId="1">

…

<w:lvl w:ilvl="0">

…

<w:numFmt w:val="upperRoman" />

<w:start w:val="2" />

…

</w:lvl>

</w:abstractNum>

In this example, since upper case Roman numerals (upperRoman) are being used as numbering symbols for this numbering level, the first instance of a numbering paragraph associated with this abstract numbering definition and numbering level would have the numbering symbol II, the second letter in the number format.

Subsequent numbered paragraphs with this abstract numbering definition and at this level would have their numbering symbols incremented from II (the starting value for this numbering level). end example]

Parent Elements

lvlOverride (§2.9.9)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

styleLink (Numbering Style Definition)

This element specifies that the parent abstract numbering definition is the base numbering definition for the specified numbering style referenced in its val attribute.

If this element is omitted, or it references a style which does not exist, then this numbering definition shall not be the underlying properties for a numbering style.

[Note: Numbering styles are never directly referenced by paragraphs or runs in the document – instead, an abstract numbering definition specifies that it contains the underlying numbering information for a numbering style, and one or more numbering definition instances reference a numbering definition which inherits from it. The numbering style itself is just a friendly name on an abstract numbering definition. end note]

[Example: Consider the WordprocessingML fragment below, representing an abstract numbering definition which defines the properties for a numbering style:

<w:numbering>

…

<w:abstractNum w:abstractNumId="5">

…

<w:styleLink w:val="ExampleNumberingStyle" />

…

</w:abstractNum>

</w:numbering>

…

<w:styles>

…

<w:style w:type="numbering" w:styleId="ExampleNumberingStyle">

<w:name w:val="ExampleNumberingStyle" />

…

<w:pPr>

<w:numPr>

<w:numId w:val="6" />

</w:numPr>

</w:pPr>

</w:style>

…

</w:styles>

The styleLink element specifies that the abstract numbering definition defines the properties for a numbering style whose styleId matches its val attribute, and is defined in the styles element of the WordprocessingML. end example]

Parent Elements

abstractNum (§2.9.1)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

suff (Content Between Numbering Symbol and Paragraph Text)

This element specifies the content which shall be added between a given numbering level's text and the text of every numbered paragraph which references that numbering level.

If this element is omitted, then its value shall be assumed to be tab.

[Example: Consider the numbered paragraph below:

In this example, a space exists between the numbering symbol 1. and the numbered paragraph text Test. The space would be specified in WordprocessingML as follows:

<w:lvl w:ilvl="0">

…

<w:suff w:val="space" />

…

</w:lvl>

The suff element with an attribute value of space specifies that the character between the numbering's level text and the paragraph text shall be a space. end example]

Parent Elements

lvl (§2.9.6); lvl (§2.9.7)

Attributes

Description

val (Character Type Between Numbering and Text)

Specifies the character which shall follow the list number.

[Example: Consider a numbered for which a tab exists between the numbering symbol and the numbered paragraph's text. The tab would be specified in WordprocessingML as follows:

<w:lvl w:ilvl="0">

…

<w:suff w:val="tab" />

…

</w:lvl>

The val attribute with a value of tab specifies that the character between the numbering's level text and the paragraph text shall be a tab. This tab will follow normal tab stop rules. end example]

The possible values for this attribute are defined by the ST_LevelSuffix simple type (§2.18.53).

The following XML Schema fragment defines the contents of this element:

</complexType>

tmpl (Numbering Template Code)

This element specifies a unique hexadecimal code which may be used to determine a location within application user interface in which this abstract numbering definition shall be displayed.

If this element is omitted, then this abstract numbering definition may be displayed in any location chosen by the consumer.

[Example: Consider the following abstract numbering definition:

<w:abstractNum w:abstractNumId="1">

…

<w:tmpl w:val="CA48B6BA" />

…

</w:abstractNum>

Parent Elements

abstractNum (§2.9.1)

Attributes

Description

val (Long Hexadecimal Number Value)

Specifies a number value specified as a four digit hexadecimal number), whose contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following value for an attribute of type ST_LongHexNumber: 00BE2C6C.

The possible values for this attribute are defined by the ST_LongHexNumber simple type (§2.18.57).

The following XML Schema fragment defines the contents of this element:

</complexType>

Headers and Footers

Headers and footers refer to text, graphics or data (such as page number, date, document title, and so on) that can appear at the top or bottom of each page in a WordprocessingML document.

A header appears in the top margin (above the main document content on the page), while a footer appears in the bottom margin of a document page (below the main document content on the page).

Since WordprocessingML is a flow-based format, headers and footers are applied by specifying the headers and footers for all pages in a particular section of a document.

Within each section of a document there may be up to three different types of headers and footers:

First page header/footer

Odd page header/footer

Even page header/footer

First page headers and footers specify a unique header or footer which shall appear on the first page of a section. Odd page headers and footers specify a unique header and footer which shall appear on all odd numbered pages for a given section. Even page headers and footers specify a unique header and footer which shall appear on all even numbered pages in a given section.

evenAndOddHeaders (Different Even/Odd Page Headers and Footers)

This element specifies whether sections in this document shall have different headers and footers for even and odd pages (an odd page header/footer and an even page header/footer).

If the val attribute is set to true, then each section in the document shall use an odd page header for all odd numbered pages in the section, and an even page header for all even numbered pages in the section (counting each page in the section starting from one, regardless of the page numbering settings for the section). If the val attribute is set to false, then all pages in a section shall use the odd page header.

This setting does not affect the presence of a first page header on each section, which is specified using the titlePg element (§2.10.6). If a first page header is specified, then all subsequent pages shall have this setting applied, including the first page in the odd/even page count.

If this element is set to false and an even page header is specified , then it shall be ignored and only the odd page header shall be displayed. Conversely, if this element is set to true and either header type is omitted for a given section, then a blank header shall be created as needed (another header type shall not be used in its place).

If this element is omitted, then its value shall be assumed to be false.

[Example: Consider a document which shall have a different even and odd page header for each section in its contents. This requirement must be specified using the following WordprocessingML:

<w:settings> … <w:evenAndOddHeaders /> …</w:setttings>

Since the evenAndOddHeaders property is set (and its default value is true), this document will now have different headers and footers for even and odd pages. end example]

Parent Elements

settings (§2.15.1.78)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

footerReference (Footer Reference)

This element specifies a single footer which shall be associated with the current section in the document. This footer shall be referenced via the id attribute, which specifies an explicit relationship to the appropriate Footer part in the WordprocessingML package.

If the relationship type of the relationship specified by this element is not http://schemas.openxmlformats.org/officeDocument/2006/footer, is not present, or does not have a TargetMode attribute value of Internal, then the document shall be considered non-conformant.

Within each section of a document there may be up to three different types of footers:

First page footer

Odd page footer

Even page footer

The footer type specified by the current footerReference is specified via the type attribute.

If any type of footer is omitted for a given section, then the following rules shall apply.

If no footerReference for the first page footer is specified and the titlePg element is specified, then the first page footer shall be inherited from the previous section or, if this is the first section in the document, a new blank footer shall be created. If the titlePg element is not specified, then no first page footer shall be shown, and the odd page footer shall be used in its place.

If no footerReference for the even page footer is specified and the evenAndOddHeaders element is specified, then the even page footer shall be inherited from the previous section or, if this is the first section in the document, a new blank footer shall be created. If the evenAndOddHeaders element is not specified, then no even page footer shall be shown. and the odd page footer shall be used in its place.

If no footerReference for the odd page footer is specified then the even page footer shall be inherited from the previous section or, if this is the first section in the document, a new blank footer shall be created.

[Example: Consider a three page document with different first, odd, and even page footers defined as follows:

This document defines three footers, each of have a relationship from the document part with a unique relationship ID, as shown in the following packaging markup:

…

…

</Relationships>

These relationships are then referenced in the section's properties using the following WordprocessingML:

<w:sectPr>

…

<w:footerReference r:id="rId6" w:type="first" />

<w:footerReference r:id="rId7" w:type="default" />

<w:footerReference r:id="rId10" w:type="even" />

…

</w:sectPr>

The resulting section shall use the footer part with relationship id rId6 for the first page, the footer part with relationship id rId10 for all subsequent even pages, and the footer part with relationship id rId7 for all subsequent odd pages. end example]

Parent Elements

sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

type (Header or Footer Type)

Specifies the type of header or footer specified by the target relationship ID. This type determines the page(s) on which the current header or footer shall be displayed.

If any section contains more than a single header or footer of each type, then the document shall be considered non-conformant.

[Example: Consider a document with the following WordprocessingML:

<w:sectPr>

…

<w:footerReference r:id="rId6" w:type="first" />

<w:footerReference r:id="rId7" w:type="first" />

<w:footerReference r:id="rId10" w:type="even" />

…

</w:sectPr>

The resulting section has two footers of type first, and therefore is invalid. end example]

[Example: Consider a WordprocessingML section which specifies the following header reference:

<w:headerReference r:id="rId10" w:type="first" />

The resulting section shall use the specified header part for the first page. end example]

The possible values for this attribute are defined by the ST_HdrFtr simple type (§2.18.41).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

ftr (Footer)

This element specifies the content for a single footer for use within one or more sections of a WordprocessingML document.

Within the ftr element, the content of the element is similar to the content of the body (§2.2.2) element, and contains what is referred to as block-level markup - markup which can exist as a sibling element to paragraphs in a WordprocessingML document.

[Example: Consider the following simple one page document with one footer:

This document defines one footer with the text footer. The footer contents are stored in a unique footer part. The resulting footer is represented by the following WordprocessingML:

<w:ftr> <w:p> <w:r> <w:t>Footer</w:t> </w:r> </w:p></w:ftr>

Since footers are containers of block level contents, all block level elements can be used within them. In this particular example, the content is a single paragraph. end example]

[Example: Consider a more complex three page document with different first, odd, and even page footers defined:

This document defines three footers stored in three different footer parts. The resulting footers are represented by the following WordprocessingML:

First page footer part:

<w:ftr> <w:p> <w:r> <w:t>First</w:t> </w:r> </w:p></w:ftr>

Even page footer part:

<w:ftr> <w:p> <w:r> <w:t>Even</w:t> </w:r> </w:p></w:ftr>

Odd page footer part:

<w:ftr> <w:p> <w:r> <w:t>Odd</w:t> </w:r> </w:p></w:ftr>

end example]

Parent Elements

Root element of WordprocessingML Footer part

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

The following XML Schema fragment defines the contents of this element:

</complexType>

hdr (Header)

This element specifies the content for a single header for use within one or more sections of a WordprocessingML document.

Within the hdr element, the content of the element is similar to the content of the body (§2.2.2) element, and contains what is referred to as block-level markup - markup which can exist as a sibling element to paragraphs in a WordprocessingML document.

[Example: Consider the following simple one page document with one header:

This document defines one header with the text Header. The header's contents is stored in a unique Header part. The resulting header is represented by the following WordprocessingML:

<w:hdr> <w:p> <w:r> <w:t>Header</w:t> </w:r> </w:p></w:hdr>

Since headers are containers of block level contents, all block level elements can be used within them. In this particular example, the content is a single paragraph. end example]

[Example: Consider a more complex three page document with different first, odd, and even page headers defined:

This document defines three headers stored in three different header parts. The resulting headers are represented by the following WordprocessingML:

First page header part:

<w:hdr> <w:p> <w:r> <w:t>First</w:t> </w:r> </w:p></w:hdr>

Even page header part:

<w:hdr> <w:p> <w:r> <w:t>Even</w:t> </w:r> </w:p></w:hdr>

Odd page header part:

<w:hdr> <w:p> <w:r> <w:t>Odd</w:t> </w:r> </w:p></w:hdr>

end example]

Parent Elements

Root element of WordprocessingML Header part

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

The following XML Schema fragment defines the contents of this element:

</complexType>

headerReference (Header Reference)

This element specifies a single header which shall be associated with the current section in the document. This header shall be referenced via the id attribute, which specifies an explicit relationship to the appropriate Header part in the WordprocessingML package.

If the relationship type of the relationship specified by this element is not http://schemas.openxmlformats.org/officeDocument/2006/header, is not present, or does not have a TargetMode attribute value of Internal, then the document shall be considered non-conformant.

Within each section of a document there may be up to three different types of headers:

First page header

Odd page header

Even page header

The header type specified by the current headerReference is specified via the type attribute.

If any type of header is omitted for a given section, then the following rules shall apply.

If no headerReference for the first page header is specified and the titlePg element is specified, then the first page header shall be inherited from the previous section or, if this is the first section in the document, a new blank header shall be created. If the titlePg element is not specified, then no first page header shall be shown, and the odd page header shall be used in its place.

If no headerReference for the even page header is specified and the evenAndOddHeaders element is specified, then the even page header shall be inherited from the previous section or, if this is the first section in the document, a new blank header shall be created. If the evenAndOddHeaders element is not specified, then no even page header shall be shown, and the odd page header shall be used in its place.

If no headerReference for the odd page header is specified then the even page header shall be inherited from the previous section or, if this is the first section in the document, a new blank header shall be created.

[Example: Consider a three page document with different first, odd, and even page header defined as follows:

This document defines three headers, each of have a relationship from the document part with a unique relationship ID, as shown in the following packaging markup:

…

…

</Relationships>

These relationships are then referenced in the section's properties using the following WordprocessingML:

<w:sectPr>

…

<w:headerReference r:id="rId3" w:type="first" />

<w:headerReference r:id="rId5" w:type="default" />

<w:headerReference r:id="rId2" w:type="even" />

…

</w:sectPr>

The resulting section shall use the header part with relationship id rId3 for the first page, the header part with relationship id rId2 for all subsequent even pages, and the header part with relationship id rId5 for all subsequent odd pages. end example]

Parent Elements

sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

id (Relationship to Part)

Namespace: .../officeDocument/2006/relationships

Specifies the relationship ID to a specified part.

The specified relationship shall match the type required by the parent element:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/footer for the footerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/header for the headerReference element

http://schemas.openxmlformats.org/officeDocument/2006/relationships/font for the embedBold, embedBoldItalic, embedItalic, or embedRegular elements

http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings for the printerSettings element

[Example: Consider an XML element which has the following id attribute:

<… r:id="rId10" />

The markup specifies the associated relationship part with relationship ID rId1 contains the corresponding relationship information for the parent XML element. end example]

The possible values for this attribute are defined by the ST_RelationshipId simple type (§7.8.2.1).

type (Header or Footer Type)

Specifies the type of header or footer specified by the target relationship ID. This type determines the page(s) on which the current header or footer shall be displayed.

If any section contains more than a single header or footer of each type, then the document shall be considered non-conformant.

[Example: Consider a document with the following WordprocessingML:

<w:sectPr>

…

<w:footerReference r:id="rId6" w:type="first" />

<w:footerReference r:id="rId7" w:type="first" />

<w:footerReference r:id="rId10" w:type="even" />

…

</w:sectPr>

The resulting section has two footers of type first, and therefore is invalid. end example]

[Example: Consider a WordprocessingML section which specifies the following header reference:

<w:headerReference r:id="rId10" w:type="first" />

The resulting section shall use the specified header part for the first page. end example]

The possible values for this attribute are defined by the ST_HdrFtr simple type (§2.18.41).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

titlePg (Different First Page Headers and Footers)

This element specifies whether the parent section in this document shall have a different header and footer for its first page.

If the val attribute is set to true, then the parent section in the document shall use a first page header for the first page in the section. If the val attribute is set to false, then the first page in the parent section shall use the odd page header.

This setting does not affect the presence of even and odd page header on all sections, which is specified using the evenAndOddHeaders element (§2.10.1).

If this element is set to false and a first page header is specified , then it shall be ignored and only the odd page header shall be displayed. Conversely, if this element is set to true and the first page header type is omitted for the given section, then a blank header shall be created as needed (another header type shall not be used in its place).

If this element is omitted, then its value shall be assumed to be false.

[Example: Consider a section which shall have a different first page header. This requirement is specified using the following WordprocessingML:

<w:sectPr> … <w:titlePg /> …</w:sectPr>

Since the titlePg property is present (and its default attribute value is true), this document will now have a different header and footer for its first page. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

Footnotes and Endnotes

Footnotes and endnotes are separate text storied used in documents and books to show the source of borrowed material or to enter explanatory or supplementary information which does not interrupt the normal reading flow of the document.

Footnotes are typically located at the bottom of a page or beneath text being referenced, and endnotes are typically placed at the end of a document or at the end of a section. If document has been divided up into one or more sections, each section of a document may contain endnotes.

Both footnotes and endnotes consist of two parts:

A note reference mark in the body text to indicate that additional information is in a footnote or endnote, with a numbering system used for each to tell readers whether to look for the note at the end of the page or the end of the document or section.

The actual footnote or endnote story content.

[Example: Example of a footnote applied to text in a document:

The note reference mark follows the noted text and specifies that there is associated footnote information, and the footnote itself is at the bottom of the current page. end example]

[Example: Consider the following example of an endnote applied to text in a document:

The note reference mark follows the noted text and specifies that there is associated endnote information, and the endnote itself is at the end of the current section. end example]

continuationSeparator (Continuation Separator Mark)

This element specifies the presence of a continuation separator mark within the current run. A continuation separator mark is a horizontal line which spans the width of the main story's text extents.

[Note: The continuation separator mark is typically used within the context of continuation separator footnotes or endnotes. These footnote and endnote types define the footnote/endnote used to separate the contents of the main document story from continuation of footnotes or endnotes which began on a previous page. end note]

[Example: Consider the following two pages in a document, where some text is referenced by a footnote that extends to the next page (with the continuation separator circled in red):

The line separating the document text from the footnote that is continued on the next page is represented by the following WordprocessingML:

<w:footnote w:type="continuationSeparator" w:id="1">

<w:p>

<w:r>

<w:continuationSeparator />

</w:r>

</w:p>

</w:footnote>

In this example, the footnote has a content which consists of a single continuationSeparator, which is displayed as a horizontal line across the text extents. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

The following XML Schema fragment defines the contents of this element:

endnote (Endnote Content)

This element specifies the content of a single endnote within a WordprocessingML document. Each endnote shall be represented by a single endnote element, which may contain any valid block-level content.

[Example: Consider a document with a single endnote, identified by a endnote element, defined in the endnotes part:

<w:endnotes> <w:endnote w:id="2"> <w:p> <w:pPr> <w:pStyle w:val="EndnoteText" /> </w:pPr> <w:r> <w:rPr> <w:rStyle w:val="EndnoteReference" /> </w:rPr> <w:endnoteRef /> </w:r> <w:r> <w:t xml:space="preserve">This is an endnote</w:t> </w:r> </w:p> </w:endnote></w:endnotes>

This endnote contains an endnote reference mark, as well as the endnote text This is an endnote. end example]

Parent Elements

endnotes (§2.11.8)

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

Attributes

Description

id (Footnote/Endnote ID)

Specifies a unique ID which shall be used to match the contents of a footnote or endnote to the associated footnote/endnote reference mark in the document using the footnoteRef or endnoteRef element, as appropriate.

If this attribute is omitted, then this footnote or endnote shall have no ID. If more than one footnote shares the same ID, then this document shall be considered non-conformant. If more than one endnote shares the same ID, then this document shall be considered non-conformant.

[Example: Consider the following footnote as defined in the footnotes part:

<w:footnotes>

<w:footnote w:type="normal" w:id="0">

…

</w:footnote>

…

</w:footnotes>

The contents of this footnote are associated with the footnoteReference with a matching ID, as follows:

<w:p> <w:r> <w:footnoteReference w:id="0" /> </w:r></w:p>

The resulting paragraph will have a footnote reference mark which references the footnote number value of the footnote with an id of 0. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

type (Footnote/Endnote Type)

Specifies the type of footnote or endnote contained within the current footnote or endnote content definition.

If this attribute is omitted, then it shall be considered to be of type normal. If a footnote or endnote is not of type normal, then it shall not be referenced by a footnoteReference or endnoteReference element within the main document story.

[Example: Consider the following example of a footnote defined in a WordprocessingML document as follows:

<w:footnote w:type="continuationSeparator" w:id="1">

<w:p>

<w:r>

<w:continuationSeparator />

</w:r>

</w:p>

</w:footnote>

In this example, the footnote is of type continuationSeparator and shall be used by a consumer to separate continued footnotes from the main document contents (see simple type for full details). end example]

The possible values for this attribute are defined by the ST_FtnEdn simple type (§2.18.37).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

endnote (Special Endnote List)

This element specifies the ID for all endnotes which are located in the current document that are not of type normal. Each other type of endnote shall be referenced in this list, or it shall not be loaded. If an endnote is not listed beneath this element, and it is required by the document content, then the document shall be considered non-conformant.

[Example: Consider a document that has three endnotes represented by the following WordprocessingML:

<w:endnotes ...>

<w:endnote w:type="separator" w:id="0">

...

</w:endnote>

<w:endnote w:type="continuationSeparator" w:id="1">

...

</w:endnote>

<w:endnote w:id="2">

...

</w:endnote>

</w:endnotes>

Each of the endnotes which are not of type normal must be specified in the endnotePr element, as follows:

<w:endnotePr>

<w:endnote w:id="0" />

<w:endnote w:id="1" />

</w:endnotePr>

This indicates to the consumer that the endnotes with an id attribute value of 0 and 1 are special endnotes, and should be treated accordingly. end example]

Parent Elements

endnotePr (§2.11.4)

Attributes

Description

id (Footnote/Endnote ID)

If more than one footnote shares the same ID, then this document shall be considered non-conformant. If more than one endnote shares the same ID, then this document shall be considered non-conformant.

[Example: Consider the following footnote as defined in the footnotes part:

<w:footnotes>

<w:footnote w:type="normal" w:id="0">

…

</w:footnote>

…

</w:footnotes>

The contents of this footnote are associated with the footnoteReference with a matching ID, as follows:

<w:p> <w:r> <w:footnoteReference w:id="0" /> </w:r></w:p>

The resulting paragraph will have a footnote reference mark which references the footnote number value of the footnote with an id of 0. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

endnotePr (Document-Wide Endnote Properties)

This element specifies the endnote properties for the current document. Each of these properties are stored as a child element within the endnotePr element.

These properties may be overridden for a specific section via the section-wide endnotePr element (§2.11.5).

[Example: Consider the following document with two sections, where the endnotes for each section appears at the end of that section and use lower case roman numerals:

Since both sections are identical, the endnote properties are specified as document-wide level properties (this is not necessary but is most efficient) as follows:

<w:settings>

…

<w:endnotePr>

<w:numFmt w:val="lowerRoman" />

<w:pos w:val="sectEnd"/>

</w:endnotePr>

…

</w:settings>

Note that the pos element could have been omitted since it is using its default value. end example]

Parent Elements

settings (§2.15.1.78)

Child Elements

Subclause

endnote (Special Endnote List)

§2.11.3

numFmt (Endnote Numbering Format)

§2.11.18

numRestart (Footnote and Endnote Numbering Restart Location)

§2.11.19

numStart (Footnote and Endnote Numbering Starting Value)

§2.11.20

pos (Endnote Placement)

§2.11.22

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

endnotePr (Section-Wide Endnote Properties)

This element specifies the endnote properties for the current section. Each of these properties are an override of the document-wide endnote properties (§2.11.4) and are stored as a child element within the endnotePr element.

If this element is omitted for a given section, then that section shall use the endnote properties defined at the document-wide level.

[Example: Consider a document consisting of three sections, which has endnotes in the first section which use lowercase roman numerals, and endnotes in the third section which use the Chicago Manual of Style format. The WordprocessingML for each section would be specified as follows:

<w:sectPr> <w:endnotePr> <w:numFmt w:val="lowerRoman" /> </w:endnotePr></w:sectPr>

…<w:sectPr> …</w:sectPr>

This assumes that the document-wide endnote settings are specified to use the Chicago Manual of Style format, as follows:

<w:settings> <w:endnotePr> <w:numFmt w:val="chicago" /> </w:endnotePr></w:settings>

The resulting document would override the endnote numbering format for the first section to lowerRoman, but would use the chicago endnote numbering format for section three (and would also use it for section two if that section had endnotes. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Child Elements

Subclause

numFmt (Endnote Numbering Format)

§2.11.18

numRestart (Footnote and Endnote Numbering Restart Location)

§2.11.19

numStart (Footnote and Endnote Numbering Starting Value)

§2.11.20

pos (Endnote Placement)

§2.11.22

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

endnoteRef (Endnote Reference Mark)

This element specifies the presence of an endnote reference mark. An endnote reference mark is a run of automatically numbered text which follows the numbering format set forth via the numFmt element (§2.11.18).

If an endnote reference mark is specified within a run which is not part of an endnote, then that endnote reference mark may be ignored.

[Example: Consider the following document where some text is referenced by an endnote at the end of the document:

The endnote reference mark is the lower case roman numeral within the actual endnote itself in the diagram above. The contents of the endnote (including the endnote reference mark) are represented by the following WordprocessingML:

<w:endnote w:id="2">

<w:p>

<w:pPr>

<w:pStyle w:val="EndnoteText" />

</w:pPr>

<w:r>

<w:rPr>

<w:rStyle w:val="EndnoteReference" />

</w:rPr>

<w:endfootnoteRef />

</w:r>

<w:r>

<w:t>Cool reference</w:t>

</w:r>

</w:p>

</w:endnote>

The resulting endnote contains the literal endnote content of Cool reference, preceding by an automatically numbered endnote reference mark. Since this is the first endnote in the document, that automatically numbered reference mark uses the lower case roman numeral i. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

The following XML Schema fragment defines the contents of this element:

endnoteReference (Endnote Reference)

This element specifies the presence of an endnote reference. An endnote reference is a run of automatically numbered text which references a particular endnote within the parent document, and inherits the endnote reference mark's numbering.

If an endnote reference is specified within a footnote or endnote, then the document shall be considered non-conformant.

[Example: Consider the following document where some text is referenced by an endnote at the end of the document:

The endnote reference is the lower case roman numeral within the document content in the diagram above. The contents of the paragraph which contains the endnote reference are represented by the following WordprocessingML:

<w:p> <w:r> <w:t>This text is followed by an endnote</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="EndnoteReference" /> </w:rPr> <w:endnoteReference w:id="2" /> </w:r> <w:r> <w:t>.</w:t> </w:r></w:p>

The resulting paragraph contains the literal text content of This text is followed by an endnote, followed by an automatically numbered endnote reference. Since this is the first endnote in the document, that automatically numbered reference inherits the lower case roman numeral i from the endnote reference mark. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

customMarkFollows (Suppress Footnote/Endnote Reference Mark)

Specifies that the current footnote or endnote shall not have an associated footnote or endnote reference mark, as appropriate.

This attribute shall be used to specify that a particular footnote or endnote shall not increment the numbering for its associated footnote/endnote numbering format, so that the use of a footnote with a custom footnote mark does not cause a missing value in the footnote/endnote values. The display of the mark is specified via the footnoteRef/endnoteRef elements, as appropriate.

If this attribute is omitted, then the footnote or endnote reference mark shall not be skipped when incrementing over this footnote or endnote.

[Example: Consider a footnote with an id value of 1 that uses a custom footnote mark:

<w:footnotes>

<w:footnote w:id="0">

…

</w:footnote>

<w:footnote w:suppressRef="1" w:id="2">

…

</w:footnote>

<w:footnote w:id="2">

…

</w:footnote>

</w:footnotes>

If the numbering format for footnotes in this document is upperRoman, then the first footnote shall be I, the second is suppressed, and the third is II, noticing that the second does not increment the numbering sequence. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

id (Footnote/Endnote ID Reference)

Specifies the footnote or endnote which is being referenced by the current footnote or endnote reference in the document.

If the resulting footnote or endnote ID is not present in the footnotes or endnote part (as appropriate), then this document shall be considered non-conformant.

[Example: Consider a paragraph with an endnote reference, represented by the following WordprocessingML:

<w:p> <w:r> <w:t>This text is followed by an endnote</w:t> </w:r> <w:r> <w:endnoteReference w:id="2" /> </w:r> <w:r> <w:t>.</w:t> </w:r></w:p>

This text references the endnote in the document's endnotes part which has an id value of 2. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

endnotes (Document Endnotes)

This element specifies the set of all endnotes in the document, including endnote separators and continuation notices. This element is the root node for the Endnotes part.

[Example: Consider the following example of the contents of the endnotes part:

<w:endnotes> <w:endnote w:type="separator" w:id="0"> … </w:endnote> <w:endnote w:type="continuationSeparator" w:id="1"> … </w:endnote> <w:endnote w:id="2"> … </w:endnote></w:endnotes>

The endnotes part contains the definition for one normal endnote, as well as the separator and continuation separator endnote for this document. end example]

Parent Elements

Root element of WordprocessingML Endnotes part

Child Elements

Subclause

endnote (Endnote Content)

§2.11.2

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

footnote (Special Footnote List)

This element specifies the ID for all footnotes which are located in the current document that are not of type normal. Each other type of footnote shall be referenced in this list, or it shall not be loaded. This means that if a special footnote is not listed beneath this element, and it is required by the document content, then the document shall be considered non-conformant.

[Example: Consider a document that has three footnotes represented by the following WordprocessingML:

<w:footnotes>

<w:footnote w:type="separator" w:id="0">

...

</w:footnote>

<w:footnote w:type="continuationSeparator" w:id="1">

...

</w:footnote >

<w:footnote w:id="2">

...

</w:footnote>

</w:footnotes>

Each of the footnotes which are not of type normal must be specified in the footnotePr element, as follows:

<w:footnotePr>

<w:footnote w:id="0" />

<w:footnote w:id="1" />

</w:footnotePr>

This indicates to the consumer that the footnotes with an id attribute value of 0 and 1 are special footnotes, and should be treated accordingly. end example]

Parent Elements

footnotePr (§2.11.11)

Attributes

Description

id (Footnote/Endnote ID)

[Example: Consider the following footnote as defined in the footnotes part:

<w:footnotes>

<w:footnote w:type="normal" w:id="0">

…

</w:footnote>

…

</w:footnotes>

The contents of this footnote are associated with the footnoteReference with a matching ID, as follows:

<w:p> <w:r> <w:footnoteReference w:id="0" /> </w:r></w:p>

The resulting paragraph will have a footnote reference mark which references the footnote number value of the footnote with an id of 0. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

footnote (Footnote Content)

This element specifies the content of a single footnote within a WordprocessingML document. Each footnote shall be represented by a single footnote element, which may contain any valid block-level content.

[Example: Consider a document with a single footnote, identified by a footnote element, defined in the footnotes part as follows:

<w:footnotes> <w:footnote w:id="2"> <w:p> <w:pPr> <w:pStyle w:val="FootnoteText" /> </w:pPr> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference" /> </w:rPr> <w:footnoteRef /> </w:r> <w:r> <w:t xml:space="preserve">This is a sample footnote</w:t> </w:r> </w:p> </w:footnote></w:footnotes>

This footnote contains an footnote reference mark, as well as the endnote text This is a sample footnote. end example]

Parent Elements

footnotes (§2.11.15)

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

Attributes

Description

id (Footnote/Endnote ID)

[Example: Consider the following footnote as defined in the footnotes part:

<w:footnotes>

<w:footnote w:type="normal" w:id="0">

…

</w:footnote>

…

</w:footnotes>

The contents of this footnote are associated with the footnoteReference with a matching ID, as follows:

<w:p> <w:r> <w:footnoteReference w:id="0" /> </w:r></w:p>

The resulting paragraph will have a footnote reference mark which references the footnote number value of the footnote with an id of 0. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

type (Footnote/Endnote Type)

Specifies the type of footnote or endnote contained within the current footnote or endnote content definition.

[Example: Consider the following example of a footnote defined in a WordprocessingML document as follows:

<w:footnote w:type="continuationSeparator" w:id="1">

<w:p>

<w:r>

<w:continuationSeparator />

</w:r>

</w:p>

</w:footnote>

The possible values for this attribute are defined by the ST_FtnEdn simple type (§2.18.37).

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

footnotePr (Document-Wide Footnote Properties)

This element specifies the footnote properties for this document. Each property is stored as a unique element within the footnotePr element.

These properties may be overridden for a specific section via the section-wide footnotePr element (§2.11.12).

[Example: Consider the following one page document, where the footnote appears beneath the text it references:

Since the document consists of a single footnote, the footnote properties may be stored in either the section-wide or document-wide footnote properties. Assuming that they are stored in the latter, the footnote properties are represented by the following WordprocessingML:

<w:settings>

…

<w:footnotePr>

<w:pos w:val="beneathText" />

</w:footnotePr>

…

</w:settings>

The footnote properties specify that footnotes will appear below the noted text end example]

Parent Elements

settings (§2.15.1.78)

Child Elements

Subclause

footnote (Special Footnote List)

§2.11.9

numFmt (Footnote Numbering Format)

§2.11.17

numRestart (Footnote and Endnote Numbering Restart Location)

§2.11.19

numStart (Footnote and Endnote Numbering Starting Value)

§2.11.20

pos (Footnote Placement)

§2.11.21

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

footnotePr (Section-Wide Footnote Properties)

This element specifies the footnote properties for the current section. Each of these properties are an override of the document-wide footnote properties (§2.11.11) and are stored as a child element within the footnotePr element.

If this element is omitted for a given section, then that section shall use the footnote properties defined at the document-wide level.

[Example: Consider a document consisting of three sections, which has footnotes in the first section which appear below text, and footnotes in the third section which appear at the bottom of the page. The WordprocessingML for each section would be specified as follows:

<w:sectPr> <w:footnotePr> <w:pos w:val="beneathText" /> </w:footnotePr></w:sectPr>

…<w:sectPr> …</w:sectPr>

This assumes that the document-wide footnote settings are specified as the default positioning at the bottom of the page by omitting the pos element (§2.11.21), as follows:

<w:settings> <w:footnotePr> … </w:footnotePr></w:settings>

The resulting document would override the footnote positioning for the first section to beneathText, but would use the pageBottom footnote positioning for section three (and would also use it for section two if that section had footnotes. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Child Elements

Subclause

numFmt (Footnote Numbering Format)

§2.11.17

numRestart (Footnote and Endnote Numbering Restart Location)

§2.11.19

numStart (Footnote and Endnote Numbering Starting Value)

§2.11.20

pos (Footnote Placement)

§2.11.21

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

footnoteRef (Footnote Reference Mark)

This element specifies the presence of a footnote reference mark. A footnote reference mark is a run of automatically numbered text which follows the numbering format set forth via the footnote numFmt element (§2.11.17).

If a footnote reference mark is specified within a run which is not part of a footnote, then that footnote reference mark may be ignored.

[Example: Consider the following document where some text is referenced by an footnote at the end of the page:

The footnote reference mark is the decimal number within the actual footnote itself in the image above. The contents of the footnote (including the footnote reference mark) are represented by the following WordprocessingML:

<w:footnote w:id="2">

<w:p>

<w:pPr>

<w:pStyle w:val="FootnoteText" />

</w:pPr>

<w:r>

<w:rPr>

<w:rStyle w:val="FootnoteReference" />

</w:rPr>

<w:footnoteRef />

</w:r>

<w:r>

<w:t>Cool reference</w:t>

</w:r>

</w:p>

</w:footnote>

The resulting footnote contains the literal endnote content of Cool reference, preceding by an automatically numbered footnote reference mark. Since this is the first footnote in the document, that automatically numbered reference mark uses the first decimal number 1. It is also important to note that the use of styles FootnoteText and FootnoteReference is not required, these may simply be added by a particular producer automatically to give the footnote contents are particular style (just like any other use of styles). end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

The following XML Schema fragment defines the contents of this element:

footnoteReference (Footnote Reference)

This element specifies the presence of a footnote reference. A footnote reference is a run of automatically numbered text which references a particular footnote within the parent document, and inherits the footnote reference mark's numbering.

If an footnote reference is specified within a footnote or endnote, then the document shall be considered non-conformant.

[Example: Consider the following document where some text is referenced by a footnote at the bottom of the page:

The footnote reference is the superscript decimal number within the document content in the diagram above. The contents of the paragraph which contains the footnote reference are represented by the following WordprocessingML:

<w:p> <w:r> <w:t>Some referenced text.</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference" /> </w:rPr> <w:footnoteReference w:id="2" /> </w:r></w:p>

The resulting paragraph contains the literal text content of Some referenced text., followed by an automatically numbered footnote reference. Since this is the first footnote in the document, that automatically numbered reference inherits the decimal number 1 from the footnote reference mark. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

customMarkFollows (Suppress Footnote/Endnote Reference Mark)

Specifies that the current footnote or endnote shall not have an associated footnote or endnote reference mark, as appropriate.

If this attribute is omitted, then the footnote or endnote reference mark shall not be skipped when incrementing over this footnote or endnote.

[Example: Consider a footnote with an id value of 1 that uses a custom footnote mark:

<w:footnotes>

<w:footnote w:id="0">

…

</w:footnote>

<w:footnote w:suppressRef="1" w:id="2">

…

</w:footnote>

<w:footnote w:id="2">

…

</w:footnote>

</w:footnotes>

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

id (Footnote/Endnote ID Reference)

Specifies the footnote or endnote which is being referenced by the current footnote or endnote reference in the document.

If the resulting footnote or endnote ID is not present in the footnotes or endnote part (as appropriate), then this document shall be considered non-conformant.

[Example: Consider a paragraph with an endnote reference, represented by the following WordprocessingML:

<w:p> <w:r> <w:t>This text is followed by an endnote</w:t> </w:r> <w:r> <w:endnoteReference w:id="2" /> </w:r> <w:r> <w:t>.</w:t> </w:r></w:p>

This text references the endnote in the document's endnotes part which has an id value of 2. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

footnotes (Document Footnotes)

This element specifies the set of all footnotes in the document, including footnote separators and continuation notices. This element is the root node for the Footnotes part.

[Example: Consider the following example of the contents of the footnotes part:

<w:footnotes> <w:footnote w:type="separator" w:id="0"> … </w:footnote > <w:footnote w:type="continuationSeparator" w:id="1"> … </w:footnote> <w:footnote w:id="2"> … </w:footnote></w:footnotes>

The footnotes part contains the definition for one normal footnote, as well as the separator and continuation separator footnotes for this document. end example]

Parent Elements

Root element of WordprocessingML Footnotes part

Child Elements

Subclause

footnote (Footnote Content)

§2.11.10

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

noEndnote (Suppress Endnotes In Document)

This element specifies that all endnotes in this document shall not be displayed or printed. If this element is placed on any section break other than the first section break in the document, it shall be ignored.

If this element is omitted, endnotes shall not be suppressed in the current document.

[Example: Consider a document in which in the first section endnotes are marked to be hidden:

<w:sectPr>

<w:noEndnote />

</w:sectPr>

In this example, this document will not display endnotes. end example]

Parent Elements

sectPr (§2.6.17); sectPr (§2.6.18); sectPr (§2.6.19)

Attributes

Description

val (On/Off Value)

Specifies a binary value for the property defined by the parent XML element.

A value of off, 0, or false specifies that the property shall be explicitly turned off.

[Example: For example, consider the following on/off property:

<w:… w:val="off"/>

The val attribute explicitly declares that the property is turned off. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</complexType>

numFmt (Footnote Numbering Format)

This element specifies the numbering format which shall be used to determine the footnote or endnote reference mark value for all automatically numbered footnote and endnote reference marks (those without the suppressRef attribute set).

If this element is omitted, then the numbering format shall be assume to be decimal.

[Example: Consider the following footnote reference with the number format set to upper case letters:

This footnote numbering format is specified by the following WordprocessingML:

<w:footnotePr> <w:numFmt w:val="upperLetter" /></w:footnotePr>

end example]

Parent Elements

footnotePr (§2.11.11); footnotePr (§2.11.12)

Attributes

Description

val (Numbering Format Type)

Specifies the number format that shall be used for all numbering in the parent object.

[Example: A value of lowerLetter indicates that a consumer shall use lowercase letters for each number in this grouping: a,b,c… end example]

The possible values for this attribute are defined by the ST_NumberFormat simple type (§2.18.66).

The following XML Schema fragment defines the contents of this element:

</complexType>

numFmt (Endnote Numbering Format)

If this element is omitted, then the numbering format shall be assume to be decimal.

[Example: Consider the following footnote reference with the number format set to upper case letters:

This footnote numbering format is specified by the following WordprocessingML:

<w:footnotePr> <w:numFmt w:val="upperLetter" /></w:footnotePr>

end example]

Parent Elements

endnotePr (§2.11.4); endnotePr (§2.11.5)

Attributes

Description

val (Numbering Format Type)

Specifies the number format that shall be used for all numbering in the parent object.

[Example: A value of lowerLetter indicates that a consumer shall use lowercase letters for each number in this grouping: a,b,c… end example]

The possible values for this attribute are defined by the ST_NumberFormat simple type (§2.18.66).

The following XML Schema fragment defines the contents of this element:

</complexType>

numRestart (Footnote and Endnote Numbering Restart Location)

This element specifies when all automatic numbering for the footnote or endnote reference marks shall be restarted. When restarted, the next automatically numbered footnote or endnote in the document (each type is handled independently) shall restart to the specified numStart value (§2.11.20).

If this element is omitted, then automatic numbering shall not be restarted between each page or section (a vlaue of continuous).

[Example: Consider the following two page document where the numbering shall be reset after each page to its starting value:

The footnote automatic restarting of the numbering is represented by the following WordprocessingML:

<w:footnotePr>

<w:numRestart w:val="eachPage" />

</w:footnotePr>

end example]

Parent Elements

endnotePr (§2.11.4); endnotePr (§2.11.5); footnotePr (§2.11.11); footnotePr (§2.11.12)

Attributes

Description

val (Automatic Numbering Restart Value)

Specifies when the automatic numbering shall be restarted for the current set of footnotes or endnotes.

[Example: Consider a WordprocessingML document where the numbering for its endnotes shall be restarted after each section shall be restarted after each page. This setting is represented by the following WordprocessingML:

<w:footnotePr>

<w:numRestart w:val="eachSect" />

</w:footnotePr>

The val attribute value of eachSect specifies that numbering shal be restarted after each section. end example]

The possible values for this attribute are defined by the ST_RestartNumber simple type (§2.18.81).

The following XML Schema fragment defines the contents of this element:

</complexType>

numStart (Footnote and Endnote Numbering Starting Value)

This element specifies the starting number or character for the first automatically numbered footnotes or endnote in the document, as well as the first automatically numbered footnotes after each restart point specified by the numRestart element (§2.11.19). This value shall be specified in decimal number units, then translated accordingly to the appropriate numbering format.

If this element is omitted, then the starting value shall be 1.

[Example: Consider the following footnote reference with the number format set to upper case letters and starting character set to D:

The number format is specified by the following WordprocessingML:

<w:footnotePr>

<w:numFmt w:val="upperLetter" />

<w:numStart w:val="4" />

</w:footnotePr>

Since D is the fourth letter in the alphabet, the starting character is set to 4. end example]

Parent Elements

endnotePr (§2.11.4); endnotePr (§2.11.5); footnotePr (§2.11.11); footnotePr (§2.11.12)

Attributes

Description

val (Decimal Number Value)

Specifies that the contents of this attribute will contain a decimal number.

The contents of this decimal number are interpreted based on the context of the parent XML element.

[Example: Consider the following numeric WordprocessingML property of type ST_DecimalNumber:

<w:… w:val="1512645511" />

The value of the val attribute is a decimal number whose value must be interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

pos (Footnote Placement)

This element specifies where footnotes shall be placed on the page when they are referenced by text in the current document.

If this element is present at the section level, then it shall be ignored.

If this element is omitted at the document level, then footnotes shall be located at the bottom of the current page.

[Example: Consider the following one page document, where the footnote appears beneath the text that it is referencing:

The footnote references the text reading Some reference text. and is represented by the following WordprocessingML:

<w:p> <w:r> <w:t>Some referenced text</w:t> </w:r> <w:r> <w:rPr> <w:rStyle w:val="FootnoteReference" /> </w:rPr> <w:footnoteReference w:id="2" /> </w:r></w:p>

Since the footnote location must be beneath the current text, the section properties shall be declared as follows:

<w:settings> … <w:footnotePr> <w:pos w:val="beneathText" /> </w:footnotePr> …</w:sectPr>

The footnote references the footnote in the footnotes part with an id attribute value equal to 2. Within the section properties of the document, the position of footnotes is specified to be beneath the page's text. end example]

Parent Elements

footnotePr (§2.11.11); footnotePr (§2.11.12)

Attributes

Description

val (Footnote Position Type)

Specifies the position of footnotes in the document.

[Example: Consider a document in which footnotes shall be positioned beneath their text. The footnote properties for this document shall be declared as follows:

<w:sectPr> <w:footnotePr> <w:pos w:val="beneathText" /> </w:footnotePr> …</w:sectPr>

The val attribute is beneathText, therefore the position of footnotes is specified to be beneath the page's text. end example]

The possible values for this attribute are defined by the ST_FtnPos simple type (§2.18.38).

The following XML Schema fragment defines the contents of this element:

</complexType>

pos (Endnote Placement)

This element specifies where endnotes shall be placed on the page when they are referenced by text in the current document.

If this element is present at the section level, then it shall be ignored.

If this element is omitted at the document level, then endnotes shall be located at the end of the document.

[Example: Consider the following multi-page, multi-section document, where the endnote appears at the end of the section in which it is referenced:

The endnote setting is the same for all sections, and is represented by the following WordprocessingML at the document level:

<w:settings> … <w:endnotePr> <w:pos w:val="sectEnd" /> … </w:endnotePr> …</w:settings>

Within the properties of the document, the position of endnotes is specified to be at the end of each section. end example]

Parent Elements

endnotePr (§2.11.4); endnotePr (§2.11.5)

Attributes

Description

val (Endnote Position Type)

Specifies the position of endnotes on the parent section or the document.

[Example: Consider a document in which endnotes shall be positioned at the end of the section. The section properties for this section shall be declared as follows:

<w:settings>

<w:endnotePr>

<w:pos w:val="endSect" />

</w:endnotePr>

…

</w:settings>

The val attribute is endSect, therefore the position of endnotes is specified to be at the end of the section. end example]

The possible values for this attribute are defined by the ST_EdnPos simple type (§2.18.26).

The following XML Schema fragment defines the contents of this element:

</complexType>

separator (Footnote/Endnote Separator Mark)

This element specifies the presence of a separator mark within the current run. A separator mark is a horizontal line which spans part of the width text extents.

[Note: The separator mark is typically used within the context of separator footnotes or endnotes. These footnote and endnote types define the footnote/endnote used to separate the contents of the main document story from the contents of footnotes or endnotes on that page. end note]

[Example: Consider the following page in a document, where some text is referenced by a footnote that is located at the bottom of the current page (with the separator circled in red):

The line separating the document text from the normal footnotes is the footnote separator, and is represented by the following WordprocessingML:

<w:footnote w:type="separator" w:id="0">

<w:p>

<w:r>

<w:separator />

</w:r>

</w:p>

</w:footnote>

In this example, the footnote has a content which consists of a single separator, which is displayed as a horizontal line across part of the text extents. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

The following XML Schema fragment defines the contents of this element:

Glossary Document

Within a WordprocessingML file, the glossary document is a supplemental storage location for additional document content which shall travel with the document, but which shall not be displayed for printed as part of the main document until it is explicitly added to that document by deliberate action.

The glossary document shall also be afforded a separate instance of all of the relationships which are provided on the main document part - this means that the glossary document shall have its own style definitions, numbering definitions, comments, headers, footers, etc. within the WordprocessingML document.

[Example: Consider a document which shall include ten optional clauses that may be inserted through a user interface. It is clearly not desirable to have these ten clauses appear in the main document story's contents before they are explicitly inserted, therefore each of them may be stored in the glossary document and inserted via the user interface as needed. end example]

Within the glossary document, each distinct region of document content is referred to as a glossary document entry, and is defined via the docPart element (§2.12.5). These document parts may contain any block-level WordprocessingML element, and may also have a set of classifications and behaviors applied to them via the glossary document entry's properties.

[Example: Consider the following definition for the contents of a glossary document part within a WordprocessingML document:

<w:glossaryDocument> <w:docParts> <w:docPart> <w:docPartPr> … </w:docPartPr> <w:docPartBody> <w:p> <w:r> <w:t>Sample entry.</w:t> </w:r> </w:p> </w:docPartBody> </w:docPart> <w:docPart> … </w:docPart> </w:docParts></w:glossaryDocument>

The glossaryDocument element (§2.12.10) defines the contents of the glossary document part. Within the glossary document, each docPart element contains the definition for one glossary document entry: in this case, there are two entries in the glossary document, the first of which contains a single paragraph with a single run of text. end example]

behavior (Entry Insertion Behavior)

This element specifies a single behavior which shall be applied to the contents of the parent glossary document entry (§2.12.5) when it is added to the main document story of a WordprocessingML document. These behaviors shall be used to format the surrounding WordprocessingML around insertion, and do not require the presence of a user interface (i.e. applications without a user interface shall also utilize these settings).

[Example: Consider the WordprocessingML fragment for a glossary document entry containing a single run, defined as follows:

<w:docPart> <w:docPartPr> <w:behaviors> <w:behavior w:val="p"/> </w:behavior> … </w:docPartPr> <w:docPartBody> <w:p> <w:r> <w:t>Sample entry.</w:t> </w:r> </w:p> </w:docPartBody></w:docPart>

The behavior element has a value of p, which specifies that the contents of the parent glossary document entry shall be inserted in their own paragraph when they are added to the contents of a document. If the document content to which they are added is defined as follows (and the part is added between the two text runs):

<w:body> <w:p> <w:r> <w:t>After this text</w:t> </w:r> <w:r> <w:t>Before this text</w:t> </w:r> </w:p></w:body>

This setting specifies that although the part would normally be inserted between the two existing runs in the paragraph, that behavior shall ensure that the part is inserted into its own paragraph, resulting in the following WordprocessingML:

<w:body> <w:p> <w:r> <w:t>After this text</w:t> </w:r> </w:p> <w:p> <w:r> <w:t>Sample entry.</w:t> </w:r> </w:p> <w:p> <w:r> <w:t>Before this text</w:t> </w:r> </w:p></w:body>

end example]

Parent Elements

behaviors (§2.12.2)

Attributes

Description

val (Insertion Behavior Value)

Specifies the insertion behavior which shall be associated with the current glossary document entry.

[Example: Consider the WordprocessingML fragment for a glossary document entry's properties, defined as follows:

<w:docPartPr> <w:behaviors> <w:behavior w:val="content"/> </w:behavior></w:docPartPr>

The val attribute value of content specifies that the insertion of this glossary document entry shall include only the content (the last paragraph in the part shall be merged into the current paragraph in the document). end example]

The possible values for this attribute are defined by the ST_DocPartBehavior simple type (§2.18.19).

The following XML Schema fragment defines the contents of this element:

</complexType>

behaviors (Entry Insertion Behaviors)

This element specifies the set of behaviors which shall be applied to the contents of the parent glossary document entry (§2.12.5) when it is added to the main document story of a WordprocessingML document. Since multiple behaviors can be specified for a single part, the sum total of all behaviors shall be used to insert the parent entry into the contents of the WordprocessingML document.

[Example: Consider the WordprocessingML fragment for a glossary document entry containing a single run, defined as follows:

<w:docPart> <w:docPartPr> <w:behaviors> <w:behavior w:val="p" /> <w:behavior w:val="pg" /> </w:behavior> … </w:docPartPr> <w:docPartBody> <w:p> <w:r> <w:t>Sample entry.</w:t> </w:r> </w:p> </w:docPartBody></w:docPart>

The behaviors element contains the set of behaviors which shall be applied to this entry when it is inserted into the document, in this case:

The entry shall be inserted into its own paragraph in the document

The entry shall be inserted onto a new page in the document (i.e. it shall be preceded by a page break)

end example]

Parent Elements

docPartPr (§2.12.7)

Child Elements

Subclause

behavior (Entry Insertion Behavior)

§2.12.1

The following XML Schema fragment defines the contents of this element:

</choice>

</complexType>

category (Entry Categorization)

This element specifies the categorization for the parent glossary document entry. This categorization shall not imply any behaviors around the entry, and is only used to organize the set of glossary document entries within an application or user interface (i.e. to disambiguate between two entries with the same entry name (§2.12.13)).

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:category> … </w:category> …<w:docPartPr>

The category element specifies the categorization applied to the current entry, for the purposes of classification or user interface sorting, for example. end example]

Parent Elements

docPartPr (§2.12.7)

Child Elements

Subclause

gallery (Gallery Associated With Entry)

§2.12.9

name (Category Associated With Entry)

§2.12.12

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

description (Description for Entry)

This element specifies a description for the contents of this glossary document entry. This description may contain any string content, and allows the entry to have additional information contained within the definition for this glossary document entry. [Note: This description may be surfaced in a user interface, for example. end note]

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> … <w:name w:val="Sample Entry" /> <w:description w:val="This is an example of a glossary document entry for example purposes." /> …<w:docPartPr>

The description element specifies that the long description associated with the parent entry shall be This is an example of a glossary document entry for example purposes. This value may be used as needed by an application, for example, to display in a user interface. end example]

Parent Elements

docPartPr (§2.12.7)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

docPart (Glossary Document Entry)

This element specifies the details for a single glossary document entry contained in the document. This glossary document entry may consist of one or both of the following:

The glossary document entry's properties, which define its name, categorization, and behaviors

The glossary document entry's contents, which consists of one or more block-level elements of WordprocessingML content

Each of these two components is specified by one of the child elements of this element, as seen in the child elements table below.

[Example: Consider the following definition for the contents of a Glossary Document part within a WordprocessingML document:

<w:glossaryDocument> <w:docParts> <w:docPart> … </w:docPart> <w:docPart> … </w:docPart> </w:docParts></w:glossaryDocument>

The docPart element uniquely defines one glossary document entry within the glossary document part, therefore there are two unique entries stored in the current example of a glossary document part. end example]

Parent Elements

docParts (§2.12.8)

Child Elements

Subclause

docPartBody (Contents of Glossary Document Entry)

§2.12.6

docPartPr (Glossary Document Entry Properties)

§2.12.7

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

docPartBody (Contents of Glossary Document Entry)

This element specifies the contents of the parent glossary document entry (§2.12.5). These contents shall consist of one or more block-level elements, analogous to the body element (§2.2.2) of the main document story for the current document.

[Example: Consider the WordprocessingML fragment for a glossary document entry containing a single run, defined as follows:

<w:docPart> … <w:docPartBody> <w:p> <w:r> <w:t>Sample entry.</w:t> </w:r> </w:p> </w:docPartBody></w:docPart>

The docPartBody element specifies the block-level elements which comprise the contents of the current glossary document entry, in this case, a single paragraph using the p element (§2.3.1.22). end example]

When the contents of a glossary document entry are added to a document, the styles, numbering definitions, and all other related parts for this entry shall be taken from the relationships from the Glossary Document part and not from the main document part. These references shall be moved to their main document equivalents when the entry is added to the document.

When the part is inserted, it shall be inserted as though its last paragraph mark does not exist (the content of the final paragraph mark shall be merged with the contents of the paragraph into which this entry is being added).

[Example: Consider the WordprocessingML fragment for a glossary document entry containing a single run, defined as follows:

<w:docPart> <w:docPartPr> <w:behaviors> <w:behavior w:val="p"/> </w:behavior> … </w:docPartPr> <w:docPartBody> <w:p> <w:r> <w:t>Sample entry.</w:t> </w:r> </w:p> </w:docPartBody></w:docPart>

If this entry is inserted into document content to which is defined as follows (and the part is added between the two text runs):

<w:body> <w:p> <w:r> <w:t>After this text</w:t> </w:r> <w:r> <w:t>Before this text</w:t> </w:r> </w:p></w:body>

This entry has only a single paragraph, which is removed before insertion, and barring any special insertion behaviors (§2.12.2), only the text run is inserted, resulting in the following WordprocessingML:

<w:body> <w:p> <w:r> <w:t>After this text</w:t> </w:r> <w:r> <w:t>Sample entry.</w:t> </w:r> <w:r> <w:t>Before this text</w:t> </w:r> </w:p></w:body>

end example]

Parent Elements

docPart (§2.12.5)

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

sectPr (Document Final Section Properties)

§2.6.18

tbl (Table)

§2.4.36

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

docPartPr (Glossary Document Entry Properties)

This element specifies the set of properties which shall be applied to the parent glossary document entry. These properties define its name, categorization, and behaviors.

[Example: Consider the WordprocessingML fragment for a glossary document entry containing a single run, defined as follows:

<w:docPart> <w:docPartPr> <w:name w:val="Sample Entry" /> … </w:docPartPr> …</w:docPart>

The docPartPr element specifies the set of properties which have been specified for the parent glossary document entry, the only one visible above being the entry's name of Sample Entry. end example]

Parent Elements

docPart (§2.12.5)

Child Elements

Subclause

behaviors (Entry Insertion Behaviors)

§2.12.2

category (Entry Categorization)

§2.12.3

description (Description for Entry)

§2.12.4

guid (Entry ID)

§2.12.11

name (Entry Name)

§2.12.13

style (Associated Paragraph Style Name)

§2.12.14

types (Entry Types)

§2.12.16

The following XML Schema fragment defines the contents of this element:

</choice>

</complexType>

docParts (List of Glossary Document Entries)

This element specifies the collection of glossary document entries which are stored in the current Glossary Document part.

[Example: Consider the following definition for the contents of a glossary document part within a WordprocessingML document:

<w:glossaryDocument> <w:docParts> <w:docPart> … </w:docPart> <w:docPart> … </w:docPart> </w:docParts></w:glossaryDocument>

The docParts element defines the set of entries which are stored in the glossary document part. end example]

Parent Elements

glossaryDocument (§2.12.10)

Child Elements

Subclause

docPart (Glossary Document Entry)

§2.12.5

The following XML Schema fragment defines the contents of this element:

</choice>

</complexType>

gallery (Gallery Associated With Entry)

This element specifies the predefined gallery into which the current glossary document part shall be classified. This classification, although its enumeration values may be interpreted to imply semantics around the contents of the parent glossary document entry, shall only be used to classify and sort this entry (via an application or a user interface).

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:category> <w:gallery w:val="coverPg" /> <w:name w:val="Internal Memo Covers" /> </w:category> …<w:docPartPr>

The gallery element with a value of coverPg specifies that the gallery categorization applied to the current entry, for the purposes of classification or user interface sorting, puts this entry into the Cover Pages classification. end example]

Parent Elements

category (§2.12.3)

Attributes

Description

val (Gallery Value)

Specifies the classification of gallery which shall be associated with the parent glossary document entry.

[Example: Consider the following WordprocessingML fragment for a single glossary document entry:

<w:gallery w:val="custom1" />

The val attribute with a value of custom1 specifies that the gallery categorization applied to the current entry is the Custom 1 classification. end example]

The possible values for this attribute are defined by the ST_DocPartGallery simple type (§2.18.20).

The following XML Schema fragment defines the contents of this element:

</complexType>

glossaryDocument (Glossary Document Root Element)

This element specifies the root element for a glossary document part within a WordprocessingML document. A glossary document is an supplementary document story in a WordprocessingML that shall be afforded all of the relationships of the Main Document part, such as:

Style definitions

Numbering definitions

Comments

Headers/footers

Etc.

The entries stored in this part shall have all of its implicit relationships target these parts, rather than their analogues stored off of the main document part.

[Example: Consider the following definition for the contents of a glossary document part within a WordprocessingML document:

<w:glossaryDocument> <w:docParts> <w:docPart> … </w:docPart> <w:docPart> … </w:docPart> </w:docParts></w:glossaryDocument>

The glossaryDocument element defines the contents of the glossary document part. end example]

Parent Elements

Root element of WordprocessingML Glossary Document part

Child Elements

Subclause

background (Document Background)

§2.2.1

docParts (List of Glossary Document Entries)

§2.12.8

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

guid (Entry ID)

This element specifies a unique identifier (specified using a 128-bit GUID stored on the val attribute) that uniquely identifies this document building block.[Note: This unique identifier may be used by an application to uniquely reference a single building block regardless of different naming, for example when the same part has different names for localization purposes. end note]

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> … <w:guid w:val="{00000000-5BD2-4BC8-9F70-7020E1357FB2}" /> …<w:docPartPr>

The guid element specifies that the unique identifier associated with the parent entry shall be {00000000-5BD2-4BC8-9F70-7020E1357FB2}. This value may be used as needed by an application, for example, to uniquely identify a part regardless of its name. end example]

Parent Elements

docPartPr (§2.12.7)

Attributes

Description

val (GUID Value)

Specifies a 128-bit globally unique identifier (GUID) value as defined by the simple type referenced below. The contents of this GUID shall be interpreted based on the context of the parent XML element.

If this attribute is omitted, its value shall be assumed to be null (i.e. no GUID shall be associated with the parent XML element).

[Example: Consider the following WordprocessingML element:

<… w:val="{6A9B8B6F-5BD2-4BC8-9F70-7020E1357FB2}"/>

The val attribute value of {6A9B8B6F-5BD2-4BC8-9F70-7020E1357FB2} shall be associated with the context of the parent XML element. end example]

The possible values for this attribute are defined by the ST_Guid simple type (§2.18.39).

The following XML Schema fragment defines the contents of this element:

</complexType>

name (Category Associated With Entry)

This element specifies the category into which the current glossary document part shall be classified. This classification may consist of any string value as determined by its contents, and shall only be used to classify and sort this entry (via an application or a user interface).

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:category> <w:gallery w:val="coverPg" /> <w:name w:val="Internal Memo Covers" /> </w:category> …<w:docPartPr>

The name element with a value of Internal Memo Covers specifies that the category grouping applied to the current entry, for the purposes of classification or user interface sorting, puts this entry into the Internal Memo Covers classification. This category may be used as desired. end example]

Parent Elements

category (§2.12.3)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

name (Entry Name)

This element specifies a name for the contents of this glossary document entry. This name may contain any string content, and allows the entry to have a friendly identifier contained within the definition for this glossary document entry. [Note: This name may be surfaced in a user interface, for example. end note]

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> … <w:name w:val="Sample Entry" /> <w:description w:val="This is an example of a glossary document entry for example purposes." /> …<w:docPartPr>

The name element specifies that the friendly name associated with the parent entry shall be Sample Entry. This value may be used as needed by an application, for example, to display in a user interface. end example]

Parent Elements

docPartPr (§2.12.7)

Attributes

Description

decorated (Built-In Entry)

Specifies that the name for the current entry is a built-in entry which should not be displayed in the user interface. [Note: This information may be used by an application as needed, for example, to disambiguate an entry from one with the same name, ensuring that the built-in entry can be uniquely identified by the application. end note]

If this attribute is omitted, its value shall be assumed to be false.

[Example: Consider the following WordprocessingML fragment for the name of a single glossary document entry:

<w:name w:decorated="true" w:val=":-)" />

The decorated attribute specifies that the parent entry is a built-in entry, and shall be treated as such. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

val (Name Value)

Specifies a string value which contains the name of the current glossary document entry.

[Example: Consider the following WordprocessingML fragment for the name of a single glossary document entry:

<w:name w:val="Sample Entry" />

The val attribute specifies that the name of the parent entry is Sample Entry. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

style (Associated Paragraph Style Name)

This element specifies the style ID for a paragraph style which shall be associated with the current glossary document entry. This paragraph style associated shall not imply anything about the formatting or content of the glossary document entry, and shall only be used to filter and/or sort this entry (via an application or a user interface). [Note: One example of the level of classification offered by this element is to only show it as available when the formatting of the paragraph matches the specified style. end note]

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:style w:val="Heading1" /> …<w:docPartPr>

The style element with a val attribute value of Heading1 specifies that the paragraph style associated with the current glossary document entry shall be the style whose style ID is equal to Heading1. end example]

Parent Elements

docPartPr (§2.12.7)

Attributes

Description

val (String Value)

Specifies that its contents will contain a string.

The contents of this string are interpreted based on the context of the parent XML element.

[Example: Consider the following WordprocessingML fragment:

<w:pPr>

<w:pStyle w:val="heading1" />

</w:pPr>

The value of the val attribute is the ID of the associated paragraph style's styleId.

However, consider the following fragment:

<w:sdtPr>

<w:alias w:val="SDT Title Example" />

...

</w:sdtPr>

In this case, the decimal number in the val attribute is the caption of the parent structured document tag. In each case, the value is interpreted in the context of the parent element. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</complexType>

type (Entry Type)

This element specifies a single type which shall be applied to the properties of the parent glossary document entry (§2.12.5). Each of these types may, based on their values, influence the visibility and behavior of the parent glossary document entry as defined by the associated simple type information.

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:types> <w:type w:val="bbPlcHdr" /> </w:types> …<w:docPartPr>

The type element with a value of bbPlcHdr specifies that the parent glossary document entry shall be treated as if it was the placeholder text for one or more structured document tags in the document. end example]

Parent Elements

types (§2.12.16)

Attributes

Description

val (Type Value)

Specifies the value for the current entry type.

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:type w:val="bbPlcHdr" />

The val attribute value of bbPlcHdr specifies that the parent glossary document entry shall be treated as if it was the placeholder text for one or more structured document tags in the document. end example]

The possible values for this attribute are defined by the ST_DocPartType simple type (§2.18.21).

The following XML Schema fragment defines the contents of this element:

</complexType>

types (Entry Types)

This element specifies the set of types which shall be applied to the properties of the parent glossary document entry (§2.12.5). Each of these types may, based on their values, influence the visibility and behavior of the parent glossary document entry.

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:types> … </w:types> …<w:docPartPr>

The types element specifies the set of entry types which shall be associated with the parent glossary document entry. end example]

Parent Elements

docPartPr (§2.12.7)

Child Elements

Subclause

type (Entry Type)

§2.12.15

Attributes

Description

all (Entry Is Of All Types)

Specifies that the current glossary document is all types. This attribute shall override any information specified as child elements of this element and shall ensure that the current entry is associated with all available types.

If this attribute is omitted, then its default value shall be assumed to be false.

[Example: Consider the following WordprocessingML fragment for the properties of a single glossary document entry:

<w:docPartPr> <w:types w:all="true"> <w:type w:val="autoExp" />

</w:types> …<w:docPartPr>

The types element contains a single entry type definition, but because the all attribute is present with a value of true, that type is augmented to place the parent entry into all possible types. end example]

The possible values for this attribute are defined by the ST_OnOff simple type (§2.18.67).

The following XML Schema fragment defines the contents of this element:

</choice>

</complexType>

Annotations

Within a WordprocessingML document, annotations refer to various types of supplementary markup which may be stored inside or around a region of text within the document's contents. [Example: The types of supplementary information stored within a document may include: comments, revisions, spelling and/or grammatical errors, bookmark information and optional editing permissions. end example]

Within a document's contents, annotations are stored in one of three different methods:

Inline

"Cross Structure"

Properties

These three forms are needed in order to maintain compatibility with both the legacy annotations functionality of current word processing applications and the requirements of an XML-based format (i.e. wellformedness of the resulting XML markup). These three forms are referenced within the individual annotation types described in the following sub clauses.

Inline Annotations

Inline annotations describe all annotations which do not require special handling in order to maintain the XML wellformedness requirements of the resulting WordprocessingML output. In these cases, a single XML element shall encapsulate the entire contents of the document content which is being annotated.

[Example: Consider the following WordprocessingML markup for a paragraph which reads The quick brown fox jumps over the jet lagged dog., where jet lagged replaced the previous text lazy when the editing application was tracking revisions:

<w:p> <w:r> <w:t xml:space="preserve">The quick brown fox jumps over the </w:t> </w:r> <w:del … > <w:r> <w:delText>lazy</w:delText> </w:r> </w:del> <w:ins … > <w:r> <w:t>jet lagged</w:t> </w:r> </w:ins> <w:r> <w:t xml:space="preserve"> dog.</w:t> </w:r></w:p>

The del and ins elements (§2.13.5.12; §2.13.5.20) each fully encapsulate the extent of their respective annotations (a marked deletion and insertion, respectively), as they are inline annotations. end example]

"Cross Structure" Annotations

"Cross structure" annotations describe the class of annotations which can span portions of WordprocessingML markup [Example: Cross structure annotations may span parts of multiple paragraphs, one half of a custom XML markup element's contents, etc. end example]. In these cases, the annotation's region is delimited by two elements: a start element and an end element. These two elements mark the start and end points of the annotated content, but do not contain it. The pairing of the start and end marker are linked via a common value for their id attributes.

[Example: Consider the following WordprocessingML markup for two paragraphs, each reading Example Text, where a bookmark has been added spanning the second word in paragraph one and the first word in paragraph two:

<w:p> <w:r> <w:t>Example</w:t> </w:r> <w:bookmarkStart w:id="0" w:name="sampleBookmark" /> <w:r> <w:t xml:space="preserve"> text.</w:t> </w:r></w:p><w:p> <w:r> <w:t>Example</w:t> </w:r> <w:bookmarkEnd w:id="0" /> <w:r> <w:t xml:space="preserve"> text.</w:t> </w:r></w:p>

The bookmarkStart and bookmarkEnd elements (§2.13.6.2; §2.13.6.1) specify the location where the bookmark starts and ends, but cannot contain it because it spans part of two paragraphs. They are part of one group because the id attribute value specifies 0 for both. end example]

Property Annotations

Property annotations describe the class of annotations which are stored as a property on an object [Example: Property annotations may appear on paragraph properties, run properties, table rows, etc. end example] In these cases, the annotation's semantics are defined by the property, as they can affect content and/or formatting.

[Example: Consider the following WordprocessingML markup for a paragraph reading Example Text, where the first word had the bold property applied when the editing application was tracking revisions:

<w:p> <w:r> <w:rPr> <w:b/> <w:rPrChange … > <w:rPr/> </w:rPrChange> </w:rPr> <w:t>Example</w:t> </w:r> <w:r> <w:t xml:space="preserve"> text.</w:t> </w:r></w:p>

The rPrChange element (§2.13.5.32; §2.13.5.33) contains the set of previously applied revision properties associated with a particular author at a particular time. It is stored itself as a property on the parent run which was modified. end example]

Comments

Comments describe annotations which are anchored to a region of document content, but which contain an arbitrary amount of block-level content stored in their own separate document stories. Within a WordprocessingML document, comments are stored in a separate Comments part within the document package.

A comment in a WordprocessingML document is divided into two components:

The comment anchor (the text on which the comment applies)

The comment content (the contents of the comment)

The comment anchor is the cross structure annotation which defines the region of text on which the comment in anchored. The comment content is the content stored in the comments part which contains the actual content of the comment.

[Example: Consider a paragraph in a WordprocessingML document whose second word is annotated with a comment:

The first component to this comment is the document content which defines the extents of the comment and references the specific comment in the comments part:

<w:p> <w:r> <w:t xml:space="preserve">Some </w:t> </w:r> <w:commentRangeStart w:id="0" /> <w:r> <w:t>text.</w:t> </w:r> <w:commentRangeEnd w:id="0" /> <w:r> <w:commentReference w:id="0" /> </w:r></w:p>

The commentRangeStart and commentRangeEnd elements (§2.13.4.4; §2.13.4.3) delimit the run content to which the comment with an id of 0 applies (in this case, the single run of text). The following commentReference element (§2.13.4.5) links the preceding run content with a comment in the comments part with an id of 0. Without all three of these elements, the range and comment cannot be linked (although the first two elements are optional, in which case the comment shall be anchored at the comment reference mark)

The second component to this comment is the comment content which defines the text in the comment:

<w:comment w:id="0" w:author="Joe Smith" w:date="2006-04-06T13:50:00Z" w:initials="User">

<w:p>

<w:pPr>

<w:pStyle w:val="CommentText" />

</w:pPr>

<w:r>

<w:rPr>

<w:rStyle w:val="CommentReference" />

</w:rPr>

<w:annotationRef />

</w:r>

<w:r>

<w:t>comment</w:t>

</w:r>

</w:p>

</w:comment>

In this example, the comment specifies that it was inserted by author Joe Smith with the initials User via the author and date attributes. It is linked to the run content via the id attribute, which matches the value of 0 specified using the commentReference element above. The block-level content of the comment specifies that its text is comment and the style of the comment content is based off of the character style with the name CommentReference. end example]

annotationRef (Comment Information Block)

This element specifies the presence of an annotation reference mark at the current location in the comment. An annotation reference mark is an information block that represents the metadata about the current comment within the document. This annotation reference mark should typically consist of the initials and a unique integer associated with its position in the document, but may be displayed in any desired format.

If this element is omitted from a single comment's contents, then an annotation reference mark may be added at the start of the comment in reading order (right in a right-to-left paragraph or left in a left-to-right paragraph). As well, an annotation reference mark may be relocated as desired within a comment's content.

[Example: Consider a document with text with an annotated comment as follows:

This comment is represented as the following WordprocessingML fragment:

<w:comment … w:initials="User">

<w:p>

<w:r>

<w:annotationRef />

</w:r>

…

</w:p>

</w:comment>

The annotationRef element specifies that the comment shall start with an annotation reference mark. In this example, this mark is displayed as a combination of the user initial, User, and a unique sequential number, 1. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

The following XML Schema fragment defines the contents of this element:

comment (Comment Content)

This element specifies the content of a single comment stored in the Comments part of a WordprocessingML document.

If a comment is not referenced by document content via a matching id attribute on a valid use of the commentReference element (§2.13.4.5), then it may be ignored when loading the document. If more than one comment shares the same value for the id attribute, then only one comment shall be loaded and the others may be ignored.

[Example: Consider a document with text with an annotated comment as follows:

This comment is represented as the following WordprocessingML fragment:

<w:comment w:id="1" w:initials="User">

…

</w:comment>

The comment element specifies the presence of a single comment within the comments part. end example]

Parent Elements

comments (§2.13.4.6)

Child Elements

Subclause

altChunk (Anchor for Imported External Content)

§2.17.3.1

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Block-Level Custom XML Element)

§2.5.1.6

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

del (Deleted Run Content)

§2.13.5.12

ins (Inserted Run Content)

§2.13.5.20

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

p (Paragraph)

§2.3.1.22

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

proofErr (Proofing Error Anchor)

§2.13.8.1

sdt (Block-Level Structured Document Tag)

§2.5.2.30

tbl (Table)

§2.4.36

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

initials (Initials of Comment Author)

Specifies the initials of the author of the current comment. This information may be used to format and present the associated comment information block (§2.13.4.1), or in any user interface supported by an application.

If this attribute is omitted, then no author shall be associated with the current comment in the document.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:comment w:id="1" w:initials="KB">

…

</w:comment>

The intials attribute specifies that the initials of the author of the current comment are KB, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

commentRangeEnd (Comment Anchor Range End)

This element specifies the end of the range around which a comment is anchored in the content of the WordprocessingML document. The id attribute on this element shall be used to link the corresponding comment anchor range start element and comment reference.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding commentRangeStart element (§2.13.4.4) with a matching id attribute value, then it shall be considered the single anchor point for the associated comment reference.

If this element appears without a corresponding commentReference element (§2.13.4.5) in the current document story with a matching id attribute value, then it shall be ignored and the comment has no associated range.

If this element appears in a comment content story (§2.13.4.2), then it may be ignored.

[Example: Consider a paragraph in a WordprocessingML document whose second word is annotated with a comment:

The WordprocessingML fragment for this comment is defined as follows:

The commentRangeEnd element specifies that the end of the comment range for the comment with an id of 0 is after the end of the run containing the word text. end example]

Parent Elements

body (§2.2.2); comment (§2.13.4.2); customXml (§2.5.1.3); customXml (§2.5.1.4); customXml (§2.5.1.5); customXml (§2.5.1.6); deg (§7.1.2.26); del (§2.13.5.12); den (§7.1.2.28); docPartBody (§2.12.6); e (§7.1.2.32); endnote (§2.11.2); fldSimple (§2.16.21); fName (§7.1.2.37); footnote (§2.11.10); ftr (§2.10.3); hdr (§2.10.4); hyperlink (§2.16.24); ins (§2.13.5.20); lim (§7.1.2.52); moveFrom (§2.13.5.21); moveTo (§2.13.5.26); num (§7.1.2.75); oMath (§7.1.2.77); p (§2.3.1.22); rt (§2.3.3.23); rubyBase (§2.3.3.26); sdtContent (§2.5.2.32); sdtContent (§2.5.2.33); sdtContent (§2.5.2.34); sdtContent (§2.5.2.35); smartTag (§2.5.1.9); sub (§7.1.2.112); sup (§7.1.2.114); tbl (§2.4.36); tc (§2.4.62); tr (§2.4.75); txbxContent (§2.17.1.1)

Attributes

Description

displacedByCustomXml (Annotation Marker Relocated For Custom XML Markup)

Specifies that the parent annotation's placement shall be directly linked with the location of the physical presentation of a custom XML element in the document. This element only has an effect when the custom XML element is block-level (i.e. surrounds an entire paragraph), as in this scenario the logical and physical placement of the annotation and custom XML element may differ.

Specifically, in this case, the custom XML is presented *around* the block-level object it encloses (the paragraph, table, table row, or table cell), but is physically represented within that same object (i.e. within the paragraph, table, table row or table cell). This requirement stems from the fact that there is no location for the location of the annotation within the document at its logical location (around a table, for example).

If this element is omitted, then the annotation shall be anchored inside of all block-level custom XML elements in the paragraph. If this element is present, but no block-level custom XML tag is located at the position it specifies (before or after), then it shall be ignored.

[Example: Consider a paragraph with block level custom XML markup and two comment anchor annotations (one before and one after the custom XML element's physical representation), as follows:

Since all three of these items are around the entire paragraph, they are stored outside of the paragraph. However, in order to ensure that their relative positions are stored correctly, any annotation which shall be displaced by the physical custom XML element specifies this information, resulting in the following WordprocessingML:

<w:commentRangeStart w:id="0" /><w:commentRangeStart w:id="1" w:displaced byCustomXml="next" /><w:customXml w:element="spec" … /><w:p> …</w:p>

The displacedByCustomXml attribute specifies that even though all three of these items are around the paragraph and will be moved inside the paragraph to be represented physically, the comment with ID 0 shall be inside the custom XML, but the comment with ID 1 shall be displaced to stay outside of the relative location of the next custom XML element (the spec element). end example]

The possible values for this attribute are defined by the ST_DisplacedByCustomXml simple type (§2.18.17).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

commentRangeStart (Comment Anchor Range Start)

This element specifies the start of the range around which a comment is anchored in the content of the WordprocessingML document. The id attribute on this element shall be used to link the corresponding comment anchor range end element and comment reference.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding commentRangeEnd element (§2.13.4.3) with a matching id attribute value, then it shall be considered the single anchor point for the associated comment reference.

If this element appears in a comment content story (§2.13.4.2), then it may be ignored.

[Example: Consider a paragraph in a WordprocessingML document whose second word is annotated with a comment:

The WordprocessingML fragment for this comment is defined as follows:

The commentRangeStart element specifies that the start of the comment range for the comment with an id of 0 is after the end of the run containing the word Some. end example]

Parent Elements

Attributes

Description

displacedByCustomXml (Annotation Marker Relocated For Custom XML Markup)

[Example: Consider a paragraph with block level custom XML markup and two comment anchor annotations (one before and one after the custom XML element's physical representation), as follows:

<w:commentRangeStart w:id="0" /><w:commentRangeStart w:id="1" w:displaced byCustomXml="next" /><w:customXml w:element="spec" … /><w:p> …</w:p>

The possible values for this attribute are defined by the ST_DisplacedByCustomXml simple type (§2.18.17).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

commentReference (Comment Content Reference Mark)

This element specifies the presence of a comment content reference mark, which links the comment content (§2.13.4.2) with the contents of a document story. This link is established by matching the comment whose id attribute matches the id attribute on this element. The resulting comment is anchored to the range with comment range elements with the same id attribute values (if present) as follows:

If either or both of the commentRangeStart and commentRangeEnd elements (§2.13.4.4; §2.13.4.3) are present, then the comment reference shall anchor the comment to the resulting range.

If neither element is present, then the comment reference shall anchor the comment to its current location.

If this element appears in a comment content story (§2.13.4.2), then it may be ignored. If no comment exists with an id attribute which matches the id attribute on this element, then this document is non-conformant.

[Example: Consider a paragraph in a WordprocessingML document whose second word is annotated with a comment:

The WordprocessingML fragment for this comment is defined as follows:

The commentReference element specifies that the associated comment in the comments part shall be the comment whose id attribute value is 0. As well, since a start and end marker exist with a matching ID, this comment is anchored to that region of the document. end example]

Parent Elements

r (§7.1.2.87); r (§2.3.2.23)

Attributes

Description

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

comments (Comments Collection)

This element specifies all of the comments defined in the current document. It is the root element of the Comments part of a WordprocessingML document.

[Example: Consider the following WordprocessingML fragment for the content of a comments part in a WordprocessingML document:

<w:comments> <w:comment … > … </w:comment></w:comments>

The comments element contains the single comment specified by this document in this example. end example]

Parent Elements

Root element of WordprocessingML Comments part

Child Elements

Subclause

comment (Comment Content)

§2.13.4.2

The following XML Schema fragment defines the contents of this element:

</sequence>

</complexType>

Revisions

Revisions in WordprocessingML provide a mechanism for storing information about the evolution of the document (i.e. the set of modifications made to a document by one of more authors). When an application adds revisions to the content of a WordprocessingML document, they are specifying this by storing either (depending on the revision type):

The current state of the document (a deletion stores the current state of the text as deleted, and implies that its original state was the content used to exist)

The initial state of the document (a run's initial properties are explicitly stored in a previous run properties block, as the current run properties are always those that are the child of the rPr element (§2.7.8.1))

A revision consists of two required pieces of information:

The revision type (specified via the name of the revision element)

A unique revision identifier (used to uniquely identify revisions)

As well as optional information:

The author of the revision

The date and time of the revision

[Example: Consider a paragraph of text in a WordprocessingML document in which one word has been inserted, as follows:

This paragraph has the word text marked inserted as a revision, and is represented as the following WordprocessingML:

<w:p>

<w:r>

<w:t>Some</w:t>

</w:r>

<w:ins w:id="0" w:author="Joe Smith" w:date="2006-03-31T12:50:00Z">

<w:r>

<w:t>text</w:t>

</w:r>

</w:ins>

</w:p>

The ins element contains both the required information: all of the content which shall be treated as revision marked as inserted (the word text); a unique revision identifier of 0.

The element also stores the optional information about the revision: the word text was inserted by Joe Smith on March 31, 2006 at 12:50pm. end example]

Within a WordprocessingML document, the following types of revisions may be used to track the changes to a document:

Insertions

Deletions

Moves

Changes to run/paragraph/table/numbering/section properties

Changes to custom XML markup

cellDel (Table Cell Deletion)

This element specifies that the parent table cell shall be treated as though it was deleted from the document while revisions were being recorded. This means that although the table cell element exists in the structure of the table, the table cell technically no longer exists in the document.

[Example: Consider a document with a two row by two columns table as follows:

If this table has each cell in its final column deleted and this is tracked as a revision, the resulting WordprocessingML would show each of these cells as deleted as follows:

<w:tbl> … <w:tr> <w:tc> <w:r> <w:t>One</w:t> </w:r> </w:tc> <w:tc> <w:tcPr> <w:cellDel w:id="0" … /> </w:tcPr> <w:r> <w:t>Two</w:t> </w:r> </w:tc> </w:tr> <w:tr> <w:tc> <w:r> <w:t>Three</w:t> </w:r> </w:tc> <w:tc> <w:tcPr> <w:cellDel w:id="1" … /> </w:tcPr> <w:r> <w:t>Four</w:t> </w:r> </w:tc> </w:tr></w:tbl>

The cellDel elements in the table cell properties of the cells with text Two and Four specify that each of those cells have been deleted from the document. Their attributes (omitted) may optionally provide information about the time at which this deletion took place. end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

cellIns (Table Cell Insertion)

This element specifies that the parent table cell shall be treated as though it was inserted into the document while revisions were being recorded.

[Example: Consider a document with a two row by two columns table as follows:

If this table has two cells added by appending an additional column, and this is tracked as a revision, the resulting WordprocessingML would show each of these cells as inserted as follows:

<w:tbl> … <w:tr> <w:tc> <w:r> <w:t>One</w:t> </w:r> </w:tc> <w:tc> <w:r> <w:t>Two</w:t> </w:r> </w:tc> <w:tc> <w:tcPr> <w:cellIns w:id="0" … /> </w:tcPr> <w:r> <w:t>New</w:t> </w:r> </w:tc> </w:tr> <w:tr> <w:tc> <w:r> <w:t>Three</w:t> </w:r> </w:tc> <w:tc> <w:r> <w:t>Four</w:t> </w:r> </w:tc> <w:tc> <w:tcPr> <w:cellIns w:id="1" … /> </w:tcPr> <w:r> <w:t>New</w:t> </w:r> </w:tc> </w:tr></w:tbl>

The cellIns elements in the table cell properties of the cells with text New specify that each of those cells have been inserted into the document. Their attributes (omitted) may optionally provide information about the insertion of these cells (author, date, etc.). end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

cellMerge (Vertically Merged/Split Table Cells)

This element specifies that the vertical merge state of the parent table cell has been modified while revisions were being tracked for the document. The vmerge and vmergeOrig attributes on this element specify the original and revised vertical merge states of the table cell.

[Example: Consider a document with a two row by two columns table as follows:

If this table has the two cells in the second column merged into one and this modification is tracked as a revision, as follows:

The resulting WordprocessingML for the revision would appear as follows:

<w:tbl> … <w:tr> <w:tc> <w:r> <w:t>One</w:t> </w:r> </w:tc> <w:tc> <w:r> <w:t>Two</w:t> </w:r> </w:tc> </w:tr> <w:tr> <w:tc> <w:r> <w:t>Three</w:t> </w:r> </w:tc> <w:tc> <w:tcPr> <w:cellMerge w:id="0" w:vmerge="cont"/> </w:tcPr> <w:r> <w:t>Four</w:t> </w:r> </w:tc> </w:tr></w:tbl>

The cellMerge element specifies that changes were made to the vertical merge settings of the last cell in the table, specifically; the cell was vertically merged with the cell above it (gaining a revised vmerge attribute value of cont). end example]

Parent Elements

tcPr (§2.7.5.8); tcPr (§2.4.66); tcPr (§2.7.5.9); tcPr (§2.4.67)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

vMerge (Revised Vertical Merge Setting)

Specifies the vertical merge setting which was applied to the parent table cell by this revision.

If this attribute is omitted, then no revised vertical merge setting is supplied for this revision (if neither this nor the vmergeOrig attribute is specified, the revision may be ignored).

[Example: Consider a two row by two column table in which the cells in the second column are merged, and this change is tracked as a revision. The annotation on the last cell in the table would appear as follows:

<w:tc> <w:tcPr> <w:cellMerge … w:vmerge="cont" /> </w:tcPr> …</w:tc>

The vmerge attribute value of cont specifies that the revision on the table cell resulted in it being merged with the previous set of vertically merged cells above it (whether that was one cell or many). end example]

The possible values for this attribute are defined by the ST_AnnotationVMerge simple type (§2.18.3).

vMergeOrig (Vertical Merge Setting Removed by Revision)

Specifies the vertical merge setting which was removed from the parent table cell by this revision.

If this attribute is omitted, then the original vertical merge setting shall be assumed to be rest (not merged).

[Example: Consider a two row by two column table in which the merged cells in the second column are split, and this change is tracked as a revision. The annotation on the last cell in the table would appear as follows:

<w:tc> <w:tcPr> <w:cellMerge … w:vmergeOrig="cont" /> </w:tcPr> …</w:tc>

The vmergeOrig attribute value of cont specifies that the revision on the table cell resulted in it having its vertical merge property removed. end example]

The possible values for this attribute are defined by the ST_AnnotationVMerge simple type (§2.18.3).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

customXmlDelRangeEnd (Custom XML Markup Deletion End)

This element specifies the end of a region in which custom XML markup has been deleted and tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML markup deletion start marker in the document.

Providing a physical representation of custom XML markup results in regions which can be inserted and deleted, but cannot be encapsulated by a single revision element, since their representation in WordprocessingML is the start or end XML tag for the custom XML markup which it represents. Therefore, the start/end "cross structure" annotation format surrounds the WordprocessingML region to which this deletion applies.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlDelRangeStart element (§2.13.5.5) with a matching id attribute value, then it shall be ignored and no deletions shall be present in the document.

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If multiple end elements exist with the same id attribute value, then the first instance in the document shall be used and subsequent elements should be treated as unmatched (no corresponding start).

[Example: Consider a document with two inline custom XML markup elements, as follows:

<w:p> <w:customXml … > <w:customXml … > <w:r> <w:t>Text.</w:t> </w:r> </w:customXml> </w:customXml> <w:r> <w:t>More text.</w:t> </w:r></w:p>

Now, if each custom XML markup element's start and end tag have a physical representation, imagine that the region from the start of the paragraph until the point between the two end points is deleted with revisions enabled. This revision cannot be encapsulated by one del element, since it starts outside of the first custom XML markup element and ends just inside of it, so it must be done using the custom XML markup revision "cross structure" syntax, as follows:

<w:p>

<w:customXmlDelRangeStart w:id="0" /> <w:customXml … > <w:customXml … > <w:del … > <w:r> <w:delText>Text.</w:delText> </w:r> </w:del> </w:customXml> <w:customXmlDelRangeEnd w:id="0" /> </w:customXml> <w:r> <w:t>More text.</w:t> </w:r></w:p>

The customXmlDelRangeEnd element delimits the end of the region in which all custom XML elements have been deleted with revisions enabled, and the del element (§2.13.5.12) handles the deletion of the text performed by this revision. Since the end of the outer customXml element was not in the deleted range, it is not revision marked deleted, but the corresponding physical character for the start element is. end example]

Parent Elements

Attributes

Description

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

customXmlDelRangeStart (Custom XML Markup Deletion Start)

This element specifies the beginning of a region in which all custom XML markup has been deleted and tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML markup deletion end marker in the document.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlDelRangeEnd element (§2.13.5.4) with a matching id attribute value, then this revision is ill-formed, and the revision may be ignored or all custom XML from this point forward may be treated as deleted.

If this element and its paired end encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If multiple start elements exist with the same id attribute value, then the each instance in the document shall be matched with an end in document order, and unmatched starts (no corresponding end) shall be handled as described above.

[Example: Consider a document with two inline custom XML markup elements, as follows:

<w:p> <w:customXml … > <w:customXml … > <w:r> <w:t>Text.</w:t> </w:r> </w:customXml> </w:customXml> <w:r> <w:t>More text.</w:t> </w:r></w:p>

<w:p>

The customXmlDelRangeStart element delimits the start of the region in which all custom XML elements have been deleted with revisions enabled, and the del element (§2.13.5.12) handles the deletion of the text performed by this revision. Since the end of the outer customXml element was not in the deleted range, it is not revision marked deleted, but the corresponding physical character for the start element is. end example]

Parent Elements

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

customXmlInsRangeEnd (Custom XML Markup Insertion End)

This element specifies the end of a region within which all custom XML markup has been inserted and tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML markup insertion start marker in the document.

Providing a physical representation of the start and end tags of custom XML markup results in regions which can be inserted and deleted independently, but cannot be encapsulated by a single revision element, since their representation in WordprocessingML is the start or end XML tag for the custom XML markup which it represents. Therefore, the start/end "cross structure" annotation format surrounds the WordprocessingML region to which this insertion applies.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlInsRangeStart element (§2.13.5.7) with a matching id attribute value, then it shall be ignored and no insertions shall be present in the document.

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If multiple end elements exist with the same id attribute value, then the first instance in the document shall be used and subsequent elements should be treated as unmatched (no corresponding start).

[Example: Consider a document with two inline custom XML markup elements, as follows:

<w:p> <w:customXml … > <w:customXml … > <w:r> <w:t>Text.</w:t> </w:r> </w:customXml> </w:customXml> <w:r> <w:t>More text.</w:t> </w:r></w:p>

If each custom XML markup element's start and end tag have a physical representation, consider that the inner XML element (but not its content) is inserted with revisions enabled. This revision cannot be encapsulated by one ins element, since the text in the element is not an insertion, so it must be done using the custom XML markup revision "cross structure" syntax, as follows:

<w:p> <w:customXml … > <w:customXmlInsRangeStart w:id="0" /> <w:customXml … > <w:r> <w:t>Text.</w:t> </w:r> </w:customXml> <w:customXmlInsRangeEnd w:id="0" /> </w:customXml> <w:r> <w:t>More text.</w:t> </w:r></w:p>

The customXmlInsRangeEnd element delimits the end of the region in which all custom XML elements have been inserted with revisions enabled. Since this element only affects custom XML, the text is not revision marked inserted, but the corresponding physical characters for the custom XML element are. end example]

Parent Elements

Attributes

Description

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

customXmlInsRangeStart (Custom XML Markup Insertion Start)

This element specifies the beginning of a region in which all custom XML markup has been inserted and tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML markup insertion end marker in the document.

Providing a physical representation of custom XML markup start and end tags results in regions which can be inserted and deleted independently, but cannot be encapsulated by a single revision element, since their representation in WordprocessingML is the start or end XML tag for the custom XML markup which it represents. Therefore, the start/end "cross structure" annotation format surrounds the WordprocessingML region to which this deletion applies.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlInsRangeEnd element (§2.13.5.6) with a matching id attribute value, then this revision is ill-formed, and the revision may be ignored or all custom XML from this point forward may be treated as inserted.

If this element and its paired end encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

The following restrictions shall be applied to this element:

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If multiple end elements exist with the same id attribute value, then the first instance in the document shall be used and subsequent elements should be treated as unmatched (no corresponding start).

[Example: Consider a document with two inline custom XML markup elements, as follows:

<w:p> <w:customXml … > <w:customXml … > <w:r> <w:t>Text.</w:t> </w:r> </w:customXml> </w:customXml> <w:r> <w:t>More text.</w:t> </w:r></w:p>

The customXmlInsRangeStart element delimits the start of the region in which all custom XML elements have been inserted with revisions enabled. Since this element only affects custom XML, the text is not revision marked inserted, but the corresponding physical characters for the custom XML element are. end example]

Parent Elements

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

This element specifies the end of a region within which all custom XML markup was moved to another location in the document and this move was tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML move source start marker in the document.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlMoveFromRangeStart element (§2.13.5.9) with a matching id attribute value, then it shall be ignored and no move source information shall be applied to the custom XML elements by this element.

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If this element and its paired start occur outside of a valid move source container (§2.13.5.24; §2.13.5.23) with a matching move destination container (§2.13.5.28; §2.13.5.27), then custom XML markup in this region shall be treated as if it was deleted

If multiple end elements exist with the same id attribute value, then the first instance in the document shall be used and subsequent elements should be treated as unmatched (no corresponding start).

[Example: Consider a three-paragraph document with a single block-level custom XML markup element, as follows:

<w:body> <w:p/> <w:customXml … > <w:p/> </w:customXml> <w:p/></w:body>

If the second paragraph is moved to the end of the document with revisions enabled. This revision must therefore be stored using the custom XML markup revision "cross structure" syntax, as follows:

<w:body> <w:p/> <w:moveFromRangeStart w:id="0" w:name="move1" w:displacedByCustomXml="next"/> <w:customXmlMoveFromRangeStart w:id="1"/> <w:customXml … > <w:p/> </w:customXml> <w:customXmlMoveFromRangeEnd w:id="1"/> <w:moveFromRangeEnd w:id="0" w:displacedByCustomXml="prev"/> <w:p/> <w:moveToRangeStart w:id="2" w:name="move1" w:displacedByCustomXml="next"/> <w:customXmlMoveToRangeStart w:id="3"/> <w:customXml … > <w:p/> </w:customXml> <w:customXmlMoveToRangeEnd w:id="3"/> <w:moveFromRangeEnd w:id="2" w:displacedByCustomXml="prev"/></w:body>

The customXmlMoveFromRangeEnd element delimits the end of the region in which all custom XML elements have been moved from this location with revisions enabled. Since this element only affects custom XML, any text in the region is not revision marked moved by this element when present, but the corresponding physical characters for the custom XML element are. end example]

Parent Elements

Attributes

Description

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

This element specifies the start of a region within which all custom XML markup was moved to another location in the document and this move was tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML move source end marker in the document.

The following restrictions shall be applied to this element:

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If this element and its paired end occur outside of a valid move source container (§2.13.5.24; §2.13.5.23) with a matching move destination container (§2.13.5.28; §2.13.5.27), then custom XML markup in this region shall be treated as if it was deleted

[Example: Consider a three-paragraph document with a single block-level custom XML markup element, as follows:

<w:body> <w:p/>

<w:customXml … > <w:p/> </w:customXml> <w:p/></w:body>

If the second paragraph is moved to the end of the document with revisions enabled. This revision must therefore be stored using the custom XML markup revision "cross structure" syntax, as follows:

<w:body> <w:p/> <w:moveFromRangeStart w:id="0" w:name="move1" w:displacedByCustomXml="next"/>

<w:customXmlMoveFromRangeStart w:id="1"/> <w:customXml … > <w:p/> </w:customXml> <w:customXmlMoveFromRangeEnd w:id="1"/> <w:moveFromRangeEnd w:id="0" w:displacedByCustomXml="prev"/> <w:p/>

<w:moveToRangeStart w:id="2" w:name="move1" w:displacedByCustomXml="next"/>

<w:customXmlMoveToRangeStart w:id="3"/> <w:customXml … > <w:p/> </w:customXml> <w:customXmlMoveToRangeEnd w:id="3"/> <w:moveFromRangeEnd w:id="2" w:displacedByCustomXml="prev"/></w:body>

The customXmlMoveFromRangeStart element delimits the start of the region in which all custom XML elements have been moved from this location with revisions enabled. Since this element only affects custom XML, any text in the region is not revision marked moved by this element when present, but the corresponding physical characters for the custom XML element are. end example]

Parent Elements

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

This element specifies the end of a region within which all custom XML markup was moved to this location in the document and this move was tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML move destination start marker in the document.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlMoveToRangeStart element (§2.13.5.11) with a matching id attribute value, then it shall be ignored and no move destination information shall be applied to the custom XML elements by this element.

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

If multiple end elements exist with the same id attribute value, then the first instance in the document shall be used and subsequent elements should be treated as unmatched (no corresponding start).

[Example: Consider a three-paragraph document with a single block-level custom XML markup element, as follows:

<w:body> <w:p/> <w:customXml … > <w:p/> </w:customXml> <w:p/></w:body>

If the second paragraph is moved to the end of the document with revisions enabled. This revision must therefore be stored using the custom XML markup revision "cross structure" syntax, as follows:

The customXmlMoveToRangeEnd element delimits the end of the region in which all custom XML elements have been moved to this location with revisions enabled. Since this element only affects custom XML, any text in the region is not revision marked moved by this element when present, but the corresponding physical characters for the custom XML element are. end example]

Parent Elements

Attributes

Description

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</complexType>

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

This element specifies the start of a region within which all custom XML markup was moved to this location in the document and this move was tracked as a revision. The id attribute on this element shall be used to link this element with the corresponding custom XML move destination end marker in the document.

The following restrictions shall be applied to this element:

If this element occurs without a corresponding customXmlMoveFromRangeEnd element (§2.13.5.8) with a matching id attribute value, then it shall be ignored and no move source information shall be applied to the custom XML elements by this element.

If this element and its paired start encapsulate a range with no custom XML markup, then they shall be ignored and may be omitted when the document is subsequently saved.

[Example: Consider a three-paragraph document with a single block-level custom XML markup element, as follows:

<w:body> <w:p/>

<w:customXml … > <w:p/> </w:customXml> <w:p/></w:body>

If the second paragraph is moved to the end of the document with revisions enabled. This revision must therefore be stored using the custom XML markup revision "cross structure" syntax, as follows:

<w:body> <w:p/> <w:moveFromRangeStart w:id="0" w:name="move1" w:displacedByCustomXml="next"/>

<w:customXmlMoveFromRangeStart w:id="1"/> <w:customXml … > <w:p/> </w:customXml> <w:customXmlMoveFromRangeEnd w:id="1"/> <w:moveFromRangeEnd w:id="0" w:displacedByCustomXml="prev"/> <w:p/>

<w:moveToRangeStart w:id="2" w:name="move1" w:displacedByCustomXml="next"/>

<w:customXmlMoveToRangeStart w:id="3"/> <w:customXml … > <w:p/> </w:customXml> <w:customXmlMoveToRangeEnd w:id="3"/> <w:moveFromRangeEnd w:id="2" w:displacedByCustomXml="prev"/></w:body>

Parent Elements

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

del (Deleted Run Content)

This element specifies that the inline-level content contained within it shall be treated as deleted content which has been tracked as a revision.

[Example: Consider a paragraph of text in a WordprocessingML document in which one word has been deleted, as follows:

This paragraph has the word text marked deleted as a revision, and is represented as the following WordprocessingML:

<w:p>

<w:r>

<w:t>Some</w:t>

</w:r>

<w:del w:id="0" w:author="Joe Smith" w:date="2006-03-31T12:50:00Z">

<w:r>

<w:delText>text</w:delText>

</w:r>

</w:del>

</w:p>

The del element contains all of the content which shall be treated as revision marked as deleted; in this case, the word text was deleted by Joe Smith on March 31, 2006 at 12:50pm. end example]

Parent Elements

Child Elements

Subclause

acc (Accent)

§7.1.2.1

bar (Bar)

§7.1.2.7

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

borderBox (Border-Box Function)

§7.1.2.11

box (Box Function)

§7.1.2.13

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

d (Delimiter Function)

§7.1.2.24

del (Deleted Run Content)

§2.13.5.12

eqArr (Equation-Array Function)

§7.1.2.34

f (Fraction Function)

§7.1.2.36

func (Function Apply Function)

§7.1.2.39

groupChr (Group-Character Function)

§7.1.2.41

ins (Inserted Run Content)

§2.13.5.20

limLow (Lower-Limit Function)

§7.1.2.54

limUpp (Upper-Limit Function)

§7.1.2.56

m (Matrix Function)

§7.1.2.60

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

nary (n-ary Operator Function)

§7.1.2.70

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

phant (Phantom Function)

§7.1.2.81

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

r (Run)

§7.1.2.87

rad (Radical Function)

§7.1.2.88

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

sPre (Pre-Sub-Superscript Function)

§7.1.2.99

sSub (Subscript Function)

§7.1.2.101

sSubSup (Sub-Superscript Function)

§7.1.2.103

sSup (Superscript Function)

§7.1.2.105

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</choice>

</extension>

</complexContent>

</complexType>

del (Deleted Paragraph)

This element specifies that the paragraph mark delimiting the end of a paragraph within a WordprocessingML document shall be treated as deleted (i.e. the contents of this paragraph are no longer delimited by this paragraph mark, and are combined with the following paragraph - but those contents shall not automatically be marked as deleted) as part of a tracked revision.

[Example: Consider a document consisting of two paragraphs (with each paragraph delimited by a pilcrow ¶), as follows:

If the physical character delimiting the end of the first paragraph is deleted and this change is tracked as a revision, resulting in the following:

This revision is represented using the following WordprocessingML:

<w:p> <w:pPr> <w:rPr> <w:del w:id="0" … /> </w:rPr> </w:pPr> <w:r> <w:t>This is paragraph one.</w:t> </w:r></w:p><w:p> <w:r> <w:t>This is paragraph two.</w:t> </w:r></w:p>

The del element on the run properties for the first paragraph mark specifies that this paragraph mark was deleted, and this deletion was tracked as a revision. end example]

Parent Elements

rPr (§2.3.1.29); rPr (§2.3.1.30)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

del (Deleted Table Row)

This element specifies that the parent table row shall be treated as a deleted row whose deletion has been tracked as a revision. This setting shall not imply any revision state about the table cells in this row or their contents (which must be revision marked independently), and shall only affect the table row itself.

[Example: Consider a two row by two column table in which the second row has been marked as deleted using a revision. This requirement would be specified using the following WordprocessingML:

<w:tbl> <w:tr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr> <w:tr> <w:trPr> <w:del w:id="0" … /> </w:trPr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr>

</w:tbl>

The del element on the table row properties for the second table row specifies that this row was deleted, and this deletion was tracked as a revision. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

del (Deleted Math Control Character)

This element specifies that the Office Open XML Math control character which contains this element was deleted and tracked as a revision. [Example: The deletion of a fraction bar. end example]

[Example: Consider a region of Office Open XML Math in a WordprocessingML document in which the control character for the fraction bar has been deleted, as follows:

This deletion is represented as the following WordprocessingML:

<m:f> <m:fPr> <m:ctrlPr> <w:del w:id="0" w:author="Joe Smith" w:date="2006-03-31T12:50:00Z"> ... </w:del> </m:ctrlPr> </m:fPr> ...</m:f>

The del element contains all of the content which shall be treated as revision marked as deleted; in this case, the fraction bar was deleted by Joe Smith on March 31, 2006 at 12:50pm. end example]

Parent Elements

ctrlPr (§7.1.2.23)

Child Elements

Subclause

rPr (Previous Run Properties)

§2.3.2.26

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

ins (Inserted Table Row)

This element specifies that the parent table row shall be treated as an inserted row whose insertion has been tracked as a revision. This setting shall not imply any revision state about the table cells in this row or their contents (which must be revision marked independently), and shall only affect the table row itself.

[Example: Consider a two row by two column table in which the second row has been marked as inserted using a revision. This requirement would be specified using the following WordprocessingML:

<w:tbl> <w:tr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr> <w:tr> <w:trPr> <w:ins w:id="0" … /> </w:trPr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr>

</w:tbl>

The ins element on the table row properties for the second table row specifies that this row was inserted, and this insertion was tracked as a revision. end example]

Parent Elements

trPr (§2.7.5.10); trPr (§2.7.5.11); trPr (§2.4.78)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

ins (Inserted Math Control Character)

This element specifies that the Office Open XML Math control character which contains this element was inserted and tracked as a revision. [Example: The insertion of a fraction bar. end example]

[Example: Consider a region of Office Open XML Math in a WordprocessingML document in which the control character for the fraction bar has been inserted, as follows:

This insertion is represented as the following WordprocessingML:

<m:f> <m:fPr> <m:ctrlPr> <w:ins w:id="0" w:author="Joe Smith" w:date="2006-03-31T12:50:00Z"> ... </w:ins> </m:ctrlPr> </m:fPr> ...</m:f>

The ins element contains all of the content which shall be treated as revision marked as inserted; in this case, the fraction bar was inserted by Joe Smith on March 31, 2006 at 12:50pm. end example]

Parent Elements

ctrlPr (§7.1.2.23)

Child Elements

Subclause

rPr (Previous Run Properties)

§2.3.2.26

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</sequence>

</extension>

</complexContent>

</complexType>

ins (Inserted Paragraph)

[Example: Consider a document consisting of a single paragraph, as follows:

If the first sentence is moved into its own new paragraph, and this change is tracked as a revision, resulting in the following:

This revision is represented using the following WordprocessingML:

<w:p> <w:pPr> <w:rPr> <w:ins w:id="0" … /> </w:rPr> </w:pPr> <w:r> <w:t>This is paragraph one.</w:t> </w:r></w:p><w:p> <w:r> <w:t>This is paragraph two.</w:t> </w:r></w:p>

The ins element on the run properties for the first paragraph mark specifies that this paragraph mark was inserted, and this insertion was tracked as a revision. end example]

Parent Elements

rPr (§2.3.1.29); rPr (§2.3.1.30)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

ins (Inserted Numbering Properties)

This element specifies that the numbering information defined by the parent element shall be treated as numbering information which was recorded as an insertion using revisions.

[Example: Consider two paragraphs in a WordprocessingML document, with the words one and two respectively, as follows:

If numbering is then applied to these two paragraphs, and this numbering is tracked as a revision, this revision is represented using the following WordprocessingML:

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="1" /> <w:ins w:id="0" w:author="Joe Smith" w:date="20050101T10:00:00Z" /> </w:numPr> </w:pPr> <w:r> <w:t>one</w:t> </w:r></w:p>

<w:p> <w:pPr> <w:numPr> <w:ilvl w:val="0" /> <w:numId w:val="1" /> <w:ins w:id="0" w:author="Joe Smith" w:date="20050101T10:00:00Z" /> </w:numPr> </w:pPr> <w:r> <w:t>two</w:t> </w:r></w:p>

The ins element as a child of the numbering properties specifies that the paragraphs in this document have been given numbering properties by Joe Smith and that this change was marked as a revision. end example]

Parent Elements

numPr (§2.3.1.19)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

ins (Inserted Run Content)

This element specifies that the inline-level content contained within it shall be treated as inserted content which has been tracked as a revision.

[Example: Consider a paragraph of text in a WordprocessingML document in which one word has been inserted, as follows:

This paragraph has the word text marked inserted as a revision, and is represented as the following WordprocessingML:

<w:p>

<w:r>

<w:t>Some</w:t>

</w:r>

<w:ins w:id="0" w:author="Joe Smith" w:date="2006-03-31T12:50:00Z">

<w:r>

<w:t>text</w:t>

</w:r>

</w:ins>

</w:p>

The ins element contains all of the content which shall be treated as revision marked as inserted; in this case, the word text was inserted by Joe Smith on March 31, 2006 at 12:50pm. end example]

Parent Elements

Child Elements

Subclause

acc (Accent)

§7.1.2.1

bar (Bar)

§7.1.2.7

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

borderBox (Border-Box Function)

§7.1.2.11

box (Box Function)

§7.1.2.13

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

d (Delimiter Function)

§7.1.2.24

del (Deleted Run Content)

§2.13.5.12

eqArr (Equation-Array Function)

§7.1.2.34

f (Fraction Function)

§7.1.2.36

func (Function Apply Function)

§7.1.2.39

groupChr (Group-Character Function)

§7.1.2.41

ins (Inserted Run Content)

§2.13.5.20

limLow (Lower-Limit Function)

§7.1.2.54

limUpp (Upper-Limit Function)

§7.1.2.56

m (Matrix Function)

§7.1.2.60

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

nary (n-ary Operator Function)

§7.1.2.70

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

phant (Phantom Function)

§7.1.2.81

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

r (Run)

§7.1.2.87

rad (Radical Function)

§7.1.2.88

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

sPre (Pre-Sub-Superscript Function)

§7.1.2.99

sSub (Subscript Function)

§7.1.2.101

sSubSup (Sub-Superscript Function)

§7.1.2.103

sSup (Superscript Function)

§7.1.2.105

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</choice>

</extension>

</complexContent>

</complexType>

moveFrom (Move Source Run Content)

This element specifies that the inline-level content contained within it shall be treated as content which has been moved away from this location and tracked as a revision.

The following restrictions shall be applied to this content:

If this element occurs outside of a valid move source container (§2.13.5.24; §2.13.5.23) for which a matching move destination container (§2.13.5.28; §2.13.5.27) exists in the document, then content in this region shall be treated as deleted, rather than moved.

[Example: Consider a WordprocessingML document in which the first paragraph contains two sentences, and the first sentence is moved before the second sentence, and this move is tracked as a revision, as follows (in this image, green underline indicates the move destination and the green strikethrough indicates the move source location):

This document has the sentence Some moved text. moved to the first sentence in the document. This revision is represented using the following WordprocessingML:

<w:p> <w:moveToRangeStart w:id="0" … w:name="move1" /> <w:moveTo w:id="1" … > <w:r> <w:t>Some moved text.</w:t> </w:r> </w:moveTo> <w:moveToRangeEnd w:id="0" /> <w:r> <w:t xml:space="preserve">Some text.</w:t> </w:r> <w:moveFromRangeStart w:id="2" … w:name="move1" /> <w:moveFrom w:id="3" … > <w:r> <w:t>Some moved text.</w:t> </w:r> </w:moveFrom> <w:moveFromRangeEnd w:id="2" /></w:p>

The moveFrom element specifies that all of the inline-level content contained within shall be revision marked as content which was moved from its current location in the document. Because this moved content is contained within a complete move source container (moveFromRangeStart and moveFromRangeEnd) with a corresponding move destination, this content is tracked as a move. end example]

Parent Elements

Child Elements

Subclause

acc (Accent)

§7.1.2.1

bar (Bar)

§7.1.2.7

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

borderBox (Border-Box Function)

§7.1.2.11

box (Box Function)

§7.1.2.13

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

d (Delimiter Function)

§7.1.2.24

del (Deleted Run Content)

§2.13.5.12

eqArr (Equation-Array Function)

§7.1.2.34

f (Fraction Function)

§7.1.2.36

func (Function Apply Function)

§7.1.2.39

groupChr (Group-Character Function)

§7.1.2.41

ins (Inserted Run Content)

§2.13.5.20

limLow (Lower-Limit Function)

§7.1.2.54

limUpp (Upper-Limit Function)

§7.1.2.56

m (Matrix Function)

§7.1.2.60

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

nary (n-ary Operator Function)

§7.1.2.70

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

phant (Phantom Function)

§7.1.2.81

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

r (Run)

§7.1.2.87

rad (Radical Function)

§7.1.2.88

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

sPre (Pre-Sub-Superscript Function)

§7.1.2.99

sSub (Subscript Function)

§7.1.2.101

sSubSup (Sub-Superscript Function)

§7.1.2.103

sSup (Superscript Function)

§7.1.2.105

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</choice>

</extension>

</complexContent>

</complexType>

moveFrom (Move Source Paragraph)

This element specifies that the parent paragraph has been moved away from this location and tracked as a revision. This does not imply anything about the revision state of the contents of the paragraph, and applies only to the existence of the paragraph as its own unique paragraph.

The following restrictions shall be applied to this content:

[Example: Consider a WordprocessingML document in which a paragraph of text is moved down in the document. This moved paragraph would be represented using the following WordprocessingML markup:

<w:moveFromRangeStart w:id="0" w:name="aMove"/><w:p> <w:pPr> <w:rPr> <w:moveFrom w:id="1" … /> </w:rPr> </w:pPr> …</w:p></w:moveFromRangeEnd w:id="0"/>

The moveFrom element as a child of the run properties of the paragraph mark specify that this paragraph mark was part of the content which was moved in the document. This implies nothing about the contents, since they may have been added later and not tracked as a revision (they must be marked as a move using the moveFrom element (§2.13.5.21) around the run content). end example]

Parent Elements

rPr (§2.3.1.29); rPr (§2.3.1.30)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

moveFromRangeEnd (Move Source Location Container - End)

This element specifies the end of a region whose move source contents are part of a single named move. When a move source is stored as a revision in a WordprocessingML document, two pieces of information must be stored about that move source:

A set of pieces of content which were moved - both inline-level content (§2.13.5.21) and paragraphs (§2.13.5.22)

A move source container (or "bookmark") which specifies that all content within it which marked as a move source is part of a single named move. The name attribute on the move container links a group of move source content with the corresponding group of move destination content.

This element defines the end of the latter piece of the move revision data - the container. The id attribute on this element shall be used to link this element with the corresponding start of a move source container in the document.

The following restrictions are applied to the use of this element:

If this element occurs without a corresponding moveFromRangeStart element (§2.13.5.24) with a matching id attribute value, then it shall be ignored and no move source container exists

If this element and its paired end occur without a matching move destination container (§2.13.5.28; §2.13.5.27), then moved content in this region shall be treated as if it was deleted

If multiple move source containers surround the same text, the last valid container (determined by the location of the container start elements, in document order) should be the container associated with that text.

This document has the sentence Some moved text. moved to the first sentence in the document. This revision is represented using the following WordprocessingML:

The moveFromRangeEnd element specifies the end of the move source container within which all moved content is part of the move named move1. end example]

Parent Elements

Attributes

Description

displacedByCustomXml (Annotation Marker Relocated For Custom XML Markup)

[Example: Consider a paragraph with block level custom XML markup and two comment anchor annotations (one before and one after the custom XML element's physical representation), as follows:

<w:commentRangeStart w:id="0" /><w:commentRangeStart w:id="1" w:displaced byCustomXml="next" /><w:customXml w:element="spec" … /><w:p> …</w:p>

The possible values for this attribute are defined by the ST_DisplacedByCustomXml simple type (§2.18.17).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

moveFromRangeStart (Move Source Location Container - Start)

This element specifies the start of a region whose move source contents are part of a single named move. When a move source is stored as a revision in a WordprocessingML document, two pieces of information must be stored about that move source:

A set of pieces of content which were moved - both inline-level content (§2.13.5.21) and paragraphs (§2.13.5.22)

This element defines the start of the latter piece of the move revision data - the container. The id attribute on this element shall be used to link this element with the corresponding end of a move source container in the document.

The following restrictions are applied to the use of this element

If this element occurs without a corresponding moveFromRangeEnd element (§2.13.5.23) with a matching id attribute value, then it shall be ignored and no move source container exists

If this element and its paired end occur without a matching move destination container (§2.13.5.28; §2.13.5.27), then moved content in this region shall be treated as if it was deleted

This document has the sentence Some moved text. moved to the first sentence in the document. This revision is represented using the following WordprocessingML:

The moveFromRangeStart element specifies the start of the move source container within which all moved content is part of the move named move1. end example]

Parent Elements

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

colFirst (First Table Column Covered By Bookmark)

Specifies the zero-based index of the first column in this row which shall be part of this bookmark.

When a bookmark is contained within a table, it is possible for that bookmark to only cover cells within a certain column and row range within that table, by specifying:

The first row for which the specified columns are part of the table bookmark. This is accomplished by placing the bookmarkStart element in the first table cell in that row.

The first column included in the bookmark for each of the specified row(s) via this attribute.

The last column included in the bookmark for each of the specified row(s) via the colLast attribute.

The last row for which the specified columns are part of the table bookmark. This is accomplished by placing the bookmarkEnd element at the end of that table row.

If this attribute appears, then the colLast attribute must also appear (regardless of where this bookmark is located) or the document shall be considered non-conformant. If this attibute and its pair occur on a bookmark which is not contained in a table, then their values should be ignored. If this value exceeds the value of colLast or the number of columns in the table, then both values should be ignored.

[Example: Consider a three row by three column table where a table bookmark shall be applied to the contents of the first two cells in the first two rows in the table (the cells shaded below):

This bookmark would be specified using the following WordprocessingML for the table's conents:

<w:tbl> … <w:tr> <w:tc> <w:bookMarkStart w:colFirst="0" w:colLast="1" w:id="0" w:name="table"/> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr> <w:tr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc>

<w:bookmarkEnd w:id="0" /> </w:tr> <w:tr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr></w:tbl>

The colFirst attribute specifies that all columns starting with the first column shall be included in the table bookmark. This will apply starting with the first row and ending with the second row (the two rows within the bookmark's start and end). end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

colLast (Last Table Column Covered By Bookmark)

Specifies the zero-based index of the last column in this row which shall be part of this bookmark.

When a bookmark is contained within a table, it is possible for that bookmark to only cover cells within a certain column and row range within that table, by specifying:

The first row for which the specified columns are part of the table bookmark. This is accomplished by placing the bookmarkStart element in the first table cell in that row.

The first column included in the bookmark for each of the specified row(s) via the colFirst attribute.

The last column included in the bookmark for each of the specified row(s) via this attribute.

The last row for which the specified columns are part of the table bookmark. This is accomplished by placing the bookmarkEnd element at the end of that table row.

If this attribute appears, then the colFirst attribute must also appear (regardless of where this bookmark is located) or the document shall be considered non-conformant. If this attibute and its pair occur on a bookmark which is not contained in a table, then their values should be ignored. If this value does not equal or exceed the value of colFirst or the number of columns in the table, then both values should be ignored.

[Example: Consider a three row by three column table where a table bookmark shall be applied to the contents of the first two cells in the first two rows in the table (the cells shaded below):

This bookmark would be specified using the following WordprocessingML for the table's conents:

<w:bookmarkEnd w:id="0" /> </w:tr> <w:tr> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> <w:tc> <w:p/> </w:tc> </w:tr></w:tbl>

The colLast attribute specifies that the last column that shall be included in the table bookmark is the second column. This will apply starting with the first row and ending with the second row (the two rows within the bookmark's start and end). end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

displacedByCustomXml (Annotation Marker Relocated For Custom XML Markup)

[Example: Consider a paragraph with block level custom XML markup and two comment anchor annotations (one before and one after the custom XML element's physical representation), as follows:

<w:commentRangeStart w:id="0" /><w:commentRangeStart w:id="1" w:displaced byCustomXml="next" /><w:customXml w:element="spec" … /><w:p> …</w:p>

The possible values for this attribute are defined by the ST_DisplacedByCustomXml simple type (§2.18.17).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

name (Bookmark Name)

Specifies the bookmark name.

If multiple bookmarks in a document share the same name, then the first bookmark (defined by the location of the bookmarkStart element in document order) shall be maintained, and all subsequent bookmarks should be ignored.

[Example: Consider the following XML for a bookmark around a single word:

<w:p> <w:bookmarkStart w:id="0" w:name="place" /> <w:r> <w:t>Seattle</w:t> </w:r> <w:bookmarkEnd w:id="0" /></w:p>

The name attribute specifies that the name for this bookmark is place. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

moveTo (Move Destination Paragraph)

This element specifies that the parent paragraph has been moved to this location and tracked as a revision. This does not imply anything about the revision state of the contents of the paragraph, and applies only to the existence of the paragraph as its own unique paragraph.

The following restrictions shall be applied to this content:

If this element occurs outside of a valid move destination container (§2.13.5.28; §2.13.5.27) for which a matching move source container (§2.13.5.24; §2.13.5.23) exists in the document, then content in this region shall be treated as inserted, rather than moved.

[Example: Consider a WordprocessingML document in which a paragraph of text is moved down in the document. This moved paragraph would be represented using the following WordprocessingML markup:

<w:moveToRangeStart w:id="0" w:name="aMove"/><w:p> <w:pPr> <w:rPr> <w:moveTo w:id="1" … /> </w:rPr> </w:pPr> …</w:p></w:moveToRangeEnd w:id="0"/>

The moveTo element as a child of the run properties of the paragraph mark specify that this paragraph mark was part of the content which was moved in the document. This implies nothing about the contents, since they may have been added later and not tracked as a revision (they must be marked as a move using the moveTo element (§2.13.5.26) around the run content). end example]

Parent Elements

rPr (§2.3.1.29); rPr (§2.3.1.30)

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

moveTo (Move Destination Run Content)

This element specifies that the inline-level content contained within it shall be treated as content which has been moved to this location and tracked as a revision.

The following restrictions shall be applied to this content:

This document has the sentence Some moved text. moved to the first sentence in the document. This revision is represented using the following WordprocessingML:

The moveTo element specifies that all of the inline-level content contained within shall be revision marked as content which was moved to its current location in the document. Because this moved content is contained within a complete move destination container (moveToRangeStart and moveToRangeEnd) with a corresponding move source, this content is tracked as a move. end example]

Parent Elements

Child Elements

Subclause

acc (Accent)

§7.1.2.1

bar (Bar)

§7.1.2.7

bookmarkEnd (Bookmark End)

§2.13.6.1

bookmarkStart (Bookmark Start)

§2.13.6.2

borderBox (Border-Box Function)

§7.1.2.11

box (Box Function)

§7.1.2.13

commentRangeEnd (Comment Anchor Range End)

§2.13.4.3

commentRangeStart (Comment Anchor Range Start)

§2.13.4.4

customXml (Inline-Level Custom XML Element)

§2.5.1.5

customXmlDelRangeEnd (Custom XML Markup Deletion End)

§2.13.5.4

customXmlDelRangeStart (Custom XML Markup Deletion Start)

§2.13.5.5

customXmlInsRangeEnd (Custom XML Markup Insertion End)

§2.13.5.6

customXmlInsRangeStart (Custom XML Markup Insertion Start)

§2.13.5.7

customXmlMoveFromRangeEnd (Custom XML Markup Move Source End)

§2.13.5.8

customXmlMoveFromRangeStart (Custom XML Markup Move Source Start)

§2.13.5.9

customXmlMoveToRangeEnd (Custom XML Markup Move Destination Location End)

§2.13.5.10

customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

§2.13.5.11

d (Delimiter Function)

§7.1.2.24

del (Deleted Run Content)

§2.13.5.12

eqArr (Equation-Array Function)

§7.1.2.34

f (Fraction Function)

§7.1.2.36

func (Function Apply Function)

§7.1.2.39

groupChr (Group-Character Function)

§7.1.2.41

ins (Inserted Run Content)

§2.13.5.20

limLow (Lower-Limit Function)

§7.1.2.54

limUpp (Upper-Limit Function)

§7.1.2.56

m (Matrix Function)

§7.1.2.60

moveFrom (Move Source Run Content)

§2.13.5.21

moveFromRangeEnd (Move Source Location Container - End)

§2.13.5.23

moveFromRangeStart (Move Source Location Container - Start)

§2.13.5.24

moveTo (Move Destination Run Content)

§2.13.5.26

moveToRangeEnd (Move Destination Location Container - End)

§2.13.5.27

moveToRangeStart (Move Destination Location Container - Start)

§2.13.5.28

nary (n-ary Operator Function)

§7.1.2.70

oMath (Office Math)

§7.1.2.77

oMathPara (Math Paragraph)

§7.1.2.78

permEnd (Range Permission End)

§2.13.7.1

permStart (Range Permission Start)

§2.13.7.2

phant (Phantom Function)

§7.1.2.81

proofErr (Proofing Error Anchor)

§2.13.8.1

r (Text Run)

§2.3.2.23

r (Run)

§7.1.2.87

rad (Radical Function)

§7.1.2.88

sdt (Inline-Level Structured Document Tag)

§2.5.2.29

smartTag (Inline-Level Smart Tag)

§2.5.1.9

sPre (Pre-Sub-Superscript Function)

§7.1.2.99

sSub (Subscript Function)

§7.1.2.101

sSubSup (Sub-Superscript Function)

§7.1.2.103

sSup (Superscript Function)

§7.1.2.105

Attributes

Description

author (Annotation Author)

Specifies the author for an annotation within a WordprocessingML document.

If this attribute is omitted, then no author shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:author="Example Author">

…

</w:…>

The author attribute specifies that the author of the current annotation is Example Author, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_String simple type (§2.18.89).

date (Annotation Date)

Specifies the date information for an annotation within a WordprocessingML document. The use of this information is outside of the scope of this Office Open XML Standard.

If this attribute is omitted, then no date information shall be associated with the parent annotation type.

[Example: Consider a comment represented using the following WordprocessingML fragment:

<w:… w:id="1" w:date="2006-01-01T10:00:00">

…

</w:…>

The date attribute specifies that the date of the current annotation is January 1st 2006 at 10:00 AM, which may be used as desired. end example]

The possible values for this attribute are defined by the ST_DateTime simple type (§2.18.15).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</choice>

</extension>

</complexContent>

</complexType>

moveToRangeEnd (Move Destination Location Container - End)

This element specifies the end of a region whose move destination contents are part of a single named move. When a move source is stored as a revision in a WordprocessingML document, two pieces of information must be stored about that move destination:

A set of pieces of content which were moved - both inline-level content (§2.13.5.26) and paragraphs (§2.13.5.25)

A move destination container (or "bookmark") which specifies that all content within it which marked as a move destination is part of a single named move. The name attribute on the move container links a group of move destination content with the corresponding group of move source content.

The following restrictions are applied to the use of this element:

If this element occurs without a corresponding moveToRangeStart element (§2.13.5.28) with a matching id attribute value, then it shall be ignored and no move source container exists

If this element and its paired end occur without a matching move source container (§2.13.5.24; §2.13.5.23), then moved content in this region shall be treated as if it was inserted

If multiple move destination containers surround the same text, the last valid container (determined by the location of the container start elements, in document order) should be the container associated with that text.

This document has the sentence Some moved text. moved to the first sentence in the document. This revision is represented using the following WordprocessingML:

The moveToRangeEnd element specifies the end of the move destination container within which all moved content is part of the move named move1. end example]

Parent Elements

Attributes

Description

displacedByCustomXml (Annotation Marker Relocated For Custom XML Markup)

[Example: Consider a paragraph with block level custom XML markup and two comment anchor annotations (one before and one after the custom XML element's physical representation), as follows:

<w:commentRangeStart w:id="0" /><w:commentRangeStart w:id="1" w:displaced byCustomXml="next" /><w:customXml w:element="spec" … /><w:p> …</w:p>

The possible values for this attribute are defined by the ST_DisplacedByCustomXml simple type (§2.18.17).

id (Annotation Identifier)

Specifies a unique identifier for an annotation within a WordprocessingML document. The restrictions on the id attribute, if any, are defined by the parent XML element.

If this attribute is omitted, then the document is non-conformant.

[Example: Consider an annotation represented using the following WordprocessingML fragment:

<w:… w:id="1" … >

…

</w:…>

The id attribute specifies that the ID of the current annotation is 1. This value is used to uniquely identify this annotation within the document content. end example]

The possible values for this attribute are defined by the ST_DecimalNumber simple type (§2.18.16).

The following XML Schema fragment defines the contents of this element:

</extension>

</complexContent>

</complexType>

moveToRangeStart (Move Destination Location Container - Start)

This element specifies the start of the region whose move destination contents are part of a single named move. When a move destination is stored as a revision in a WordprocessingML document, two pieces of information must be stored about that move destination:

A set of pieces of content which were moved - both inline-level content (§2.13.5.26) and paragraphs (§2.13.5.25)

The following restrictions are applied to the use of this element

If this element occurs without a corresponding moveToRangeEnd element (§2.13.5.27) with a matching id attribute value, then it shall be ignored and no move source container exists

If this element and its paired end occur without a matching move source container (§2.13.5.24; §2.13.5.23), then moved content in this region shall be treated as if it was inserted

This document has the sentence Some moved text. moved to the first sentence in the document. This revision is represented using the following WordprocessingML:

The moveToRangeStart element specifies the start of the move destination container within which all moved content is part of the move named move1. end example]