2.1.327 Part 1 Section 17.13.5.11, customXmlMoveToRangeStart (Custom XML Markup Move Destination Location Start)

  • Article

For additional notes that apply to this portion of the standard, please see the notes for sdt, §17.5.2.30(a); sdt, §17.5.2.31(a); sdt, §17.5.2.32(a); comment, §17.13.4.2(b, c); cellDel, §17.13.5.1(a); ins, §17.13.5.18(b).

a.   The standard states that the customXmlMoveToRangeStart element applies moveTo to customXml elements.

Word also uses this element to apply moveTo to structured document tag elements.

b.   The standard states that the range specified by a pair of customXmlMoveToRangeStart and customXmlMoveToRangeEnd elements can overlap the range specified by another such pair of elements.

Word does not allow the range specified by a pair of customXmlMoveToRangeStart and customXmlMoveToRangeEnd elements to overlap the range specified by any other such pair of elements.

c.   The standard allows customXML move tracking to begin inside, end inside, or contain an oMathPara element.

Word has unpredictable behavior when customXML move tracking begins inside, ends inside, or contains an oMathPara element.

d.   The standard states that the document is non-conformant if customXmlMoveToRangeStart is not contained in a move source container.

Word ignores customXmlMoveToRangeStart if it is contained in a move source container.

e.   The standard states that the document is non-conformant if customXmlMoveToRangeStart is not contained in a move source container.

Word always writes the customXmlMoveToRangeStart in a move destination container.