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>
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>
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:
<complexType name="CT_CellMergeTrackChange">
<complexContent>
<extension base="CT_TrackChange">
<attribute name="vMerge" type="ST_AnnotationVMerge" use="optional"/>
<attribute name="vMergeOrig" type="ST_AnnotationVMerge" use="optional"/>
</extension>
</complexContent>
</complexType>